critic-looplisted

LLM-as-judge quality gate. Before any deliverable ships, spawn an independent critic subagent (or N critics with distinct lenses) that ADVERSARIALLY grades the artifact against an explicit rubric, returns PASS/FAIL + a prioritized fix list, and loops (build → critique → fix) until it passes or N rounds hit. The builder must NOT grade its own work. Critic defaults to FAIL on uncertainty. Output is a scorecard + prioritized fixes + a hard ship/no-ship verdict. Domain rubrics baked in for SkynetLabs work: client website, content/copy, automation/n8n, Upwork/Fiverr proposal. Generic mode takes any artifact + rubric. Multi-critic mode runs 3 lenses + majority vote (ties to fanout-ship pattern). Trigger when user says: "critic loop", "/critic-loop", "judge this", "grade this before I send", "is this good enough to ship", "quality gate", "have a critic review", "second-agent review", or before ANY billable deliverable leaves. Auto-trigger heuristic: a deliverable (site, copy, workflow, proposal, audit) is about to b
waseemnasir2k26/skynetlabs-all-claude-code · ★ 0 · AI & Automation · score 68

Install: claude install-skill waseemnasir2k26/skynetlabs-all-claude-code

# critic-loop LLM-as-judge quality gate. Operationalizes the "2nd agent grades/self-corrects before you accept" lesson (claude-code-mastery, video 8). SkynetLabs only had the manual `/review`; this is the automated gate that runs before a deliverable ships. ## Core principle **The builder never grades its own work.** A model that wrote an artifact is biased toward approving it. Spawn a SEPARATE critic agent with a clean context, give it the artifact + rubric + adversarial framing, and let IT decide. Loop until PASS. ``` build → spawn critic (FAIL-biased) → PASS? ship : apply fixes → re-critique ↑________________________________________| max N rounds (default 3) ``` ## When to use USE before: - A client deliverable is sent (website, copy, audit, proposal, automation) - A deploy / publish / `git push` to production - Anything with secrets, credentials, or money flow SKIP when: - Throwaway scratch work, internal notes, exploratory spikes - Already passed critic this session AND artifact unchanged - Time-critical hotfix where the fix is trivial + reversible (still log it) ## Inputs required 1. **Artifact** — path(s), URL, pasted text, or git diff (`git diff main`) 2. **Type** — one of: `website` | `copy` | `automation` | `proposal` | `generic` 3. **Rubric** — auto-selected from type (below), or user-supplied for `generic` 4. **Mode** — `single` (1 critic, default) | `multi` (3 lenses, majority vote) 5. **Max ro