reporting-standard-checklist
Skill1 starsChanged 3 months agoApache-2.0View on GitHub
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.
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
- quality-appraisal-checklistSkill
- question-framingSkill
- rationale-selectionSkill
- reforms-gradingSkill
- 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
Reporting 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) -->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.