CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

biomarker-landscape-scanner

Scans the biomarker landscape of a disease area by biomarker type, clinical/research use case, evidence layer, validation status, and maturity level. Use this skill when a user wants a field-level biomarker evidence map rather than a generic literature summary. Always separate exploratory biomarkers from externally validated or clinically embedded biomarkers, and never imply clinical maturity without explicit evidence support.

Quality

78%

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 ./awesome-med-research-skills/Evidence Insight/biomarker-landscape-scanner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 delivers a highly actionable, well-sequenced analysis workflow with excellent checkpointing and a genuine, well-signaled reference bundle. Its main weakness is token redundancy: duplicated trigger examples and prohibition lists that restate hard rules across multiple sections inflate the skill's size without adding guidance.

Suggestions

Consolidate the duplicated trigger-example lists ('Input Validation' examples and 'Sample Triggers') into one section, and merge 'What This Skill Should Not Do' into the 'Core Function should not' list to remove repeated prohibitions.

Trim Hard Rules 13–17, which restate rules already specified in Step 2, Step 8, and Section J, into a short cross-reference or fold them into the sections where they first appear.

Add one brief worked example of a filled Section C biomarker entry to push actionability to fully executable coverage of the common case.

DimensionReasoningScore

Conciseness

The body is dense and directive with no concept-explanation padding, but contains real redundancy: trigger examples are duplicated across 'Input Validation' and 'Sample Triggers', the 'Core Function should not' list is restated in 'What This Skill Should Not Do', and Hard Rules 13–17 restate rules already given in Step 2, Step 8, and Section J (fabrication bans appear three to four times). Mostly efficient, but could be tightened — it is not anchor 2 because there is no filler or generic explanation, and not anchor 4 because the duplication exceeds minor instances.

3 / 5

Actionability

Eight ordered steps, a field-by-field mandatory output structure (Sections A–J), a precise five-tier maturity table with minimum evidence standards, exact copy-paste fallback strings, and a ready-to-use out-of-scope redirect quote make the guidance highly executable for an instruction-only skill. The minor gap is the absence of a worked example of a filled Section C biomarker entry, keeping it at anchor 4 rather than 5.

4 / 5

Workflow Clarity

'Execution — 8 Steps (always run in order)' provides a clear sequence with explicit checkpoints and feedback loops: a scope-check gate with mode branching (Step 1.5), a self-critical review checklist before the recommendation (Step 8), citation-certainty labeling gates, and a retrieval-fallback path when live literature access is unavailable. This matches the anchor for explicit validation steps, error-recovery loops, and checklists; it is not a destructive or batch operation, so no cap applies.

5 / 5

Progressive Disclosure

Eight real, one-level-deep reference files are clearly signaled in a dedicated 'Reference Module Integration' section that maps each file to the specific sections where it applies, and all referenced paths exist in the bundle. Minor duplication — the inline maturity table and Mandatory Output Structure overlap content in biomarker-maturity-framework.md and output-section-guidance.md — keeps this at anchor 4 rather than a fully clean split.

4 / 5

Total

16

/

20

Passed

Description

75%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 a clear what, an explicit use-when clause, good natural trigger terms, and a distinctive niche. Its main limitation is a single-condition when-clause and a one-verb capability framing that keeps it just short of the top anchors.

DimensionReasoningScore

Specificity

The description names the domain and several concrete capability dimensions — 'by biomarker type, clinical/research use case, evidence layer, validation status, and maturity level' plus 'Always separate exploratory biomarkers from externally validated or clinically embedded biomarkers' — but is framed around a single scan verb rather than multiple distinct concrete actions, leaving minor coverage gaps versus the comprehensive anchor.

4 / 5

Completeness

It clearly answers 'what' (scans by type, use case, evidence layer, validation status, maturity level) and has an explicit 'Use this skill when...' clause ('when a user wants a field-level biomarker evidence map rather than a generic literature summary'). The when-clause covers a single trigger condition and could be more explicit about additional trigger situations, so it sits at anchor 4 rather than 5.

4 / 5

Trigger Term Quality

'biomarker landscape', 'evidence map', 'validation status', and 'maturity level' are natural phrasings a user would say when needing this skill. Coverage is good but a few common natural variations (e.g., 'which biomarkers are validated', 'promising biomarkers', 'biomarker maturity') are absent from the trigger framing.

4 / 5

Distinctiveness Conflict Risk

The biomarker-evidence-mapping niche is clear with distinct triggers ('field-level biomarker evidence map'), but there is minor overlap risk with closely related medical-research skills in the same family (e.g., evidence-level-ranker and translational opportunity finder referenced in the body), matching 'mostly distinct; minor overlap risk'.

4 / 5

Total

16

/

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/Evidence Insight/biomarker-landscape-scanner/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.