CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gene-info

Retrieves comprehensive gene information including PubMed publication counts, NCBI summaries, and Ensembl transcript data. Supports batch processing and file input. Invoke when the user asks for gene details, publication statistics, or needs to analyze a list of genes.

Quality

75%

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/gene-info/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 second half of the body is a solid, actionable tool reference with executable examples and a clear output schema, but it is undermined by ~60 lines of auto-generated filler that duplicates the description and pads with generic process rules, plus path inconsistencies and one fabricated expected-output block. Trimming the boilerplate and unifying script paths would materially improve it.

Suggestions

Delete the boilerplate header block (When to Use, Key Features, Dependencies, Example Usage run plan, Implementation Details) — it repeats the frontmatter description verbatim and states generic process rules Claude already knows, nearly halving the file while losing nothing.

Unify script paths: the usage examples invoke '.trae/skills/gene-info/scripts/fetch_gene_info.py' while the validation and example-plan sections use 'scripts/fetch_gene_info.py'; pick one relative path and use it everywhere.

Fix the 'Quick Validation' section: replace the fabricated 'Expected output format' block (result file / PASS-FAIL summary) with what 'python scripts/fetch_gene_info.py --help' actually prints, and add a concrete post-run checkpoint for batch runs (e.g. verify each gene in the input list appears in the output JSON).

DimensionReasoningScore

Conciseness

The first ~60 lines are template boilerplate: the frontmatter description is repeated verbatim in 'Key Features', and sections like 'When to Use' ('when the request matches its documented task boundary') and circular pointers ('See ## Usage above for related details', 'See ## Prerequisites above') add no skill-specific information. The Dependencies and Example Usage sections also duplicate content, and generic sections like 'Deterministic Output Rules' and 'Completion Checklist' state what Claude already knows.

2 / 5

Actionability

Provides concrete, mostly copy-paste-ready commands for single gene, keyword search, batch, file input, export, and advanced flags (--include-sequence, --include-homology), plus a documented output field list. Minor gaps: inconsistent script paths ('.trae/skills/gene-info/scripts/...' vs 'scripts/...') and a 'cd "20260316/scientific-skills/..."' example path that won't exist for users, and the 'Expected output format' block under Quick Validation does not match what '--help' actually prints.

4 / 5

Workflow Clarity

The usage sections sequence single → keyword → batch → file → export clearly, and validation content exists (Quick Validation, validate_skill.py, Recommended Workflow step 4, Completion Checklist). However the checkpoints are generic boilerplate rather than concrete verification of the batch results, and the quick-validation 'Expected output format' (a gene_info_result.md with PASS/FAIL summary) is fabricated relative to the documented script behavior, so validation is present but confusing.

3 / 5

Progressive Disclosure

Scored against the actual bundle (scripts/fetch_gene_info.py and scripts/validate_skill.py both exist and are referenced with clear paths; no references/ or assets/ dirs). Sections are well-organized with headers and the tool documentation is appropriately inline for its size. Minor gaps: the conflicting '.trae/skills/...' vs 'scripts/...' path prefixes hurt navigation, and the boilerplate front section buries the real content ('# Gene Information Tool' starts at line 60).

4 / 5

Total

13

/

20

Passed

Description

87%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: third-person, concrete about capabilities and data sources, with an explicit 'Invoke when' clause covering single-gene, statistics, and list-analysis use cases. Only minor omissions (export formats, sequence/homology features, a few synonyms) keep it from full marks on specificity and trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'PubMed publication counts, NCBI summaries, and Ensembl transcript data', 'batch processing and file input' — naming specific data sources. Minor gaps in coverage: output export formats, genomic sequence, and ortholog/homology retrieval documented in the body are omitted.

4 / 5

Completeness

Explicitly answers both: 'what' — retrieves publication counts, NCBI summaries, Ensembl transcript data with batch and file input; 'when' — 'Invoke when the user asks for gene details, publication statistics, or needs to analyze a list of genes' with concrete trigger phrases. Matches the anchor-5 example structure.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('gene details', 'publication statistics', 'analyze a list of genes') plus source keywords (PubMed, NCBI, Ensembl). A few natural terms are missing, e.g. 'gene symbol', 'gene lookup', 'orthologs', 'Ensembl'.

4 / 5

Distinctiveness Conflict Risk

Clear niche (gene information retrieval from PubMed/NCBI/Ensembl) with distinct triggers; unlikely to fire for unrelated skills since the triggers are gene- and publication-statistics-specific.

5 / 5

Total

18

/

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/gene-info/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.