Agent skill

opposing-counsel

Read a contract the way the counterparty's lawyer will — hunting for leverage, not fairness. Use when someone says 'read this like opposing counsel', 'how would the other side attack this agreement', 'find the weaknesses before they do', or before sending or signing any contract. Produces the demand/position letter opposing counsel would actually send, plus an out-of-character debrief with the clause fixes that defang each attack.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill opposing-counsel --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/opposing-counsel/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Opposing Counsel A friendly contract review asks "is this fair?". Opposing counsel asks "where does this bleed?". This skill reads the agreement as the counterparty's lawyer — paid to find ambiguity, missing protections, and unenforceable optimism — and writes the letter they would send when the relationship sours. (For the friendly review, use `contract-review`; this skill only attacks.) ## What This Skill Produces - A **weakness map**: every exploitable clause, ranked by severity - The **artifact**: the actual demand/position letter opposing counsel would send, in character - A **debrief** out of character: the clause-level fixes that would defang each attack, ranked by urgency ## Required Inputs Ask for these if missing; work with a thin brief but label every assumption: - **The contract or agreement text** (or the clauses in dispute) - **Which side the user is on** and what they most need the contract to protect - **The likely dispute scenario** (non-payment, scope fight, IP claim, termination) — if unknown, attack the three most probable - Optional: governing law, deal value, what has already gone wrong ## The Adversary's Method Read as counsel for the other side, in this or

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. The Adversary's Method
  4. Output Format
  5. The Weakness Map
  6. The Letter (in character)
  7. Debrief — out of character
  8. Quality Checks
  9. Anti-Patterns
Ships with 1 file
  • references/worked-example.md
More from pm-claude-skills
All skills →
About this skill
What does the opposing-counsel skill do?

Read a contract the way the counterparty's lawyer will — hunting for leverage, not fairness. Use when someone says 'read this like opposing counsel', 'how would the other side attack this agreement', 'find the weaknesses before they do', or before sending or signing any contract. Produces the demand/position letter opposing counsel would actually send, plus an out-of-character debrief with the clause fixes that defang each attack.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill opposing-counsel --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going