CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

phenotype-introduction

Expert system for generating comprehensive biomedical phenotype introductions with structured academic content. Use when users request detailed explanations of cellular phenotypes including concept, mechanism, regulation, and detection methods in Chinese academic writing.

Quality

72%

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/Evidence Insight/phenotype-introduction/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 core instructions (section requirements, word counts, output template) are genuinely actionable, but the skill is buried under templated boilerplate sections that restate the description and add generic filler. Navigation to the bundled reference files is missing, and validation is asserted but never wired to the bundled validation script.

Suggestions

Delete the boilerplate 'When to Use', 'Key Features', 'Dependencies', and 'Implementation Details' sections (or collapse them into a few lines), and state the four sections and word counts once — the core content in Quick Start, Content Requirements, and Output Format already covers everything.

Replace the generic "reference material available in `references/`" mentions with explicit links, e.g. "**Academic writing style**: See [references/academic_writing_guide.md](references/academic_writing_guide.md)", so the bundled references are discoverable and each has a signaled purpose.

Wire validation into the workflow: name `scripts/validate_word_count.py` in Quick Start and Quality Control with its invocation (e.g. `python scripts/validate_word_count.py <output file>`) and add a fix-and-re-validate loop, and replace the placeholder `scripts/example.py` / timestamped `cd` path in Example Usage with the real runnable path.

DimensionReasoningScore

Conciseness

The body carries substantial auto-generated boilerplate that adds nothing Claude doesn't know: the 'When to Use' section awkwardly re-quotes the description verbatim ("use when users request detailed explanations of cellular phenotypes... in chinese academic writing"), and 'Key Features', 'Dependencies', and 'Implementation Details' are padded filler ("Repository baseline for current packaged skills", "not explicitly version-pinned in this skill package", "avoid undocumented side effects"). The four mandatory sections and their word counts are stated three times (Overview, Quick Start, Content Requirements), and 'Implementation Details' opens with a broken forward reference ("See `## Overview` above" to a section defined later). This is noticeably verbose with several unnecessary sections, matching the level-2 anchor rather than the mostly-efficient level-3 anchor.

2 / 5

Actionability

The core generation guidance is concrete: explicit per-section word counts ("≥800 words", "≥500 words, ≥5 markers"), required content bullets, and a copy-paste output template with a marker line format ("Molecule: [Marker name]; Principle: [Detection principle]; Methods: [Detection method]"). Minor gaps keep it from the top anchor: the Example Usage runs a placeholder script against a brittle timestamped path ("cd \"20260316/scientific-skills/Evidence Insight/phenotype-introduction\""), and the bundled validation script is never invoked by name, so the run plan's 'review the generated output' step is not tied to an executable check.

4 / 5

Workflow Clarity

Quick Start gives a clear 6-step sequence (parse name → generate four sections → format output), but validation is only implicit: Quality Control says "All outputs must pass validation for word count per section" yet provides no command or loop, even though a validate_word_count.py script exists in the bundle and is never referenced. This matches the level-3 anchor 'steps listed but validation gaps; checkpoints missing or implicit' — the level-4 anchor requires most checkpoints to be executable.

3 / 5

Progressive Disclosure

The bundle has references/academic_writing_guide.md and references/api_reference.md, but the body never names or links either — it only says "Reference material available in `references/` for task-specific guidance" and "references/ contains supporting rules, prompts, or checklists", so a reader cannot know which file to open for what. Scripts are named (scripts/example.py) and assets are named (assets/example_asset.txt), but the reference navigation is generic. This fits the level-3 anchor 'references present but not clearly signaled' rather than level 4's 'references mostly clear'.

3 / 5

Total

12

/

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: it clearly states what the skill produces and when to use it, with domain-appropriate trigger terms and a distinctive niche. Its only weaknesses are the 'Expert system' buzzword framing and the single-action capability description.

DimensionReasoningScore

Specificity

The description names a concrete action ("generating comprehensive biomedical phenotype introductions") and enumerates the content areas ("concept, mechanism, regulation, and detection methods"), but the leading phrases "Expert system" and "structured academic content" are buzzword-ish and it describes only one action rather than a list of specific capabilities. It fits the anchor 'names domain and 1-2 concrete actions, but not comprehensive' better than the level-4 anchor, which expects several distinct specific actions.

3 / 5

Completeness

It clearly answers both questions: the 'what' ("generating comprehensive biomedical phenotype introductions with structured academic content") and an explicit, concrete 'when' clause ("Use when users request detailed explanations of cellular phenotypes including concept, mechanism, regulation, and detection methods in Chinese academic writing"). The when-clause is specific about content areas and output language, matching the top anchor rather than the level-4 anchor where the 'when' could be more explicit.

5 / 5

Trigger Term Quality

Trigger terms are natural for the domain — "phenotype introductions", "cellular phenotypes", "concept, mechanism, regulation, and detection methods", "Chinese academic writing" — and a user requesting this work would plausibly say these. A few natural variations are missing (e.g., "phenotype overview/review", Chinese-language synonyms like 表型介绍), so it falls just short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The niche is narrow and well-defined — biomedical phenotype introductions written in Chinese academic style — with distinct triggers that no general writing or document skill would match. Conflict risk with other skills is minimal.

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/Evidence Insight/phenotype-introduction/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.