CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

primary-plan-recommender

Compares multiple study-route options for the same biomedical research question and recommends one primary plan, while explicitly explaining why alternative routes are secondary, premature, weaker, or dependency-heavy. Always use this skill when the user already has a reasonably defined question but is unsure which main study route should anchor the project. Focus on plan comparison, route selection, dependency awareness, and primary-plan justification rather than full protocol drafting.

Quality

81%

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 well-structured for progressive disclosure and provides a clear, actionable decision workflow with a mandated output format, but it is noticeably padded: the same instructions are repeated across Core Function, Decision Logic, Hard Rules, What This Skill Should Not Do, and Quality Standard. Consolidating those overlapping sections and adding one worked example would raise both conciseness and actionability.

Suggestions

Merge "Core Function", "What This Skill Should Not Do", and "Quality Standard" into the Decision Logic steps and Hard Rules to eliminate triple-statement of the same constraints.

Fold "Route Selection Logic" typical-patterns into the referenced plan-route-taxonomy.md module, since the pattern rules are close cousins of the taxonomy.

Add a short worked example (a filled-in route comparison matrix with a primary-plan recommendation) so the Section E–G output shape is concrete rather than only described.

DimensionReasoningScore

Conciseness

The body duplicates itself across sections: "Core Function" (steps 1–8) restates "Decision Logic" (Steps 1–10); "What This Skill Should Not Do" repeats "Core Function should not" and Hard Rules 3, 5, 7, and 12; "Quality Standard" restates Core Function yet again; and "Route Selection Logic" overlaps "Supported Study Route Families". Several padded, redundant sections push this noticeably below "mostly efficient".

2 / 5

Actionability

Concrete, specific guidance throughout — an Input Validation section with quoted request examples and a literal redirect template, sample triggers, a 10-step decision sequence each mapped to a reference module, a mandatory output structure (Sections A–J), and explicit table-usage rules. It falls short of fully executable because no worked example of a completed route comparison or matrix is provided.

4 / 5

Workflow Clarity

The 10-step decision logic is clearly sequenced and tied to specific output sections and reference modules, with an input-validation checkpoint ("respond with the redirect below and stop"). Completeness checks exist ("treat the output as incomplete", Hard Rule 15) but they are stated as post-hoc standards rather than in-flow validate-and-fix checkpoints, and no error-recovery feedback loop is defined.

4 / 5

Progressive Disclosure

All 9 reference files cited in the body exist in references/, each is one level deep, and each is signaled with a precise "use when / which section" purpose (e.g., "plan-route-taxonomy.md → use when classifying candidate study-route families in Section B"). Content is appropriately split into the references with SKILL.md serving as the navigable overview.

5 / 5

Total

15

/

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.

The description is strong: it states concrete capabilities, gives an explicit and specific trigger clause, and clearly delineates its niche against neighboring tasks. Trigger-term coverage is the only soft spot, missing a few natural synonyms users might phrase the request with.

Suggestions

Add one or two natural user phrasings as trigger synonyms, e.g. "use when the user asks which study design or approach should lead the project".

Consider naming the deliverable explicitly (a primary-plan recommendation with route comparison rationale) to sharpen what the user gets back.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Compares multiple study-route options", "recommends one primary plan", "explicitly explaining why alternative routes are secondary, premature, weaker, or dependency-heavy" — with comprehensive coverage of the skill's behavior.

5 / 5

Completeness

Both what ("Compares multiple study-route options... recommends one primary plan") and when ("Always use this skill when the user already has a reasonably defined question but is unsure which main study route should anchor the project") are explicitly and concretely stated.

5 / 5

Trigger Term Quality

Natural phrases like "main study route", "primary plan", "route selection", and "plan comparison" are present and match what a researcher would say, but common variations such as "study design", "which approach", or "help me choose the best design" are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

A clear niche — pre-protocol route selection — with distinct triggers, and the explicit contrast "rather than full protocol drafting" sharply reduces overlap with adjacent planning or protocol-writing skills.

5 / 5

Total

19

/

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/primary-plan-recommender/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.