CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mechanism-to-validation-planner

Extends a mechanistic or association-level biomedical finding into a staged validation pathway that moves from descriptive evidence toward stronger functional support, mechanistic specificity, and clinical relevance. Use this skill when a user has a pathway, biomarker, cell-state, target, mechanism, or association finding and needs to decide what should be validated next, in what order, and which evidence layers are necessary versus optional. Do not default to maximal validation stacks. Build a structured validation ladder with a primary route, stronger upgrade route, and optional extensions.

Quality

84%

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 skill is well structured and actionable — a clear staged workflow with an excellent reference-module architecture — but the body carries significant duplicate content across Core Function, Hard Rules, 'What This Skill Should Not Do', and 'Quality Standard', roughly doubling its token cost without adding new guidance. Trimming the redundancy would raise conciseness to match the other dimensions.

Suggestions

Collapse 'What This Skill Should Not Do' and 'Quality Standard' into Hard Rules (or vice versa) — the three sections restate the same negative constraints and quality criteria nearly verbatim.

Delete or shrink 'Sample Triggers', which duplicates the frontmatter description's trigger examples and adds no new operational guidance.

Merge 'Core Function' with the 'Decision Logic' steps, since the ten numbered items restate the ten steps one section later.

DimensionReasoningScore

Conciseness

The body systematically repeats the same rules: 'never confuse repeated association with functional validation' appears in the intro, Core Function, Hard Rules, and 'What This Skill Should Not Do'; the 'What This Skill Should Not Do' and 'Quality Standard' sections largely restate 'This skill should not' and Hard Rules 1–15, and Sample Triggers duplicates the frontmatter description. This matches the 2 anchor ('several unnecessary explanations or padded sections') rather than 3, since redundancy is structural across at least four sections rather than occasional.

2 / 5

Actionability

For an instruction-only skill the guidance is concrete: ten named decision steps, route types with explicit trigger conditions ('association-reinforcement-first → when the finding is thin, single-context…'), a fixed A–J output structure, and a literal out-of-scope redirect script. It falls short of 5 because no worked example or model output snippet grounds the sections.

4 / 5

Workflow Clarity

The 10-step decision sequence is clear, ordered, and each step is mapped to a reference module and output section, with Hard Rule 14 and the reference-module completeness rule acting as validation checkpoints. It is 4 rather than 5 because those checkpoints are scattered across sections instead of forming an explicit end-of-run verification phase.

4 / 5

Progressive Disclosure

The body delegates rule detail to ten real, one-level-deep reference files, each explicitly signaled with its purpose and point of use ('use when classifying the dominant type of finding in Section B'), and all referenced paths exist in the bundle. This matches the 5 anchor: clear orchestration overview with well-signaled references and easy navigation.

5 / 5

Total

15

/

20

Passed

Description

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

The description is strong: third-person voice, concrete multi-action capability statement, an explicit 'Use this skill when…' trigger clause with the natural terms users would say, and a clearly bounded niche. It closely matches the rubric's good examples in both structure and specificity.

DimensionReasoningScore

Specificity

The description lists multiple concrete, distinct actions — 'Extends a mechanistic or association-level biomedical finding into a staged validation pathway', 'decide what should be validated next, in what order', and 'Build a structured validation ladder with a primary route, stronger upgrade route, and optional extensions' — comprehensively covering the skill's scope. It matches the 5 anchor rather than 4 because there are no notable coverage gaps.

5 / 5

Completeness

Both 'what' (extends a finding into a staged validation pathway) and 'when' ('Use this skill when a user has a pathway, biomarker, cell-state, target, mechanism, or association finding and needs to decide what should be validated next') are explicitly and concretely stated, matching the 5 anchor with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user phrasings are well covered: 'pathway, biomarker, cell-state, target, mechanism, or association finding' and 'what should be validated next' are exactly what a biomedical researcher would say. No relevant synonyms are missing (file extensions do not apply to this skill type).

5 / 5

Distinctiveness Conflict Risk

The niche is clearly delimited ('mechanistic or association-level biomedical finding' validation planning) with distinct triggers, so overlap risk with adjacent skills (general literature review, protocol generation) is minimal — the description even states what it does not do ('Do not default to maximal validation stacks').

5 / 5

Total

20

/

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/mechanism-to-validation-planner/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.