CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cellosaurus-api

Access Cellosaurus database for cell line information and release data. Invoke when user asks to search cell lines, get cell line details by accession, or check database release info.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/cellosaurus-api/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 skill has a solid core — accurate, executable CLI examples for all three capabilities — wrapped in a large shell of generic template boilerplate. The main problems are padding, duplicated sections, inconsistent script paths, and a Quick Validation section whose expected output contradicts the actual script behavior.

Suggestions

Delete the generic template sections (When to Use, Key Features, Dependencies, Implementation Details, Required Inputs, Recommended Workflow, Output Contract, Validation and Safety Rules, Failure Handling, Deterministic Output Rules, Completion Checklist) — they restate what Claude already knows and more than double the token cost of the real content.

Unify script paths to `scripts/client.py` throughout and remove the phantom `cd "20260316/scientific-skills/…"` and `.trae/skills/…` paths so the Usage examples are copy-paste runnable.

Fix the Quick Validation section to describe what `python scripts/client.py --help` actually prints (argparse usage), and document the supported `--format` (json/xml/txt/tsv) and `--sort` options.

DimensionReasoningScore

Conciseness

Over half the body is generic template filler that assumes no intelligence ("Use this skill when the request matches its documented task boundary", "keep the output safe, reproducible, and within the documented scope at all times", "Confirm assumptions, limitations, and warnings are surfaced explicitly") plus the circular "See `## Usage` above" reference. Not 1 because the Cellosaurus-specific Usage commands are lean and genuinely useful.

2 / 5

Actionability

Concrete executable commands with real examples (`get CVCL_0030 --fields id,ac,sy`, `search "id:HeLa" --rows 5`) that match the actual argparse interface in scripts/client.py. Not 5 because script paths are inconsistent across sections (`scripts/client.py` vs `.trae/skills/cellosaurus-api/scripts/client.py` vs `cd "20260316/scientific-skills/…"`), breaking copy-paste readiness, and the --format/--sort options are undocumented.

4 / 5

Workflow Clarity

Sequences and validation sections exist (Recommended Workflow, run plan, Completion Checklist, Quick Validation) but are generic boilerplate untethered to the actual operations. Not 4 because the "Quick Validation" expected output ("Result file: cellosaurus_api_result.md / Validation summary: PASS/FAIL") contradicts what `python scripts/client.py --help` actually produces (argparse help text) and the script produces no result file at all.

3 / 5

Progressive Disclosure

The bundle is appropriately small (two scripts, both real and referenced), but the monolithic SKILL.md carries duplicated scaffolding (two validation sections, two usage sections) and content that should simply be deleted rather than inlined, with inconsistent script paths across sections. Not 2 because headers provide real structure and no bulk content wrongly belongs in separate files.

3 / 5

Total

12

/

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: it states the domain, enumerates all three concrete capabilities, and provides an explicit, specific 'use when' trigger clause in the third person. Only minor keyword synonyms are missing.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("search cell lines", "get cell line details by accession", "check database release info") covering all three capabilities of the skill. Not 5 because the lead phrase "Access Cellosaurus database for cell line information and release data" is mildly generic and no output or interface detail is given.

4 / 5

Completeness

It explicitly answers both what ("Access Cellosaurus database for cell line information and release data") and when ("Invoke when user asks to search cell lines, get cell line details by accession, or check database release info") with concrete trigger phrases, mirroring the anchor-5 example structure. It is not 4 because the 'when' clause is fully explicit and specific.

5 / 5

Trigger Term Quality

Natural domain terms are present: "cell lines", "cell line details", "accession", "Cellosaurus", "release info". Not 5 because common user variations like "CVCL", "cell line database", or specific cell line names (e.g., HeLa) are missing.

4 / 5

Distinctiveness Conflict Risk

"Cellosaurus" plus "accession number" defines a clear niche with distinct triggers; the risk of this firing for the wrong skill is minimal. Uses third-person voice ("Access", "Invoke when user asks") so no voice penalty applies.

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/cellosaurus-api/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.