self-critiquelisted

<!-- 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, and report the outcome honestly, including where you were wrong. The point is to surface error before the user does, and to make "is this actually right?" a measured quantity instead of a vibe. ## 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 verbatim, plus the concrete claims it makes and the source each claim rests on. This is `v1`. 2. **Spawn the critic.** Launch one independent agent with live-source access (issue tracker, code host, error monitor, the repo). Use the prompt template below. The critic must return: `s