CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

55

Quality

63%

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

42%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 phenotype-writing guidance is concrete and well-structured, but it is buried under templated boilerplate, broken example paths, and a placeholder script. The workflow omits an available validation script as an explicit checkpoint, and bundle references are not specifically signaled.

Suggestions

Remove the templated boilerplate — drop the verbatim description repeats in 'When to Use' and 'Key Features', the meaningless 'See ## Overview above' pointer, and the generic 'Implementation Details' platitudes to tighten conciseness.

Wire the existing `scripts/validate_word_count.py` into the Quick Start as an explicit validation checkpoint with a fix-and-retry loop, and fix or remove the bogus `20260316/scientific-skills/...` path and the placeholder `example.py`.

Replace generic 'references/ contains supporting rules' pointers with specific links to `references/academic_writing_guide.md` and `references/api_reference.md` so navigation is one level deep and clearly signaled.

DimensionReasoningScore

Conciseness

The body is noticeably padded: 'When to Use' and 'Key Features' restate the description verbatim, 'Implementation Details' offers generic platitudes ('keep results reproducible, identify assumptions explicitly'), and 'See ## Overview above for related details' is a meaningless pointer. The core phenotype guidance is efficient, but the templated wrapper adds several unnecessary sections, placing it below the midpoint.

2 / 5

Actionability

The writing spec is concrete — explicit word counts (≥800, ≥500), a ≥5 marker requirement, and a copy-ready Output Format template — but the executable tooling is incomplete: `scripts/example.py` is a placeholder stub that only prints, and 'Example Usage' points at a non-existent path (`20260316/scientific-skills/...`). Concrete guidance is present but undercut by broken/stub tooling.

3 / 5

Workflow Clarity

Quick Start provides a clear 6-step sequence and Quality Control lists validation criteria, but checkpoints are implicit rather than enforced — notably, the existing `scripts/validate_word_count.py` is never invoked as a validate→fix→retry step. Sequence is present but validation gaps keep it at 3.

3 / 5

Progressive Disclosure

Structure exists (Overview, Quick Start, Content Requirements, Output Format, Quality Control) and bundle files are present, but references are only signaled generically ('Reference material available in references/') rather than pointing to the actual `academic_writing_guide.md` or `api_reference.md`, and `validate_word_count.py` is not surfaced. References are present but not clearly signaled.

3 / 5

Total

11

/

20

Passed

Description

83%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 explicitly states both what the skill does and when to use it, with a distinct, well-scoped niche and concrete content dimensions. It is held back only by limited verb diversity and incomplete synonym coverage in its trigger terms.

DimensionReasoningScore

Specificity

Names the domain ('biomedical phenotype introductions with structured academic content') and several concrete actions — generating introductions spanning concept, mechanism, regulation, and detection methods — with only minor coverage gaps. It does not reach 5 because 'generating' is the sole verb and the actions are framed as content sections rather than distinct operations.

4 / 5

Completeness

Explicitly answers both 'what' ('Expert system for generating comprehensive biomedical phenotype introductions with structured academic content') and 'when' ('Use when users request detailed explanations of cellular phenotypes including concept, mechanism, regulation, and detection methods in Chinese academic writing') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Includes reasonably natural phrasing ('users request detailed explanations of cellular phenotypes', 'Chinese academic writing') that a user might actually say, but misses common synonyms and variations. It is above the midpoint (good keyword coverage) but not comprehensive enough for a 5.

4 / 5

Distinctiveness Conflict Risk

The combination of biomedical phenotype introductions, four named content sections, and Chinese academic writing forms a fairly distinct niche with minor overlap risk against general biomedical-writing skills. Not a 5 because 'phenotype' content could still overlap with adjacent biomedical skills.

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

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