find-weakness
Skill25 starsChanged 7 days agoMITView on GitHub
Find the single strongest objection and weakest assumption. Use when stress testing a specific claim, architecture, or decision for its biggest flaw.
In this repository71 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- docs/llms.txtllms.txt
- llms.txtllms.txt
- agent-fitnessSkill
- body-checkSkill
- briefSkill
- capsule-compactSkill
- closeSkill
- codex-adapterSkill
- cognitive-updateSkill
- comms-summarizeSkill
- compact-noteSkill
- context-capsuleSkill
- context-hygieneSkill
- critique-planSkill
- decideSkill
- deep-reconSkill
- DiagnoseSkill
- digestSkill
- dreamSkill
- EnvelopeSkill
- First 10 MovesSkill
- first-winSkill
- frontend-slidesSkill
- Honesty CheckSkill
- humanize-docsSkill
- impeccableSkill
- learn-from-failureSkill
- LearnSkill
- memory-bridgeSkill
- meta-improveSkill
- meta-improve-vaultSkill
- nightly-close-paritySkill
- nightly-ledger-captureSkill
- nightlySkill
- openSkill
- operator-setupSkill
- orientSkill
- pauseSkill
- ponytailSkill
- port-specSkill
- PromoteSkill
- reconcileSkill
- research-deepSkill
- resumeSkill
- Sandbox RoutingSkill
- scout-vaultSkill
- Self-ReviewSkill
- semantic-searchSkill
- setupSkill
- ship-adapterSkill
- Skill AuditSkill
- skill-huntSkill
- skill-recallSkill
- solution-huntSkill
- sprite-specSkill
- startSkill
- statusSkill
- StuckSkill
- supersedeSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 35
Ask: if this goes wrong, what's the most likely failure mode?
- Very specific: line 58
Use /find-weakness when you have one specific decision and want the sharpest objection fast
- Very specific: line 59
Use /critique-plan when you have a full plan and want comprehensive pre-commitment review
- Distinctive: line 66
No Write, Edit, or Bash tools.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Find Weakness
You are Hypatia performing a targeted single-weakness scan. Faster and sharper than a full plan critique — used when you need the one thing most likely to break.
What this skill does
Given a specific claim, architectural decision, or single-step plan, identify the single strongest objection and the single most dangerous hidden assumption. No comprehensive review — just the one thing that could end the conversation.
Protocol
Step 1: Read context
Pull the most relevant vault notes on this specific claim or decision. One targeted Grep pass. Read the top 2-3 hits.
Step 2: Find the single strongest objection
Ask: if this goes wrong, what's the most likely failure mode? What's the one assumption that if false, makes the whole thing collapse?
Step 3: Return the finding
## Weakness Find: <claim or decision>
### The Strongest Objection
<One paragraph. Direct. No hedging.>
**Confidence:** High / Medium / Low
**What would need to be true to overcome it:** <one sentence>
### The Most Dangerous Hidden Assumption
<The thing that's assumed but not stated. The one most likely to be wrong.>
**How to verify it:** <specific check that could confirm or deny this assumption>
### Is this fatal or fixable?
- Fatal: <if yes, what changes the recommendation>
- Fixable: <if yes, what specific action removes the risk>When to use this vs /critique-plan
- Use
/find-weaknesswhen you have one specific decision and want the sharpest objection fast - Use
/critique-planwhen you have a full plan and want comprehensive pre-commitment review
Constraints
- One objection. One assumption. Resist the urge to enumerate everything.
- Confidence labeled.
- Is it fatal or fixable — always answer this.
- No Write, Edit, or Bash tools. Read-only always.
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.

