CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

quapas-quality-assessment-for-prognosis-studies

Evaluates bias in medical literature (prognosis studies) using QUAPAS criteria. Use when the user wants to assess the quality or risk of bias of a medical paper text.

Quality

68%

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/quapas-quality-assessment-for-prognosis-studies/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 core Workflow section is genuinely good — explicit decision rules, a defined 5-domain structure, and a strict JSON output schema, with real one-level-deep bundle files. However, roughly 40% of the body is generic template boilerplate ('When to Use', 'Key Features', 'Implementation Details'), the helper-script section is truncated mid-sentence, and the overall-judgment rule relies on an undefined 'key domains' notion.

Suggestions

Delete the boilerplate 'When to Use' bullets 3-6, 'Key Features', and 'Implementation Details' sections — they restate generic process language and duplicate the frontmatter description, roughly halving token cost.

Complete the truncated 'Helper Scripts' section with actual extract_pdf.py usage (e.g., `python scripts/extract_pdf.py paper.pdf --output extracted.txt`) instead of ending mid-sentence.

Replace 'If key domains are High Risk' with an explicit rule naming which domains are decisive for the overall judgment, and add a final validation step that checks the output JSON against the schema.

DimensionReasoningScore

Conciseness

Several padded, template-generated sections add no skill-specific value: 'When to Use' bullets like 'when a data analytics task needs a packaged method instead of ad-hoc freeform output' and 'when the user expects a concrete deliverable', the generic 'Key Features' and 'Implementation Details' sections (e.g., 'Output discipline: keep results reproducible...'), and a duplicated '## Description' section that restates the frontmatter. Roughly 40% of the body is boilerplate — matching 'noticeably verbose; several unnecessary explanations or padded sections'. Not a 1 because the Workflow section itself is dense and non-generic.

2 / 5

Actionability

The Workflow provides executable decision rules ('If all answers are "Yes" -> Low Risk', 'If any answer is "No" -> High Risk') and a strict JSON output schema, and Example Usage gives runnable commands (`python -m py_compile scripts/extract_pdf.py`). Falls short of 5 because 'key domains' in the overall judgment is undefined and the 'Helper Scripts' section is truncated mid-sentence ('before assessment:') with no usage shown; above 3 because the core assessment path is fully specified.

4 / 5

Workflow Clarity

The 6-step Workflow is clearly sequenced (input -> study extraction -> domain analysis -> ROB assessment -> overall judgment -> JSON output) with explicit per-domain decision rules acting as checkpoints. Not a 5: the overall-judgment criteria are vague ('If key domains are High Risk' — which domains are key?) and no step validates the final JSON against the schema. This is an assessment skill, not a destructive/batch operation, so the validation cap does not apply.

4 / 5

Progressive Disclosure

Scored against the actual bundle: the body delegates signaling questions to references/quapas_prompts.md and PDF handling to scripts/extract_pdf.py, both real files referenced one level deep with a clearly signaled References link — good structure with minor gaps. Not a 5 because the 'Implementation Details' bullet ('references/ contains supporting rules, prompts, or checklists') is vague filler rather than a precise per-file pointer, and the domain list is inlined twice.

4 / 5

Total

14

/

20

Passed

Description

62%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 solid description: third-person voice, explicit 'Use when...' clause, and a clearly named niche (QUAPAS / prognosis studies). Its weaknesses are limited action coverage — it describes evaluating bias but not the concrete verdict deliverable — and missing common trigger synonyms like 'critical appraisal'.

Suggestions

Mention the concrete deliverable in the description (e.g., 'outputs a per-domain Low/High/Unclear risk-of-bias judgment as JSON') to raise specificity.

Add trigger synonyms users would naturally say, such as 'critical appraisal', 'quality assessment of a study', or 'prognostic/cohort study', to improve trigger term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('medical literature (prognosis studies)') and one concrete action ('Evaluates bias ... using QUAPAS criteria'), matching the anchor for 1-2 concrete actions without comprehensive coverage — it never mentions the deliverable (per-domain Low/High/Unclear verdicts) or the 5-domain structure. Not a 4 because no additional specific actions are listed; not a 2 because the action and domain are both named concretely.

3 / 5

Completeness

It explicitly answers both what ('Evaluates bias in medical literature (prognosis studies) using QUAPAS criteria') and when ('Use when the user wants to assess the quality or risk of bias of a medical paper text'), in third person. Not a 5 because the 'when' clause is a single generic trigger rather than concrete trigger phrases/synonyms; well above a 3 since the 'when' is explicit, not weakly implied.

4 / 5

Trigger Term Quality

Phrases like 'prognosis studies', 'risk of bias', 'quality', and 'medical paper text' are natural terms, but common variations are missing — 'critical appraisal', 'systematic review', 'cohort/prognostic study', or any file-extension triggers. This matches 'some relevant keywords but missing common variations or synonyms'; it lacks the near-synonym coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

QUAPAS plus 'prognosis studies' carves a clear niche with distinct triggers, but 'Evaluates bias in medical literature' broadly overlaps with closely related appraisal skills (e.g., diagnostic-accuracy tools like QUADAS), matching 'mostly distinct; minor overlap risk'.

4 / 5

Total

14

/

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/quapas-quality-assessment-for-prognosis-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.