← ClaudeAtlas

self-critiquelisted

Adversarially critique your own last substantial answer before the user has to. Spawn a critic agent that verifies every claim against live sources, checks similar and related issues, finds patterns, and addresses comments directly to you. Loop (revise, re-score) until satisfied, report where you were wrong, iterations-to-satisfy, the numeric improvement and a final score, then convert what the critic caught into a durable rule so the next session does not repeat it. Use when the user asks you to criticize, challenge, stress-test, or red-team your own answer, or accepts a "critical-thinking review" offer.
oleg-koval/agent-skills · ★ 3 · AI & Automation · score 75
Install: claude install-skill oleg-koval/agent-skills
<!-- Generated by scripts/build-adapters.sh. Do not edit directly. --> # Self-critique Run an adversarial review of **your own previous answer** and report the result in numbers. ## Overview A confident answer is not a verified one. This skill turns your last substantial reply into the subject of a hostile review: a separate critic agent tries to refute it against live sources, hunts for the related issue or pattern you missed, and scores it. You then revise and re-score until the score stops moving, report the outcome honestly, including where you were wrong, and convert what the critic caught into a rule that survives the session. The point is to surface error before the user does, to make "is this actually right?" a measured quantity instead of a vibe, and to make the same mistake cost less the second time than it did the first. A critique that ends at a score has bought one corrected answer. A critique that ends at a durable rule has bought every answer after it. ## When to Use - The user asks you to criticize, challenge, stress-test, red-team, or "poke holes in" your own answer. - The user accepts a "critical-thinking review" offer. - You have just produced a substantial analysis, recommendation, or investigation and want a confidence number before the user acts on it. Do not use for trivial one-shot replies or simple chat. The overhead only pays off on load-bearing answers. ## Procedure 1. **Snapshot the target.** Capture your last substantial answer verbati