CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

quadas-c-assessment-for-diagnostic-accuracy-studies

Automated bias assessment for diagnostic accuracy studies using QUADAS-C criteria. Requires full text input.

Quality

66%

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/quadas-c-assessment-for-diagnostic-accuracy-studies/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 core operational content is solid — an executable script invocation, a clear output format, and a well-signaled reference file holding the detailed signaling questions. However, roughly half the body is templated boilerplate (auto-generated "Key Features"/"Implementation Details" sections, a duplicated When-to-Use list, a date-stamped directory path) that inflates token cost without adding actionable guidance, and the workflow is split between two overlapping sections with only implicit validation checkpoints.

Suggestions

Delete the boilerplate sections ("When to Use" bullet list, "Key Features", "Dependencies", "Implementation Details") and keep only the substantive "When to Use This Skill" conditions; this would cut the body roughly in half.

Remove the date-stamped "20260316/scientific-skills/..." cd path and the py_compile/--help steps; show a real end-to-end run (e.g., extract_pdf.py paper.pdf then quadas_c.py --file extracted.txt) instead.

Fix the "See ## Usage above" reference (Usage is below), add a validation checkpoint after the run (e.g., confirm the JSON contains all four domains with valid Low/High/Unclear values), and merge the two overlapping workflow sections into one.

DimensionReasoningScore

Conciseness

The body is noticeably padded: generic boilerplate sections ("Key Features", "Dependencies", "Implementation Details") add no skill-specific information, the "When to Use" section repeats the frontmatter description nearly verbatim as filler bullets, and a date-stamped path "20260316/scientific-skills/Data Analytics/..." injects time-sensitive cruft. This matches anchor 2 (several unnecessary/padded sections); it is not anchor 1 because the core sections (Usage, Execution, Output Format) are not explaining concepts Claude already knows, and not anchor 3 because the padding spans roughly half the document.

2 / 5

Actionability

Provides an executable command ("python scripts/quadas_c.py --file 'path/to/paper.txt'"), a concrete JSON output schema (P/I/R/FT keys with Low/High/Unclear), a documented PDF extraction helper, and a real references/prompts.md file. Minor gaps keep it below anchor 5: the bash example runs py_compile and --help instead of an actual assessment, the "Example run plan" includes vague conditionals ("if the script uses fixed settings"), and direct command-line text input is mentioned in prose but never shown.

4 / 5

Workflow Clarity

A sequence is present (Extraction → Assessment → Signaling Questions → Risk of Bias → Reporting) plus a run plan with input confirmation and output review, but checkpoints are implicit ("Review the generated output" with no criteria), the steps describe what the script does internally rather than what the agent executes, and the workflow is duplicated across two competing sections ("Example run plan" vs "Usage"). This matches anchor 3 (sequence present, checkpoints missing/implicit) rather than anchor 4's mostly-explicit checkpoints.

3 / 5

Progressive Disclosure

The body appropriately points to a real, one-level-deep reference ("See references/prompts.md for the specific signaling questions and risk of bias criteria") and both referenced scripts exist in the bundle. Minor organization gaps (duplicate "When to Use" / "When to Use This Skill" sections, and a wrong forward reference "See ## Usage above" for a section that appears later) keep it below anchor 5.

4 / 5

Total

13

/

20

Passed

Description

65%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.

The description identifies a distinct, well-scoped niche with strong domain keywords, but it reads as a partial sentence-style capability statement rather than a complete trigger. It lacks an explicit 'use when' clause and omits the multi-action scope (comparing index tests, per-domain risk ratings, structured reporting) that would make it comprehensive.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to assess risk of bias or methodological quality in a diagnostic accuracy study, mentions QUADAS-C/QUADAS-2, or provides a paper comparing two or more index tests."

Include the standard synonym "risk of bias" (not just "bias assessment") and mention the structured JSON report as a concrete deliverable.

Briefly state the comparison aspect (two or more index tests), since that is what distinguishes QUADAS-C from QUADAS-2.

DimensionReasoningScore

Specificity

"Automated bias assessment for diagnostic accuracy studies using QUADAS-C criteria" names the domain and one concrete action (bias assessment), but does not list several specific actions such as comparing index tests, rating per-domain risk, or producing a JSON report. This matches anchor 3 (domain plus 1-2 concrete actions); it falls short of anchor 4's several specific actions and is more concrete than anchor 2's generic domain naming.

3 / 5

Completeness

The "what" is clear (automated QUADAS-C bias assessment), but "Requires full text input" is an input requirement, not an explicit "use when" trigger clause. Per the guideline that a missing 'Use when...' clause caps completeness at 3, this matches anchor 3 (clear what, when only weakly implied) rather than anchor 4.

3 / 5

Trigger Term Quality

Includes strong natural keywords a user in this domain would say: "QUADAS-C", "bias assessment", "diagnostic accuracy studies", "full text". It misses common synonyms such as "risk of bias" and "quality assessment", keeping it just below anchor 5 but above anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

QUADAS-C is a highly specific tool for diagnostic accuracy studies comparing index tests; virtually no other skill would trigger on these terms. This matches anchor 5 (clear niche with distinct triggers, minimal conflict risk).

5 / 5

Total

15

/

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/quadas-c-assessment-for-diagnostic-accuracy-studies/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.