critique-report

Reviews finished drafts against a thirteen-point checklist and returns a pass, fix, or block verdict.

4|1|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/radarist/structured-analytic-skills --skill critique-report-radarist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: critique-report
Source: https://github.com/radarist/structured-analytic-skills/tree/main/skills/critique-report
Command: npx skills add https://github.com/radarist/structured-analytic-skills --skill critique-report-radarist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Finished reports and briefs often ship with unsourced claims, overstated confidence, missing limitations, or vague next actions that a reviewer would catch immediately. This Skill runs a structured pre-publication self-critique so those defects are found and fixed before the document reaches its reader. ## Core Features & Use Cases - Fixed thirteen-point review: Scores ten base points (answers the question, evidence sourced, anti-patterns avoided, reproducible method, honest confidence, limitations stated, audience calibration, counter-evidence, defensible numbers, actionable next steps) plus three conditional points that fire only on specific document shapes. - Mechanical verdict: Derives an APPROVE, REVISE, or BLOCK verdict directly from the point statuses, with a located fix and pass condition for every non-passing point. - Use Case: A market brief claims a vendor is the "clear leader" with "60% YoY growth" but cites nothing. The critique blocks publication, flags the unsourced figures and missing limitations, and specifies exactly which sections to rewrite and what fixed looks like. ## Quick Start Use the critique-report skill to review my finished draft brief before I send it and tell me what a reviewer would catch.

Frequently Asked Questions about critique-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a report before publishing it?▼

Run a structured self-critique over the complete draft: score ten base points covering sourcing, confidence, limitations, counter-evidence, numbers, and next actions, then derive an approve, revise, or block verdict. Every failing point gets a located fix and the condition under which it would pass.

What should a pre-publication checklist for analytical reports include?▼

It should check that the document answers the question asked, every load-bearing claim is cited, the method is reproducible, stated confidence matches the evidence grade, limitations and counter-evidence are addressed, numbers carry units and dates, and next actions have an owner and a date.

When should I use red-team-claim instead of a full document critique?▼

Use red-team-claim when one headline claim needs adversarial attack along definitions, baselines, and counter-examples. Use the full document critique when the whole draft's structure, sourcing, and next actions need auditing before publication.

Can this review short chat replies or working notes?▼

No. The critique applies only to reader-facing deliverables of roughly 400 words or more, such as reports and briefs. Short replies and intermediate working notes are not gated, and a document already reviewed and revised once should not be critiqued a third time.

Why does a document critique return a block verdict?▼

A block verdict follows mechanically whenever any of the ten base points is marked red, such as unsourced load-bearing claims, missing limitations, or unreproducible numbers. The affected sections must be rewritten and the failing points re-reviewed before shipping.