CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roc-diagnostic-performance

Use when evaluating diagnostic biomarker performance from case-control expression data with logistic regression and ROC curves, exporting coefficient and AUC tables together with a ROC PDF. NOT for: survival analysis, time-to-event outcomes, multiclass classification, calibration curves, decision-curve analysis, or nomogram construction.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 is a highly actionable CLI reference with clear workflows and good reference signaling, but it is padded with a bibliography, an implementation checklist, and a version stamp, and it points users at a tests/ directory that is absent from the bundle. Tightening the non-executable sections and fixing or removing the tests/ references would raise it substantially.

Suggestions

Remove the bibliography, 'Implementation Checklist', and 'Last updated / Version' footer — they consume tokens without helping Claude execute the skill.

Fix the bundle/reference mismatch: either include the tests/ tree (tests/data/, tests/run_smoke_test.R, tests/run_smoke_test.sh) or remove the 'With Test Data' example, the tests/data/ row in the file-reading table, and the smoke-test commands.

Move styling-only CLI options (font_family, line_colors, legend_position, etc.) into references/cli-guide.md and keep SKILL.md to the core analysis arguments.

DimensionReasoningScore

Conciseness

The core is efficient dense tables (arguments, formats, outputs, errors), but whole sections add tokens without execution value: the bibliography, the dev-facing 'Implementation Checklist' (e.g. 'CLI parsing with `optparse`', 'requireNamespace() dependency checks'), and a 'Last updated: 2026-04-17 | Version: 2.1.0' line. More than the 'minor instances' of anchor 4, so it sits at 'mostly efficient but could be tightened'.

3 / 5

Actionability

Fully executable copy-paste `Rscript` commands with a complete argument table and multiple worked examples covering the common cases. Not a 5 because the 'With Test Data' example and smoke-test commands reference a `tests/` tree that does not exist in the bundle, so that guidance fails when followed verbatim.

4 / 5

Workflow Clarity

A clear five-step sequence (validate → prepare → fit → compute ROC → save) with input validation as an explicit first step and an error-code table mapping causes to solutions with escalation to troubleshooting. Not a 5: post-run verification is only implied by the expected-output tree, and the checklist documents implementation facts rather than execution checkpoints.

4 / 5

Progressive Disclosure

The 'When to Read External Files' table is well signaled and references are one level deep, and the three references/ files plus scripts/ exist. However, scored against the actual bundle, the repeatedly referenced `tests/data/`, `tests/run_smoke_test.R`, and `tests/run_smoke_test.sh` paths do not exist, making navigation unreliable — worse than anchor 4's 'minor organization gaps' despite better signaling than anchor 3's examples.

3 / 5

Total

14

/

20

Passed

Description

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

An excellent description: concrete third-person actions, an explicit 'Use when...' trigger, and explicit exclusions that sharply bound the skill's scope. The only minor gap is missing a few natural synonyms such as 'receiver operating characteristic' or 'diagnostic model'.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions within its niche — 'evaluating diagnostic biomarker performance', 'logistic regression and ROC curves', 'exporting coefficient and AUC tables together with a ROC PDF' — giving comprehensive coverage of fit, evaluate, and export. It is not a 4 because no meaningful capability of the skill is left uncovered.

5 / 5

Completeness

Both halves are explicit: 'what' (logistic regression + ROC evaluation, exporting coefficient/AUC tables and a ROC PDF) and 'when' ('Use when evaluating diagnostic biomarker performance from case-control expression data...'), plus concrete negative triggers. Matches the anchor-5 example structure; not a 4 because the 'when' clause is fully explicit rather than improvable.

5 / 5

Trigger Term Quality

Strong natural keywords a bioinformatics user would say: 'diagnostic biomarker performance', 'case-control', 'expression data', 'logistic regression', 'ROC curves', 'AUC'. Falls short of a 5 because common synonyms and phrasings like 'receiver operating characteristic', 'diagnostic model', or 'gene expression' are absent.

4 / 5

Distinctiveness Conflict Risk

A clear niche (case-control expression ROC diagnostics) with an explicit 'NOT for:' exclusion list covering survival analysis, multiclass, calibration, decision-curve, and nomogram construction, minimizing the risk of triggering for adjacent biostatistics skills. Distinct triggers, minimal conflict.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

aipoch/medical-research-skills

Path

awesome-med-research-skills/Data Analysis/roc-diagnostic-performance/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.