CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

prognostic-biomarker-protocol-designer

Designs discovery, modeling, and validation workflows for prognostic biomarkers in biomedical and clinical research. Always use this skill when the user needs a prognostic biomarker study blueprint rather than a diagnostic test protocol, predictive biomarker design, treatment recommendation, or a completed manuscript. Focus on endpoint family, follow-up horizon, time scale, candidate marker strategy, model-building logic, risk stratification framework, and internal/external validation requirements. Do not invent cohort size, event rate, assay readiness, literature support, or validation access.

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

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

A well-structured expert workflow skill: crisp 10-step sequence, fixed A–L output contract, and exemplary progressive disclosure with all 11 referenced modules verified on disk. The main weakness is token efficiency — the same rules are restated across the distinctions list, Core Function, Execution, Hard Rules, and the 'should not' sections — and the absence of any worked example or final output-verification step.

Suggestions

Consolidate redundant rule statements: the "must distinguish between" list, Core Function "should not" list, Hard Rules, and "What This Skill Should Not Do" repeat the same prohibitions (post-baseline predictors, univariable sufficiency, assumed external validation, unvalidated cutoffs) — state each once in Hard Rules and reference it, cutting 30–40% of the body.

Merge the Execution Steps 1–10 with the Mandatory Output Structure A–L (or make one a compact map of the other) since both currently encode the same section-to-reference-module mapping three times (Reference Module Integration, Execution, and Output Structure).

Add a final output-verification checkpoint (e.g., 'Before delivering, confirm all sections A–L are present, every assumption-dependent item is labeled, and one lead protocol version is named') and optionally a short worked example of one filled-in section to make the output contract fully concrete.

DimensionReasoningScore

Conciseness

Almost every line carries domain-specific design constraints (no space is wasted teaching Claude what biomarkers or survival analysis are), but the ~420-line body restates the same rules repeatedly: the "must distinguish between" list, Core Function (10 items), Execution Steps 1–10, Hard Rules, and "What This Skill Should Not Do" each restate overlapping prohibitions (e.g., post-baseline predictor bias and unverified external validation appear in 3–4 places), and the Execution steps largely mirror the A–L Mandatory Output Structure. This is 'mostly efficient but could be tightened' rather than a 2, since the redundancy is rule-restatement, not explanation of known concepts — but consolidation could cut 30–40% of tokens.

3 / 5

Actionability

For an instruction-only skill the guidance is concrete: every Execution step specifies exactly what to "State" (e.g., Step 3 lists primary endpoint, time origin, follow-up horizon, censoring logic), the Mandatory Output Structure fixes sections A–L with per-section content contracts, and the Clarification Rule bounds questions to "2–6 concise, high-yield follow-up questions". It misses a 5 because some directives remain abstract ("Lead with one coherent main line") and there is no worked example (e.g., a short filled-in sample of sections A–L for one cohort) to anchor the expected output shape.

4 / 5

Workflow Clarity

The 10-step execution sequence is explicit, each step is mapped to a specific reference module and to output sections, and there are genuine checkpoints: input validation with a redirect-and-stop script, a clarification gate before locking the design, and audit steps (Step 8 leakage/overfitting review, Step 9 translation-readiness check). It falls short of 5 because there is no final verify-your-output step (e.g., 'confirm every A–L section is present and assumption-dependent items are labeled before delivering'), so the feedback loop stops at design-time audits rather than output validation.

4 / 5

Progressive Disclosure

The Reference Module Integration section explicitly signals all 11 reference files with one-level-deep paths, assigns each a precise 'use when' condition tied to specific sections/steps, and all 11 files verified present in references/. The body holds the workflow while the rules live in the bundle files — matching the 'clear overview with well-signaled one-level-deep references' anchor; the guard clause ("If any output section is generated without using its corresponding reference module... incomplete") reinforces navigation.

5 / 5

Total

16

/

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' with concrete trigger phrases, and explicit disambiguation from diagnostic/predictive/treatment-use skills. Keyword coverage is good though a few natural synonyms (survival, recurrence, prognosis) would improve triggering.

DimensionReasoningScore

Specificity

The description names concrete capabilities — "Designs discovery, modeling, and validation workflows for prognostic biomarkers" — and enumerates specific design facets ("endpoint family, follow-up horizon, time scale, candidate marker strategy, model-building logic, risk stratification framework, and internal/external validation requirements"). It falls short of a 5 because the actions collapse into one verb ("designs") applied to a focus list, with no per-stage actions, and it is not below 4 since several specific, distinguishable capabilities are explicitly stated.

4 / 5

Completeness

It explicitly answers both questions: the 'what' ("Designs discovery, modeling, and validation workflows for prognostic biomarkers in biomedical and clinical research") and the 'when' with a concrete trigger clause ("Always use this skill when the user needs a prognostic biomarker study blueprint rather than a diagnostic test protocol, predictive biomarker design..."). The 'when' clause even includes disambiguating anti-triggers, matching the 5 anchor exactly; 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Natural trigger phrases are present: "prognostic biomarker study blueprint", "diagnostic test protocol", "predictive biomarker design", "risk stratification", "validation". A few natural synonyms users would plausibly say are missing (e.g., "survival", "recurrence", "prognosis", "outcome model"), which fits the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche and actively de-conflicts against the nearest competing skills ("rather than a diagnostic test protocol, predictive biomarker design, treatment recommendation, or a completed manuscript"), plus boundary constraints ("Do not invent cohort size, event rate, assay readiness..."). Minimal conflict risk with adjacent biomarker-use skills, matching the 5 anchor; 4 would require minor overlap risk that is not evident.

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

awesome-med-research-skills/Protocol Design/prognostic-biomarker-protocol-designer/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.