quality-appraisal-checklist
Skill1 starsChanged 3 months agoApache-2.0View on GitHub
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).
In this repository34 other files it gives its agents.
- acu-nugget-recallSkill
- argumentative-zoningSkill
- atomic-unit-matchingSkill
- atomic-unit-recall-aggregateSkill
- atomic-unit-writingSkill
- claim-label-predictionSkill
- claim-writingSkill
- domain-level-judgmentSkill
- dual-column-self-checkSkill
- engineering-config-gradingSkill
- first-pass-skimSkill
- keshav-three-passSkill
- multi-stage-cascade-extractionSkill
- paper-fetchSkill
- qalmriSkill
- qalmri-worksheetSkill
- qasper-evidence-qaSkill
- question-framingSkill
- rationale-selectionSkill
- reforms-gradingSkill
- reporting-standard-checklistSkill
- reproducibility-third-party-verificationSkill
- research-question-appraisalSkill
- rhetorical-structure-qualitySkill
- second-pass-graspSkill
- signalling-question-answeringSkill
- star-awardingSkill
- study-design-tool-gateSkill
- sum-threshold-scoringSkill
- template-slot-fillingSkill
- third-pass-deep-readSkill
- unit-classificationSkill
- unit-segmentationSkill
- worst-case-lookupSkill
The file
Files
Quality 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) -->Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.