CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

case-control-study-quality-assessment-nos

Clinical Research Bias Assessment - Case-Control Study (NOS) v2.3.0. Use when you need to assess the bias of a case-control study using the Newcastle-Ottawa Scale (NOS) criteria, or when evaluating the quality of a medical paper.

Quality

65%

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/Case-control-study-quality-assessment-nos/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

38%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 body has a legitimate core workflow (NOS three-domain evaluation with script-based formatting), but it is buried in generic template boilerplate, its evaluation criteria and both scripts are delegated to files that are absent from the bundle, and no concrete example of the aggregated JSON or scoring rubric appears inline. As shipped, the skill cannot be executed as documented.

Suggestions

Ship the referenced bundle files (`references/nos_criteria_prompts.md`, `scripts/extract_pdf.py`, `scripts/format_nos_table.py`) or remove all references to them and inline the NOS criteria for the Selection, Comparability, and Exposure domains.

Cut the template filler — Key Features, Example Usage ("See `## Usage` above"), Recommended Workflow, Required Inputs, Output Contract, and Validation and Safety Rules add no NOS-specific information; consolidate the real workflow (Usage + Detailed Workflow + Helper Scripts) into one section.

Add a concrete example of the aggregated JSON passed to `python scripts/format_nos_table.py '<json_string>'` and show the expected summary-table output, replacing the placeholder and the environment-specific `cd "20260316/..."` path.

DimensionReasoningScore

Conciseness

Noticeably verbose with several padded template sections: "Key Features" restates the description verbatim, "Example Usage" says only "See `## Usage` above for related details", and "Use this skill when the request matches its documented task boundary" is circular filler. Generic boilerplate (Recommended Workflow, Output Contract, Validation and Safety Rules, Failure Handling, Required Inputs) adds tokens without NOS-specific knowledge. It is template padding rather than explanation of known concepts, so it fits anchor 2 rather than anchor 1's 'extensively explains concepts Claude already knows'.

2 / 5

Actionability

Some concrete guidance exists — real commands (`python scripts/extract_pdf.py --help`, `python scripts/format_nos_table.py '<json_string>'`) and a four-step usage sequence — but key details are missing: the actual NOS criteria are delegated to `references/nos_criteria_prompts.md` which does not exist in the bundle, `'<json_string>'` is a placeholder with no example JSON, and the `cd "20260316/scientific-skills/..."` path is environment-specific. This matches anchor 3 ('some concrete guidance but incomplete ... missing key details'), not anchor 4 whose gaps would be minor.

3 / 5

Workflow Clarity

A clear sequence is present (extract metadata → evaluate Selection/Comparability/Exposure → synthesize JSON → format table), but checkpoints are missing or implicit between steps: Steps 1-3 say only "Evaluate the domain" with criteria in a nonexistent file, and the validation text ("Run a final validation pass for completeness, consistency, and safety") is generic template language rather than a real checkpoint tied to the workflow. This fits anchor 3 rather than anchor 4's explicit per-step verify steps.

3 / 5

Progressive Disclosure

The body signals one-level-deep references (`references/nos_criteria_prompts.md`, `scripts/extract_pdf.py`, `scripts/format_nos_table.py`), but the bundle contains no references/, scripts/, or assets/ directories — every referenced path is dangling, so the promised navigation leads nowhere. Structure exists in name only, and the inline template sections are content that belongs in separate files or nowhere. Scored against the actual (empty) bundle structure, this is a broken reference graph, matching anchor 2 rather than anchor 3's 'references present but not clearly signaled'.

2 / 5

Total

10

/

20

Passed

Description

78%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 with an explicit and specific 'Use when...' clause, good natural trigger terms, and a clearly named domain and instrument. Main weaknesses are limited action coverage (only one truly concrete capability is named) and a slightly over-broad secondary trigger around generic medical-paper quality evaluation.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ("assess the bias of a case-control study using the Newcastle-Ottawa Scale (NOS) criteria"), plus a second vaguer one ("evaluating the quality of a medical paper"). It is not comprehensive — the actual workflow steps (evaluate Selection/Comparability/Exposure domains, generate a summary table) are absent, and the "v2.3.0" version tag is administrative padding. It lists domain + 1-2 concrete actions without comprehensive coverage, matching anchor 3 rather than anchor 4's 'several specific actions'.

3 / 5

Completeness

Explicitly answers both: what ("assess the bias of a case-control study using the Newcastle-Ottawa Scale (NOS) criteria") and when ("Use when you need to assess the bias of a case-control study ... or when evaluating the quality of a medical paper") with concrete trigger phrases. It contains an explicit 'Use when...' clause so the cap at 3 does not apply, and the when-clause is specific enough to exceed anchor 4's 'could be more explicit'.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "bias", "case-control study", "Newcastle-Ottawa Scale", "NOS", "quality of a medical paper" — phrases users would plausibly say. A few common synonyms are missing ("critical appraisal", "risk of bias", "study quality"), which keeps it below anchor 5 but comfortably above anchor 3's 'missing common variations'.

4 / 5

Distinctiveness Conflict Risk

The NOS case-control framing is a clear, mostly distinct niche, but the secondary trigger "evaluating the quality of a medical paper" is broad and could fire for non-case-control designs or overlap with closely related quality-appraisal skills (e.g., a cohort-study NOS sibling skill), matching anchor 4's 'minor overlap risk with closely related skills'.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 missing

Warning

referenced_paths_exist

Referenced path issues: 11 missing

Warning

Total

13

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Data Analysis/Case-control-study-quality-assessment-nos/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.