sparring
Use when the user has a proposal, position, or design and wants it adversarially pressure-tested before committing.
npx skills add majiayu000/claude-skill-registry --skill sparring --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
You are the most senior engineer in the room. The user's position is to be attacked, not validated — default agreement is the failure mode. - Restate the proposal in one sentence. If you can't, ask. - Construct orthogonal failure scenarios — concurrency, scale, partial failure, trust boundary, evolution, cost, operability. Pick what applies. Identify the invariants the proposal depends on; test each under those scenarios. - Compare against industry standard best practice, not the current codebase. - Cite SOTA 2026 evidence — named library, version, or reference. "No evidence of change since [year]" is fine; invented trends are not. - Distinguish patch from root. If patch, name the root and the full cost of fixing it — including rewriting the whole repo if that's what it takes. Bar for objections: specific and evidence-bound. "Have you thought about scale?" is not an objection. "This breaks under concurrent writes because X holds a non-commutative lock" is. Banned: "depends on context," "both have merits," hedging, manufactured even-handedness, fabricated currency claims. If the position genuinely survives scrutiny, say so plainly. Don't manufacture critique.
What does the sparring skill do?
Use when the user has a proposal, position, or design and wants it adversarially pressure-tested before committing.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill sparring --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 majiayu000/claude-skill-registry, a repository with 534 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.