find-weakness — Claude Code skill: what it does, how to install
find-weakness — a skill for Claude Code and Codex isolates the single strongest objection and the riskiest unstated assumption in any architectural choice or claim.
MIT ★ 26 updated 2026-11-16
npx skills add wrg32786/aigent-os --skill find-weakness -a claude-codeWhat find-weakness does
The skill runs a fast stress test on a single technical claim or architectural decision instead of executing a full plan review. The agent scans local notes or code with Grep and Read, then highlights the single failure mode most likely to break the approach.
Each report specifies a confidence rating, the exact condition needed to overcome the objection, a concrete verification check for the assumption, and whether the issue is fatal or fixable.
The skill runs strictly read-only using Read, Grep, Glob, and WebFetch. It lacks access to Write, Edit, or Bash, so it cannot modify files in the repository.
What it helps with
- stress test an architectural decision against its worst-case failure mode
- surface dangerous unstated assumptions before committing to an approach
- determine whether an architectural flaw is fatal or fixable
Example prompts for the agent
- Stress test our decision to store all user sessions in Redis
- Find the weakest assumption in this database migration approach
- What is the single biggest risk with adopting this message queue
How to install find-weakness
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill find-weakness -a claude-code2Manually: put the files in place
~/.claude/skills/find-weakness/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/find-weakness/
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill find-weakness -a codex2Manually: put the files in place
.agents/skills/find-weakness/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill find-weakness -a cursor2Manually: put the files in place
.cursor/skills/find-weakness/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wrg32786/aigent-os skills/find-weakness2Manually: put the files in place
.github/skills/find-weakness/SKILL.md1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill find-weakness -a gemini-cli2Platform CLI
gemini skills install https://github.com/wrg32786/aigent-os --path skills/find-weaknessManually: put the files in place
.devin/skills/find-weakness/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill find-weakness -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about find-weakness
How do I install find-weakness in Claude Code?
Run npx skills add wrg32786/aigent-os --skill find-weakness -a claude-code in your terminal or place the file in ~/.claude/skills/find-weakness/SKILL.md.
How does find-weakness differ from critique-plan?
It evaluates a single isolated decision and returns only one objection and one assumption, skipping full pre-commitment audits.
Can find-weakness modify files in the workspace?
No, the skill is restricted to Read, Grep, Glob, and WebFetch, with Write, Edit, and Bash completely disabled.
Source text
SKILL.md · MIT
--- name: find-weakness agent: hypatia description: "Find the single strongest objection and weakest assumption. Use when stress testing a specific claim, architecture, or decision for its biggest flaw." allowed-tools: Read, Grep, Glob, WebFetch user-invocable: true triggers: - find the weakness - find weakness - what's the flaw - what's wrong with this - strongest objection - single biggest risk - stress test this - what's the weakest point - find the assumption --- # 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-weakness` when you have one specific decision and want the sharpest objection fast - Use `/critique-plan` when 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.
© wrg32786 · MIT · wrg32786/aigent-os