Agent skill
tone-aggressive
Applies aggressive advocacy tone to legal writing with forceful, adversarial prose, strong declarative framing, and minimal hedging. Use when drafting opposition briefs, responses to bad-faith conduct, compliance demands, trial briefs, or any document requiring zealous positional advocacy.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/tone-aggressive
SKILL.md
Aggressive Advocacy Tone
Forceful, adversarial writing style for zealous positional advocacy. Produces short declarative sentences, eliminates hedging, and front-loads conclusions.
When to Apply
- Opposing frivolous or bad-faith motions
- Responding to discovery abuse or litigation misconduct
- Demanding compliance with clear legal obligations
- Trial briefs requiring credibility attacks on adverse witnesses
- Pre-suit demands after failed good-faith negotiation
Quick Start
- Identify the strongest factual point — lead with it
- Replace hedging language ("may," "might," "arguably") with declaratives ("is," "was," "conclusively")
- Frame around opposing party's failures first, then client's strength
- Anchor every assertion to an exhibit, transcript page, or statutory provision
- Check against guardrails before finalizing
Voice Directives
| Attribute | Directive |
|---|---|
| Sentence structure | Short, declarative, front-loaded with conclusions |
| Hedging | Eliminate — use "is," "was," "conclusively" |
| Framing | Opposing party's failures first, then client's strength |
| Emphasis | Repetition of key facts; parallel structure for cumulative impact |
| Register | Formal but blunt — courthouse, not boardroom |
| Transitions | Confrontational ("Yet," "Despite this," "Nonetheless") over neutral connectors |
Phrase Toolkit
| Purpose | Examples |
|---|---|
| Dismissing arguments | "fails for multiple independent reasons"; "is unsupported by any authority" |
| Establishing misconduct | "was willful and calculated"; "cannot be explained by inadvertence" |
| Asserting facts | "the evidence conclusively establishes"; "the record is unambiguous" |
| Challenging credibility | "flatly contradicted by the documentary record"; "ignores the plain language of" |
| Demanding action | "must immediately cease"; "is required — not invited — to comply" |
Calibration
- Factual anchors required — every strong assertion needs a cite (exhibit, transcript, statute)
- Attack positions, not counsel — "Plaintiff's argument misrepresents" not "Plaintiff's counsel misrepresents"
- Match intensity to forum — scale back for judges known to penalize overheated briefing
- Preserve credibility — one overstatement undermines the entire document
- Front-load strongest points — aggressive tone loses force when buried mid-section
Guardrails
- No ad hominem attacks on opposing counsel
- No assertions without evidentiary support in the record
- No mischaracterization of authority — quote holdings accurately even while distinguishing aggressively
- Comply with Model Rule 3.4 (fairness to opposing party) and 8.4(d) (conduct prejudicial to administration of justice)
- Tribunal civility rules or local decorum orders override tone preferences
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?