CtrlK
BlogDocsLog inGet started
Tessl Logo

validation-strategy-designer

Designs internal, external, temporal, and functional validation strategies at the protocol stage for medical research studies.

51

Quality

64%

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/Protocol Design/validation-strategy-designer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 body delivers a well-sequenced, genuinely actionable design workflow with a strong clarification gate and a concrete mandatory output structure, and its reference bundle is real, one-level-deep, and clearly signaled. Its main weakness is heavy internal duplication — the same rules and tier lists are repeated across four or more sections and again in the reference files — which wastes context tokens.

Suggestions

Consolidate the validation tier list to a single appearance (in references/validation-tier-framework.md) and reference it from Task and Step 3 instead of restating it three times.

Deduplicate the overlapping prohibition sections — Scope Boundary, Important Distinctions, What This Skill Should Not Do, and Hard Rules — into one canonical section plus references/hard-rules.md, cutting the body roughly in half.

Add a short worked example (a sample validation-planning memo for a typical biomarker study) to lift actionability by covering the most common case end-to-end.

DimensionReasoningScore

Conciseness

The body is noticeably verbose with several padded, duplicated sections: the validation tier list appears in "Task", again in "Step 3", and again in references/validation-tier-framework.md; the 12 "Hard Rules" duplicate references/hard-rules.md; "Input Validation" restates Step 1; and "Scope Boundary", "Important Distinctions", "What This Skill Should Not Do", and "Hard Rules" each restate the same prohibitions (e.g., do-not-invent-experiments and internal-vs-external separation each appear 4+ times). This is more than 'some unnecessary explanation', fitting the noticeably-verbose anchor rather than the mostly-efficient one.

2 / 5

Actionability

For an instruction-only skill, the guidance is concrete and executable: a named 8-step execution flow, an explicit tier classification scheme (necessary/recommended/optional/not currently justified), a three-way resource triage (available/obtainable/unavailable), and a mandatory A-L output structure defining exactly what each section must contain. It falls short of fully-executable because no worked example (e.g., a sample validation memo for a biomarker study) covers the common cases.

4 / 5

Workflow Clarity

The 8-step sequence is clearly ordered with an explicit clarification gate up front (Step 1: ask targeted questions before generating a long answer), an evidence-boundary review step (Step 7), and a mandatory self-critical risk review (Section L) acting as a checklist. Minor gaps remain — there is no explicit re-check loop after resource mapping, and Step 5/6 outputs are described but not verified against the claim — so it sits at 'clear sequence with most checkpoints present' rather than the explicit feedback-loop anchor.

4 / 5

Progressive Disclosure

All 5 referenced files exist in references/ and are one level deep, clearly signaled in a dedicated "Reference Module Integration" section with per-file usage guidance — better than typical signaling. However, the body inlines substantial content that already lives in the bundle files (the tier lists and hard rules are duplicated nearly verbatim), so organization is good but not the clean split of the top anchor.

4 / 5

Total

14

/

20

Passed

Description

53%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 clearly states what the skill does and names its domain with a decent set of domain-specific terms, but it lacks any 'use when' trigger guidance and misses the natural phrasings a researcher would actually use. It is serviceable but under-performs its potential for discoverability and disambiguation.

Suggestions

Append an explicit trigger clause, e.g. "Use when designing validation plans for biomarker, prognostic, or translational studies, or when deciding whether external or functional validation is needed."

Include natural user phrasings such as "external cohort", "validation plan", "how should I validate this biomarker" to improve trigger term quality.

Add a second concrete action verb (e.g., "classifies validation tiers as necessary, recommended, optional, or not justified") to raise specificity from one action to several.

DimensionReasoningScore

Specificity

The description names the domain ("medical research studies") and one concrete action ("Designs ... validation strategies") with enumerated validation types (internal, external, temporal, functional), matching the anchor for naming a domain with 1-2 concrete actions. It stays at 3 rather than 4 because only a single action verb is offered and coverage of what the skill actually does (classify tiers, define minimum packages, review evidence boundaries) is not present.

3 / 5

Completeness

The 'what' is clearly stated ("Designs internal, external, temporal, and functional validation strategies at the protocol stage"), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Relevant keywords exist ("validation strategies", "protocol stage", "medical research", "external validation") but they are formal/technical phrasings. Common natural variations users would say — "biomarker study", "do I need an external cohort", "validation plan", "study design" — are missing, so the anchor for some relevant keywords with missing synonyms applies.

3 / 5

Distinctiveness Conflict Risk

The protocol-stage validation niche is mostly distinct with specific terminology, but "medical research studies" is broad enough to overlap with sibling skills in the same medical-research suite (e.g., study-design or biomarker-analysis skills), and no distinct trigger phrases are given. This fits 'mostly distinct; minor overlap risk with closely related skills' rather than the fully distinct anchor 5.

4 / 5

Total

13

/

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