cross-critique
Skill1 starsChanged 16 days agoMITView on GitHub
Use when a decision is high-stakes or genuinely uncertain and you want it stress-tested before committing — dispatch independent critiques of a proposed choice, then synthesize. Triggers include "pressure-test this decision", "what am I missing", "red-team this", choosing between architectures, or any irreversible call worth a second and third opinion.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- warpdotdev/common-skillstheir own version, first seen Oct 20, 2026
- zhouycheng/skillstheir own version, first seen Oct 13, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- warpdotdev/common-skills★ 630same name
- zhouycheng/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository44 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- bigquery-superpowersSkill
- building-data-pipelinesSkill
- data-quality-checksSkill
- dbt-incremental-modelsSkill
- dimensional-modelingSkill
- reviewing-sqlSkill
- writing-dbt-modelsSkill
- arenaSkill
- authority-boundarySkill
- beadflowSkill
- blast-radiusSkill
- control-uiSkill
- create-prSkill
- create-verification-skillSkill
- deslopSkill
- diagnosing-bugsSkill
- feedback-to-infrastructureSkill
- finding-concurrency-bugsSkill
- fixing-and-merging-prsSkill
- foundational-thinkingSkill
- grilling-frontend-prototypingSkill
- improve-harnessSkill
- maintain-verification-skillSkill
- make-operations-idempotentSkill
- metamorphic-testingSkill
- minimize-reader-loadSkill
- preflightSkill
- prototypeSkill
- recon-before-actionSkill
- redesign-from-first-principlesSkill
- resolve-merge-conflictsSkill
- tddSkill
- whySkill
- writing-great-skillsSkill
- catch-me-upSkill
- definition-of-doneSkill
- experience-firstSkill
- grillingSkill
- grill-with-docsSkill
- handoffSkill
- never-block-on-the-humanSkill
- show-me-your-workSkill
- unslopSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Dispatch independent critics — give each a distinct lens: Don't ask three agents the same question.
- Distinctive: line 36
Run them independently so they don't anchor on each other.
- Distinctive: line 42
Synthesize — don't just average: Read the critiques and decide what actually changes your mind.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Cross-Critique
Sharpen a decision by attacking it from several independent angles before you commit, then synthesize what survives. A single line of reasoning has blind spots; multiple independent critiques expose the ones you can't see from inside your own argument.
When it's worth it
For reversible, low-stakes calls, just decide. Reach for cross-critique when the decision is expensive to undo or genuinely uncertain: architecture choices, data-model commitments, anything where being wrong costs days.
How to run it
- State the proposal crisply. One clear statement of the decision and the reasoning behind it. Vague proposals get vague critiques.
Dispatch independent critics — give each a distinct lens. Don't ask three agents the same question; redundant critics find redundant problems. Assign different angles, e.g.:
- Correctness / logic — where does the reasoning not hold?
- Risk / failure modes — how does this go wrong in production, at scale, at 3am?
- Cost / simplicity — is there a materially cheaper or simpler option that gets 90% of the value?
- The opposite — argue the strongest case for the alternative we're rejecting.
Run them independently so they don't anchor on each other.
- Demand specifics, not vibes. A critique that says "seems risky" is noise. Each critic should name a concrete failure, a concrete cheaper alternative, or a concrete flawed assumption.
- Synthesize — don't just average. Read the critiques and decide what actually changes your mind. Some objections are decisive; some are theoretical. The output is a sharper decision (possibly the original one, now better-justified), not a tally of votes.
Output
A short writeup: the decision, the objections that mattered, how they changed (or didn't change) the call, and the residual risks you're knowingly accepting. That record is itself valuable — it's the "why" a future handoff or ADR needs.
Inspired by Warp's cross-critique skill (https://github.com/warpdotdev/common-skills). Prose is our own.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

