agentleFS
yogsoth-aiyogsoth-ai/paper-reading/skills/study-design-tool-gate/SKILL.md

study-design-tool-gate

Skill1 starsChanged 3 months agoApache-2.0View on GitHub

Classify a paper's study design (RCT, cohort, case-control, diagnostic-accuracy, systematic-review, animal-study, prediction-model, etc., or not_applicable) and dispatch to the correct downstream bias-risk/quality/reporting tool and specific variant (CASP has 8 variants, JBI ~6, RoB2 has parallel/cluster/crossover versions). Use this as the mandatory first step before running ANY of CASP, JBI, AMSTAR-2, NOS, RoB2, ROBINS-I, QUADAS-2, CONSORT, STROBE, ARRIVE, SPIRIT, TRIPOD, or engineering-config-grading — these tools are all study-design-conditional and picking the wrong variant produces meaningless results. It is entirely correct and common for this gate to determine that none of these medically-descended tools applies (e.g. most CS/ML papers) — that is a valid, complete answer, not a failure.

The file

Files
SKILL.md

Study Design Tool Gate

Classifies study design and dispatches to the right bias-risk/quality/reporting tool + variant — or determines none applies. Added per coverage-audit M11: the original graph had no node representing this dispatch decision at all; every A1/A2 tool was drawn as if it started with no gate.

Execution

Subagent — spawned via spawn-agent skill.

Reference

references/tool-dispatch-table.md — the full dispatch table (every study_design → tool + variant mapping). Read before drafting the prompt's decision, not summarized inline here (kept out of this SKILL.md body per Progressive Disclosure).

"not_applicable" Is a Correct, Common Answer

This is worth restating: most of these tools carry medical/clinical assumptions baked into their domains, and forcing a dispatch onto a paper that has no matching study design produces a meaningless result, not a conservative one. Do not treat a high not_applicable rate across a batch of CS/ML papers as a sign this SOP is failing to trigger correctly.

<!-- BEGIN available-tables (generated) -->

Available SOPs

SOPWhen to use
spawn-agentSpawn a customized CC subagent with full MCP tool access.
<!-- END available-tables (generated) -->

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.