CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

diagnostic-study-quality-assessment-quadas

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

74%

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/Data Analysis/diagnostic-study-quality-assessment-quadas-2/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 has a solid core — a clear four-domain QUADAS-2 workflow, a mandatory output template, quality rules, and a working PDF extraction script — but it is buried under roughly half a document of auto-generated template boilerplate, a broken example path, a dangling cross-reference ('See ## Workflow above' when Workflow appears below), and placeholder bundle files. The description is strong; the body needs a significant pruning pass and integration of its own bundle.

Suggestions

Delete the auto-generated boilerplate sections ('When to Use' bullets that restate the description, 'Key Features', 'Implementation Details', 'Dependencies' filler) — they consume tokens without adding guidance Claude doesn't already have.

Fix broken navigation: correct 'See ## Workflow above' (Workflow appears below), replace the nonexistent 'cd "20260316/scientific-skills/..."' example with a bundle-relative path, and replace 'copy and send to me' with a direct instruction to extract text and proceed to assessment.

Reconcile the bundle: either wire scripts/quadas_assessment.py into the workflow or remove it, and replace or delete the placeholder files (references/api_reference.md, assets/example_asset.txt) so the only signaled reference is the real criteria document.

Add an explicit completeness check at the end of the workflow (e.g., verify all signaling questions for all four domains are answered with quotes before producing the final report) to convert the implicit validation into a real checkpoint.

DimensionReasoningScore

Conciseness

Large portions of the body are auto-generated boilerplate that adds no guidance: 'When to Use' restates the description almost verbatim across six padded bullets, 'Key Features' is pure meta-fill ('Packaged executable path(s)... plus 1 additional script(s)', 'Reusable packaged asset(s)'), and 'Implementation Details' offers generic filler ('validate the request, choose the packaged workflow, and produce a bounded deliverable'). This matches anchor 2 — several unnecessary padded sections — rather than 3, because the padding occupies roughly half the document and repeats the description rather than explaining concepts Claude doesn't know.

2 / 5

Actionability

The core guidance is executable: numbered per-domain assessment steps, an exact mandatory output template, and runnable commands ('pip install PyPDF2', 'python scripts/pdf_extractor.py "paper.pdf" 5 15') pointing at a real script. Minor gaps keep it below 5: the Example Usage 'cd "20260316/scientific-skills/..."' path doesn't exist in the bundle, scripts/quadas_assessment.py is never used, and 'which you can then copy and send to me' is leftover conversational phrasing.

4 / 5

Workflow Clarity

The assessment sequence itself is listed (four domain steps with a pointer to references/quadas_2_criteria.md) and the Output Format's 'Repeat for all signaling questions' acts as a partial checklist, but checkpoints are otherwise implicit — there is no verification that extraction succeeded or that every signaling question is answered, and the boilerplate 'Example run plan'/'Implementation Details' sections present competing pseudo-workflows that muddy the real path. This sits at anchor 3, not 4, because the validation that exists is implied by formatting rules rather than explicit steps.

3 / 5

Progressive Disclosure

The one substantive reference (references/quadas_2_criteria.md) is clearly signaled and one level deep, but the rest of the bundle is placeholder noise — references/api_reference.md, assets/example_asset.txt, and scripts/quadas_assessment.py are placeholder files referenced only in meaningless boilerplate or not at all, so navigation to real detail is only partially organized. This fits anchor 3 ('could be better organized; references present but not clearly signaled') better than 4.

3 / 5

Total

12

/

20

Passed

Description

87%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 what and when, a concrete example trigger phrase, and a distinct methodological niche. It is only slightly under comprehensive on action/keyword enumeration (no mention of the four QUADAS-2 domains or synonyms like 'critical appraisal').

DimensionReasoningScore

Specificity

The description names the domain ('clinical diagnostic accuracy studies') and several concrete actions — 'analyzes... for bias', 'assess the quality, risk of bias, or applicability' — anchored to a named tool (QUADAS-2). It falls just short of anchor 5 because it doesn't enumerate the tool's four assessment domains or the output deliverable, leaving minor coverage gaps.

4 / 5

Completeness

Both parts are explicit: the 'what' ('Analyzes clinical diagnostic accuracy studies for bias using the QUADAS-2 tool') and the 'when' ('Use when Claude needs to assess the quality, risk of bias, or applicability... e.g., "Assess this paper using QUADAS-2"'), matching the anchor-5 pattern of what + when with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Natural trigger phrases are present: 'QUADAS-2', 'diagnostic accuracy studies', 'risk of bias', 'applicability', and a concrete example utterance ('Assess this paper using QUADAS-2'). A few natural synonyms users might say ('critical appraisal', 'study quality') are missing, so it fits anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

QUADAS-2 is a highly specific, named methodology for diagnostic accuracy studies — a clear niche with distinct triggers and minimal overlap risk with generic literature-review or PDF skills.

5 / 5

Total

18

/

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/Data Analysis/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.