CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

basic-research-design

A biomedical research topic designer that generates progressive experimental subtitles and detailed research outlines based on a given subject. Use when the user wants to design a research proposal, outline experiments for a topic, or structure a biomedical study.

Quality

62%

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 ./scientific-skills/Protocol Design/basic-research-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

31%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 has a clear two-step workflow skeleton with concrete quality rules, but it is unrunnable as packaged because the referenced prompt templates are missing, and roughly half of the body is generic template boilerplate that adds no value. It needs the actual reference files shipped and the filler sections removed.

Suggestions

Ship the referenced references/prompt_templates.md file (or inline the actual subtitle and outline prompts) — the workflow is unexecutable without it.

Delete the generic filler sections (When to Use, Key Features, Example Usage, Implementation Details, Quick Validation) that restate the description or state that nothing is required; keep only the workflow, quality rules, output format, and failure guidance.

Consolidate the overlapping boilerplate sections (Required Inputs, Input Validation, Validation and Safety Rules, Output Contract) into one concise input/validation block to cut token cost.

DimensionReasoningScore

Conciseness

Several sections are generic padded boilerplate: 'When to Use' ('Use this skill when the request matches its documented task boundary'), 'Key Features' repeating the frontmatter description verbatim, an 'Example Usage' block that is just a directory listing, 'Implementation Details' opening with 'See ## Workflow above', and a 'Quick Validation' section stating 'No local script validation step is required.' This matches anchor 2 ('Noticeably verbose; several unnecessary explanations or padded sections') — far more than the 'some unnecessary explanation' of anchor 3.

2 / 5

Actionability

The workflow steps ('Use the Subtitle Generation Prompt (see references/prompt_templates.md)') point to the actual executable prompts, but that file — and the entire references/ directory — does not exist, so the concrete instructions are missing. The Quality Rules are specific ('exactly 6 subtitles', 'screening -> verification -> mechanism -> in vivo'), but the core executable guidance lives in a missing file, matching anchor 2 ('Minimal concrete guidance; high-level hints but missing the specific steps to execute') rather than anchor 3, which requires some concrete guidance that is present but incomplete.

2 / 5

Workflow Clarity

The two-step sequence (generate 6 subtitles, then generate the outline from subject + subtitles) is clearly ordered with explicit inputs, and Quality Rules serve as checkpoints. However, the workflow's central dependency is a missing prompt-templates file, and the validation sections are filler ('No local script validation step is required'), so anchor 3 ('Steps listed but validation gaps') fits better than anchor 4's 'most checkpoints present'.

3 / 5

Progressive Disclosure

The body's only reference, 'references/prompt_templates.md', points to a nonexistent file — no references/, scripts/, or assets/ directories exist in the bundle, so the skill is unrunnable as packaged. Combined with inlined generic boilerplate that should be trimmed rather than kept in SKILL.md, this matches anchor 2 ('Minimal structure; ... references are buried' / broken) rather than anchor 3, which requires a present, if imperfectly signaled, reference structure.

2 / 5

Total

9

/

20

Passed

Description

78%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 solid description with an explicit what/when structure, third-person voice, and natural trigger phrases. Its main weakness is limited specificity — only two actions are described — and minor overlap risk with general proposal-writing skills.

DimensionReasoningScore

Specificity

The description names the domain ('biomedical research topic designer') and two concrete actions ('generates progressive experimental subtitles and detailed research outlines'), but coverage stops there — no mention of what the subtitles/outline contain or how they're structured. This matches anchor 3 ('Names domain and 1-2 concrete actions, but not comprehensive') and falls short of anchor 4, which requires several specific actions with only minor gaps.

3 / 5

Completeness

Both parts are explicit: the 'what' ('generates progressive experimental subtitles and detailed research outlines based on a given subject') and the 'when' ('Use when the user wants to design a research proposal, outline experiments for a topic, or structure a biomedical study') with three concrete trigger phrases. This matches anchor 5 exactly; anchor 4 would require a less explicit or specific 'when' clause, which is not the case here.

5 / 5

Trigger Term Quality

Natural trigger phrases are present: 'design a research proposal', 'outline experiments for a topic', 'structure a biomedical study'. A few common variations are missing (e.g., 'experimental design', 'study design', 'grant proposal'), so it fits anchor 4 ('Good keyword coverage; a few natural terms missing') rather than anchor 5's comprehensive synonym coverage, and is clearly above anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

The biomedical research design niche is fairly distinct, but 'design a research proposal' and 'outline experiments' could overlap with generic proposal-writing or general research skills, so anchor 4 ('Mostly distinct; minor overlap risk with closely related skills') fits better than anchor 5's 'minimal conflict risk'.

4 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Protocol Design/basic-research-design/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.