/reporting-standard-checklist
Check whether a paper reports each item from PRISMA, CONSORT, STROBE, ARRIVE, SPIRIT, or TRIPOD (per whichever study-design-tool-gate dispatched to), citing where each item is or isn't addressed — including a/b sub-item hierarchy where the standard defines one. Use this after
$ npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill reporting-standard-checklist --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/reporting-standard-checklist
Context preview
The summary Claude sees to decide when to auto-load this skill.
Check whether a paper reports each item from PRISMA, CONSORT, STROBE, ARRIVE, SPIRIT, or TRIPOD (per whichever study-design-tool-gate dispatched to), citing where each item is or isn't addressed — including a/b sub-item hierarchy where the standard defines one. Use this after
SKILL.md
reporting-standard-checklist.SKILL.mdname: reporting-standard-checklist
description: Check whether a paper reports each item from PRISMA, CONSORT, STROBE, ARRIVE, SPIRIT, or TRIPOD (per whichever study-design-tool-gate dispatched to), citing where each item is or isn't addressed — including a/b sub-item hierarchy where the standard defines one. Use this after study-design-tool-gate has dispatched to one of these 6 reporting standards; this checks report completeness (did they say where), not methodological quality (was the study done well) — there is no overall synthesis step, judgment per item is the terminal output.
version: 1.0.0
category: paper-reading
type: sop
execution: subagent
prompt: ./prompt.md
input: 'source_path (string), meta_path (string), dispatched_tool (string)'
reads: 'full paper — a reporting checklist asks whether each item appears anywhere'
output: 'checklist_result (list of {item, sub_item, judgment, location})'
dependencies:
sops:
- spawn-agentReporting Standard Checklist
Per-item report-completeness check (with location citation) across PRISMA/CONSORT/STROBE/ARRIVE/SPIRIT/TRIPOD. No integration step — unlike quality-appraisal-checklist, judgment per item IS the terminal output.
Execution
Subagent — spawned via spawn-agent skill.
Reference
`references/item-sets.md` — the authorial-to-reader reversal note that applies to all 6 standards is there, read before drafting (Progressive Disclosure — kept out of this SKILL.md body).
<!-- BEGIN available-tables (generated) -->
Available SOPs
| SOP | When to use | | --- | --- | | spawn-agent | Spawn a customized CC subagent with full MCP tool access. |
<!-- END available-tables (generated) -->
Read more
name: reporting-standard-checklist
description: Check whether a paper reports each item from PRISMA, CONSORT, STROBE, ARRIVE, SPIRIT, or TRIPOD (per whichever study-design-tool-gate dispatched to), citing where each item is or isn't addressed — including a/b sub-item hierarchy where the standard defines one. Use this after study-design-tool-gate has dispatched to one of these 6 reporting standards; this checks report completeness (did they say where), not methodological quality (was the study done well) — there is no overall synthesis step, judgment per item is the terminal output.
version: 1.0.0
category: paper-reading
type: sop
execution: subagent
prompt: ./prompt.md
input: 'source_path (string), meta_path (string), dispatched_tool (string)'
reads: 'full paper — a reporting checklist asks whether each item appears anywhere'
output: 'checklist_result (list of {item, sub_item, judgment, location})'
dependencies:
sops:
- spawn-agentReporting Standard Checklist
Per-item report-completeness check (with location citation) across PRISMA/CONSORT/STROBE/ARRIVE/SPIRIT/TRIPOD. No integration step — unlike quality-appraisal-checklist, judgment per item IS the terminal output.
Execution
Subagent — spawned via spawn-agent skill.
Reference
`references/item-sets.md` — the authorial-to-reader reversal note that applies to all 6 standards is there, read before drafting (Progressive Disclosure — kept out of this SKILL.md body).
<!-- BEGIN available-tables (generated) -->
Available SOPs
| SOP | When to use | | --- | --- | | spawn-agent | Spawn a customized CC subagent with full MCP tool access. |
<!-- END available-tables (generated) -->
The complete research orchestration system for AI-native science. What It Does Design Philosophy Architecture (v3.2.2) Quick Start Configuration Roadmap License DARE is not a tool that helps you do research. It is the researcher.
Repo: yogsoth-ai/de-anthropocentric-research-engine
Other skills on de-anthropocentric-research-engine.
- /formated-results
Closing skill for the research-executor, loaded as the last step of formated-specs. Summarize the design just produced into one research-result JSON fenced block in your reply. Do not execute the research.
Open skill - /formated-specs
Spec-slot skill for the research-executor. Emit the 4-layer DARE orchestration of the assigned topic as one research-graph JSON fenced block in your reply. Replaces the generic spec-writing step.
Open skill - /injection-fidelity
Loss-1 judge (codex role). Given one sample's de-identified dialogue and its PolicyCard, decide axis-by-axis whether the user-simulator enacted the card's per-axis pressure. Judge enactment of the card, never whether the research is good.
Open skill - /ladder-quality-order
Loss-2 judge (codex role). Over one topic's 6 shuffled research-design samples, pairwise-rank by quality using the D1–D5 standard. Emit the pairwise log; the harness computes the order and the ladder verdicts. Judge quality difference, never against academic standards.
Open skill - /optimization-loop
The optimizer brain for the ladder-foundry pretraining loop. Runs the two-level nested batch loop, delegates gating to gate_eval, attributes a failing batch to one weight (attribute-first), and recovers from disk after compaction. Control flow is fully scripted; only the
Open skill - /acu-nugget-recall
Tactic: Extract atomic units from one paper and score how much of a caller-supplied summary covers. Use for ACU-style binary or Nugget-style ternary recall checks; cannot run without a target summary.
Open skill

