/quality-appraisal-checklist
Run CASP (8 study-type variants), JBI (~6 variants), or AMSTAR-2 quality-appraisal checklists — each ending in the tool''s own required integrated judgment, not just item tallies. Also runs a proposal "rhetorical-completeness-check" mode (entry_mode="completeness_check") that
$ npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill quality-appraisal-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
/quality-appraisal-checklist
Context preview
The summary Claude sees to decide when to auto-load this skill.
Run CASP (8 study-type variants), JBI (~6 variants), or AMSTAR-2 quality-appraisal checklists — each ending in the tool''s own required integrated judgment, not just item tallies. Also runs a proposal "rhetorical-completeness-check" mode (entry_mode="completeness_check") that
SKILL.md
quality-appraisal-checklist.SKILL.mdname: quality-appraisal-checklist
description: 'Run CASP (8 study-type variants), JBI (~6 variants), or AMSTAR-2 quality-appraisal checklists — each ending in the tool''s own required integrated judgment, not just item tallies. Also runs a proposal "rhetorical-completeness-check" mode (entry_mode="completeness_check") that instead diffs unit-classification''s rhetorical labels against a target checklist''s expected label set. Use this after study-design-tool-gate has dispatched to CASP/JBI/AMSTAR-2 (mode a), or directly after unit-classification when checking for missing argumentative moves (mode b, proposal/unverified).'
version: 1.0.0
category: paper-reading
type: sop
execution: subagent
prompt: ./prompt.md
input: 'entry_mode (string: "checklist" | "completeness_check"), source_path (string) and meta_path (string) and dispatched_tool (string) when entry_mode is "checklist", OR classified_units (list) and target_checklist_labels (list of strings) when entry_mode is "completeness_check"'
reads: 'method and results sections in checklist mode; nothing in completeness_check mode'
output: 'checklist_result (list of {item, judgment}), overall_appraisal (string, mode a only)'
dependencies:
sops:
- spawn-agentQuality Appraisal Checklist
CASP/JBI/AMSTAR-2 item-level appraisal + each tool's own required overall synthesis. Also hosts the proposal rhetorical-completeness-check as a second entry mode (see below) rather than as its own SOP file.
Execution
Subagent — spawned via spawn-agent skill.
Reference
`references/item-sets.md` — full item lists per tool/variant, read before drafting; kept out of this SKILL.md body per Progressive Disclosure (CASP alone has 8 variants).
Why rhetorical-completeness-check Is a Mode Here, Not Its Own File
This plan's header documents a correction found while planning: the pipeline graph (`context/2026-08-07-13-42-sop-pipeline-graph.html`) never defines `rhetorical-completeness-check` as a node in its `nodes` array — it only appears as a method label on the edge `unit-classification → quality-appraisal-checklist`, with the edge's own inline comment ("M13修订") describing it as an entry mode into THIS SOP, not a standalone one. The design spec (§4) listed it as a separate file, but per the spec's own stated rule that the graph is the source of truth over the transcription, this SOP's `entry_mode` parameter is the correct home for it — building a 5th file here would silently inflate the buildable-SOP count past the spec's own stated total of 30.
<!-- 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: quality-appraisal-checklist
description: 'Run CASP (8 study-type variants), JBI (~6 variants), or AMSTAR-2 quality-appraisal checklists — each ending in the tool''s own required integrated judgment, not just item tallies. Also runs a proposal "rhetorical-completeness-check" mode (entry_mode="completeness_check") that instead diffs unit-classification''s rhetorical labels against a target checklist''s expected label set. Use this after study-design-tool-gate has dispatched to CASP/JBI/AMSTAR-2 (mode a), or directly after unit-classification when checking for missing argumentative moves (mode b, proposal/unverified).'
version: 1.0.0
category: paper-reading
type: sop
execution: subagent
prompt: ./prompt.md
input: 'entry_mode (string: "checklist" | "completeness_check"), source_path (string) and meta_path (string) and dispatched_tool (string) when entry_mode is "checklist", OR classified_units (list) and target_checklist_labels (list of strings) when entry_mode is "completeness_check"'
reads: 'method and results sections in checklist mode; nothing in completeness_check mode'
output: 'checklist_result (list of {item, judgment}), overall_appraisal (string, mode a only)'
dependencies:
sops:
- spawn-agentQuality Appraisal Checklist
CASP/JBI/AMSTAR-2 item-level appraisal + each tool's own required overall synthesis. Also hosts the proposal rhetorical-completeness-check as a second entry mode (see below) rather than as its own SOP file.
Execution
Subagent — spawned via spawn-agent skill.
Reference
`references/item-sets.md` — full item lists per tool/variant, read before drafting; kept out of this SKILL.md body per Progressive Disclosure (CASP alone has 8 variants).
Why rhetorical-completeness-check Is a Mode Here, Not Its Own File
This plan's header documents a correction found while planning: the pipeline graph (`context/2026-08-07-13-42-sop-pipeline-graph.html`) never defines `rhetorical-completeness-check` as a node in its `nodes` array — it only appears as a method label on the edge `unit-classification → quality-appraisal-checklist`, with the edge's own inline comment ("M13修订") describing it as an entry mode into THIS SOP, not a standalone one. The design spec (§4) listed it as a separate file, but per the spec's own stated rule that the graph is the source of truth over the transcription, this SOP's `entry_mode` parameter is the correct home for it — building a 5th file here would silently inflate the buildable-SOP count past the spec's own stated total of 30.
<!-- 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