CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

biomed-outline-generator

Generates structured biomedical outlines for review articles, discussion sections, and thesis proposals. Use when a user provides biomedical keywords, results/discussion text, or a proposal title plus background and needs a directly usable academic writing scaffold.

Quality

79%

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/Academic Writing/biomed-outline-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, safety-conscious instruction skill with concrete output contracts, a refusal mechanism, and a verifiable script reference. The main weaknesses are the duplicated type-recognition section inflating token cost, the absence of a worked output example, and the underspecified 'enrich' step in the workflow.

Suggestions

Merge 'Type Recognition Rules' into 'When to Use' (or reduce it to just the disambiguating signals) — the input patterns are currently stated twice, costing tokens without adding guidance.

Add one short worked example of a completed Type I or Type II outline so the expected output shape is shown, not just listed as required sections.

Make step 4 of the workflow concrete (e.g., '2-3 subpoints per section covering mechanism, evidence, limitation') and add a recovery action for when the Completion Checklist fails, mirroring the existing fallback contract.

DimensionReasoningScore

Conciseness

The body is list-based and free of concept re-teaching, but the 'Type Recognition Rules' section substantially duplicates the 'When to Use' input patterns (e.g., 'topic keywords', 'observations or findings', '`Title:`' each appear twice), and the 'Optional Validation Shortcut' section adds marginal value. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened'; it is not a 4 because the duplication is a whole section rather than minor instances, and not a 2 because there is no padding or explanation of things Claude already knows.

3 / 5

Actionability

Guidance is concrete for an instruction-only skill: exact required-section contracts per type, literal refusal templates, a real executable command ('python scripts/validate_skill.py --check'), and input examples for all three types. It is not a 5 because there is no worked example of an actual output outline, so 'specific examples cover the common cases' is only partially met; it is not a 3 because the guidance is directly executable as written, not pseudocode or high-level hints.

4 / 5

Workflow Clarity

The workflow gives a clear 5-step sequence with checkpoints (step 1 validates domain and sufficiency, step 5 is a final safety pass), a fallback contract with retry formats, and a completion checklist — matching 'clear sequence with most checkpoints present'. It is not a 5 because there is no feedback loop after the final pass (nothing tells Claude what to do if the checklist fails) and step 4's 'Enrich with academic logic' is underspecified relative to the other steps; it is well above a 3 because validation checkpoints are explicit rather than implicit.

4 / 5

Progressive Disclosure

The body is well-organized with clear section headers, and its single bundle reference ('scripts/validate_skill.py') exists and is correctly signaled. It is not a 5 because at ~215 inline lines with all type rules, contracts, and examples in one file, some content (e.g., the three output contracts or the example inputs) could be split out, and the 'Optional Validation Shortcut' section sits oddly before 'When to Use'; it is not a 3 because there is no misplaced bulk content and navigation is easy.

4 / 5

Total

15

/

20

Passed

Description

82%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 explicit what/when structure, third-person voice, and concrete multi-form trigger phrases. Its only real limitations are a single action verb (limiting described capability coverage) and missing natural synonyms like 'manuscript' or 'literature review' in the trigger terms.

DimensionReasoningScore

Specificity

The description names one concrete action — 'Generates structured biomedical outlines' — and enumerates three specific target artifacts ('review articles, discussion sections, and thesis proposals'), which fits the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. It is not a 4 because there is only a single action verb with no variation in what the skill actually does (e.g., no mention of the refusal/validation behaviors), and not a 2 because the three artifact types make the action concrete rather than generic.

3 / 5

Completeness

It explicitly answers both: what — 'Generates structured biomedical outlines for review articles, discussion sections, and thesis proposals' — and when — 'Use when a user provides biomedical keywords, results/discussion text, or a proposal title plus background and needs a directly usable academic writing scaffold'. Both are present with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Trigger phrases like 'biomedical keywords, results/discussion text, or a proposal title plus background' are natural things users would say, giving good keyword coverage. It is not a 5 because common synonyms and variations are missing — e.g., 'manuscript', 'literature review', 'paper', 'discussion draft' — and not a 3 because the input patterns are specific and multi-form rather than just relevant keywords with missing variations.

4 / 5

Distinctiveness Conflict Risk

The biomedical academic-writing niche with its specific input patterns ('proposal title plus background', 'results/discussion text') is clearly distinct from generic outlining, writing, or document skills, so conflict risk is minimal. It clearly matches the 'clear niche with distinct triggers' anchor rather than the 4 anchor's 'minor overlap risk with closely related skills'.

5 / 5

Total

17

/

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

scientific-skills/Academic Writing/biomed-outline-generator/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.