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

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/cellosaurus-api/SKILL.md

Quality

Content

56%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 body delivers usable, executable API examples backed by real scripts, but is significantly over-padded with templated boilerplate and suffers from structural duplication and inconsistent command paths. Trimming the generic process sections and reconciling the invocation paths would materially improve it.

Suggestions

Remove the generic boilerplate sections ('When to Use', 'Output Contract', 'Validation and Safety Rules', 'Completion Checklist', etc.) that restate process discipline Claude already knows, keeping only the Cellosaurus-specific guidance.

Reconcile the conflicting command paths: pick one canonical invocation path (e.g. `python scripts/client.py ...`) and use it consistently across all examples instead of mixing `20260316/...`, `.trae/skills/...`, and `scripts/...`.

De-duplicate the document skeleton: the file contains two overlapping structures (an upper templated half and a lower '# Cellosaurus API Skill' half) with repeated 'Quick Validation' blocks — merge them into one coherent document.

Dimension	Reasoning	Score
Conciseness	The body is padded with generic boilerplate ('When to Use', 'Output Contract', 'Validation and Safety Rules', 'Completion Checklist', etc.) restating process discipline Claude already knows, and it stitches two parallel document skeletons together with duplicated sections and conflicting command paths.	2 / 5
Actionability	Provides real executable commands covering common cases ('client.py info', 'get CVCL_0030', 'search "id:HeLa" --rows 5'), but copy-paste reliability is undermined by inconsistent invocation paths (.trae/skills/... vs scripts/client.py vs 20260316/...).	4 / 5
Workflow Clarity	A clear sequenced 'Recommended Workflow' with validation checkpoints and a completion checklist is present (this is a read-only API skill, so the destructive-cap does not apply), though validation guidance is duplicated ('Quick Validation' appears twice) and templates overlap.	4 / 5
Progressive Disclosure	Sections exist (Capabilities, Usage, References) and referenced bundle files (scripts/client.py, scripts/validate_skill.py) are real and one level deep, but generic boilerplate is inlined in a single file and the stitched-together structure (two skeletons, a mid-document '# Cellosaurus API Skill' heading) makes navigation confusing.	3 / 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.

The description is well-constructed: third-person voice, explicit trigger clause, and three concrete named actions tied to a distinctive data source. Its only weakness is a slightly narrow action list that omits common synonyms a user might utter.

Dimension	Reasoning	Score
Specificity	Names the domain and three concrete actions ('search cell lines, get cell line details by accession, ... check database release info'), which is strong coverage though narrowly scoped to just three operations rather than a fully comprehensive list.	4 / 5
Completeness	Explicitly answers both 'what' (access Cellosaurus for cell line info and release data) and 'when' via a concrete 'Invoke when user asks to...' trigger clause, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('search cell lines', 'get cell line details', 'check database release info'), with good coverage but a few common synonyms (e.g. 'cell line database', 'Cellosaurus lookup') absent.	4 / 5
Distinctiveness Conflict Risk	Targets a specific named database (Cellosaurus) with distinct triggers ('by accession', 'release info'), giving a clear niche with minimal overlap risk.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 63c61d3

Reviewed: 4 hours ago

Table of Contents

Discovery Implementation Validation

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.