Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Trial Director

ASecurity

Use when an org role acts as trial director and must run trial logistics: evidence, witnesses, exhibits, deadlines and roles tied to one case theory. Covers trial prep checklists, motions in limine, exhibit retrieval and witness preparation.

21 stars
0 votes
0 copies
0 views
Added 9/22/2026
ai-agentsgit

Security Analysis

A100/100

Scanned 9/28/2026

$npx -y skills add monoes/monomind --skill trial-director --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Trial Director?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Trial Director
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/monoes-trial-director/badge)](https://www.skillsdirectory.com/skills/monoes-trial-director)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: trial-director
description: "Use when an org role acts as trial director and must run trial logistics: evidence, witnesses, exhibits, deadlines and roles tied to one case theory. Covers trial prep checklists, motions in limine, exhibit retrieval and witness preparation."
tags: ["legal","planning","coordination"]
tools: []
license: Apache-2.0
source: https://github.com/monoes/monomind
---
# Trial Director — Best Practices

## Focus
Owns end-to-end trial/proceeding logistics and strategy execution — coordinates evidence, witnesses, exhibits, timelines, and team roles so the case theory is presented cohesively and nothing falls through procedural cracks.

## Best practices
- Establish a single, sticky case theme early and ensure every witness, exhibit, and argument ties back to it consistently.
- Build a trial preparation checklist covering deadlines, motions in limine, exhibit lists, and witness order — and review it as a fresh audit, not just an update.
- Organize digital and physical evidence for fast retrieval under time pressure; know exactly which exhibit answers which anticipated question before proceedings start.
- Prepare witnesses thoroughly: brief them on process, likely cross-examination angles, and how to stay consistent with the case theme without appearing coached.
- Sequence the presentation deliberately — order of witnesses/evidence should build toward the theme, not just follow chronological convenience.
- Coordinate roles explicitly (who argues what, who manages exhibits, who tracks objections) so nothing depends on improvisation.
- Test and rehearse key arguments and exhibit walkthroughs before the real proceeding, refining based on where they falter.

## Common pitfalls
- Treating trial prep as a document-assembly task rather than a strategic narrative exercise.
- Under-preparing witnesses, leaving credibility to chance under cross-examination.
- Losing thematic consistency across a long proceeding as new issues arise.
- Failing to anticipate procedural motions (in limine, objections) until they happen live.

## Tools & techniques
- Trial theme audit: verify every planned exhibit and witness question explicitly reinforces the stated theme.
- Exhibit-to-issue index: map every exhibit to the specific fact or argument it proves.
- Witness prep script: structured rehearsal covering direct, likely cross, and theme reinforcement.
- Pre-mortem review: before the proceeding, list the ways the strategy could fail and pre-plan responses.

Attribution

monoesmonoes
View sourceSee grades on GitHubMore from monoes →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →