CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

diagnostic-study-quality-assessment-quadas-2

Analyzes clinical diagnostic accuracy studies for bias using the QUADAS-2 tool. Use when Claude needs to assess the quality, risk of bias, or applicability of diagnostic accuracy studies (e.g., "Assess this paper using QUADAS-2").

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/diagnostic-study-quality-assessment-quadas-2/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill's functional core is strong: a clear four-domain QUADAS-2 workflow, a concrete output contract, strict evidence rules, and working PDF-extraction commands. However, nearly half of the body is generic validation/contract boilerplate that wastes context, and the bundle ships two placeholder files (api_reference.md, quadas_assessment.py) that are never referenced, undermining an otherwise clean progressive-disclosure structure.

Suggestions

Cut or drastically condense the generic boilerplate sections (Input Validation, When to Use/Not to Use, Required Inputs, Output Contract, Failure Handling, User Checkpoints, Quick Validation) into a few lines — they restate process behavior Claude already applies and consume roughly half the body's tokens.

Fix the PDF Parsing section's multi-turn phrasing ('which you can then copy and send to me') so the extraction step integrates unambiguously into the assessment workflow, and mention scripts/quadas_assessment.py (or delete it) so the whole bundle is discoverable.

Replace the placeholder references/api_reference.md template text with real content, remove it, or link it from the References section so no orphaned filler files remain in the bundle.

DimensionReasoningScore

Conciseness

Beyond the genuinely useful core (Workflow, Output Format, Quality Rules, PDF Parsing Tool), roughly half the body is generic template boilerplate — "Input Validation", "When to Use", "When Not to Use", the "Required Inputs" table, "Output Contract", "Failure Handling", "User Checkpoints", and "Quick Validation" — which restates obvious process rules Claude already follows (e.g., "Do not proceed when required input files... are missing — ask the user to provide them first"). This matches 'noticeably verbose; several unnecessary explanations or padded sections'; it is above 1 because the core sections themselves are tight and free of concept explanations.

2 / 5

Actionability

The guidance is concrete and executable: four workflow steps with specific checks ("Assess if the sample was consecutive or random", "Check for case-control design"), a fully specified output template with Yes/No/Unclear answers, and copy-paste commands ("pip install PyPDF2", "python scripts/pdf_extractor.py \"paper.pdf\" 5 15") — matching 'mostly executable guidance... with minor gaps'. It is not 5 because the PDF section's instruction to copy extracted text "and send to me" is confusing multi-turn phrasing, and the bundled scripts/quadas_assessment.py is never mentioned despite existing.

4 / 5

Workflow Clarity

The four-domain sequence is clearly numbered and each step names its checks and points to references/quadas_2_criteria.md, with output structure and strictness rules defined ("If information is missing, select 'Unclear'. Do not guess.") — 'clear sequence with most checkpoints present'. It is not 5 because validation is confined to generic boilerplate (Quick Validation) rather than an integrated step, and the PDF-extraction step's relation to the assessment workflow (copy text "and send to me") is ambiguous; it is above 3 because the sequence itself has no real gaps and no risky operations lack checks.

4 / 5

Progressive Disclosure

Content is appropriately split: detailed signaling questions live in references/quadas_2_criteria.md (clearly signaled in both the workflow and a References section), and script usage is inline — 'good structure; most content appropriately placed'. It is not 5 because the bundle contains two orphaned placeholder files never referenced in the body (references/api_reference.md, which is unfilled template text, and scripts/quadas_assessment.py), a minor organization gap in bundle hygiene.

4 / 5

Total

14

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person voice, explicit 'Use when' trigger with an example user utterance, a named domain and tool, and enumeration of the tool's assessment targets. Main residual weaknesses are missing common synonyms (critical appraisal, validity, PDF/PMID inputs) and slight overlap risk with generic quality-appraisal requests.

DimensionReasoningScore

Specificity

The description lists several specific actions — "Analyzes clinical diagnostic accuracy studies for bias", "assess the quality, risk of bias, or applicability" — tied to a named tool (QUADAS-2), matching the 'several specific actions; minor gaps' anchor. It is not a 5 because coverage is limited to the assessment act itself; the tool's domain-level output structure (four domains) is not conveyed, though that is a minor gap for a description.

4 / 5

Completeness

It clearly answers both questions: the 'what' ("Analyzes clinical diagnostic accuracy studies for bias using the QUADAS-2 tool") and an explicit 'when' with concrete trigger phrases ("Use when Claude needs to assess the quality, risk of bias, or applicability of diagnostic accuracy studies (e.g., 'Assess this paper using QUADAS-2')"), matching the top anchor exactly. It is not a 4 because the 'when' clause is already explicit and includes a quoted example trigger, not merely implied or generic.

5 / 5

Trigger Term Quality

Natural user phrases are present: "assess the quality", "risk of bias", "diagnostic accuracy studies", "QUADAS-2", plus a concrete example utterance ("Assess this paper using QUADAS-2") — good keyword coverage per the anchor. It falls short of 5 because common synonyms users actually say, such as "critical appraisal", "validity", "test accuracy", or input types like PDF/PMID, are missing.

4 / 5

Distinctiveness Conflict Risk

QUADAS-2 and "diagnostic accuracy studies" carve out a clear niche with distinct triggers, so conflict risk is low — matching 'mostly distinct; minor overlap risk'. It is not a 5 because generic quality-appraisal phrasing ("assess the quality" of a study) could overlap with other critical-appraisal or risk-of-bias skills (e.g., Cochrane RoB) since no exclusionary framing distinguishes those sibling tools.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/diagnostic-study-quality-assessment-quadas-2/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.