CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-cell-line-profiling

Cancer cell-line selection and profiling for experimental model choice. Cross-references DepMap, Cellosaurus, COSMIC, PharmacoDB to deliver identity verification, mutation/CNV profile, gene dependencies, drug sensitivities, and druggable targets. Use to answer 'which cell line should I use for studying gene X?' or 'is this cell line a good model for cancer Y?'. Outputs ranked recommendations with rationale, growth characteristics, and known pitfalls.

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

An excellent, highly actionable body: concrete tool invocations with real parameter values, executable script usage, quantified decision criteria, per-phase outputs, error handling, and a closing checklist. Remaining gaps are minor — some duplicated content (HPA line list repeated three times) and a couple of inlined lookup tables that would be better placed in a references/ directory.

Suggestions

State the HPA supported-cell-line list (hela, mcf7, a549, hepg2, jurkat, pc3, rh30, siha, u251, ishikawa) once and reference it from Phase 2B and the Error Handling table instead of repeating it three times.

Move the Phase 0 tool parameter reference table into a references/tool_parameters.md (or similar) and keep a short pointer in SKILL.md, trimming the main body's token load.

Consider condensing 'LOOK UP, DON'T GUESS' and 'COMPUTE, DON'T DESCRIBE' into the KEY PRINCIPLES list to remove near-duplicate guidance.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious, skill-specific data (tool parameter quirks, the HPA 10-line restriction, SYNERGxDB scope limits) rather than concepts Claude already knows, so it largely earns its tokens. It is not a 5 because of repeated content: the HPA supported-line list appears three times (Phase 0 table, Phase 2B, Error Handling) and generic mantras like "LOOK UP, DON'T GUESS" / "COMPUTE, DON'T DESCRIBE" could be trimmed to one line each.

4 / 5

Actionability

Nearly every section gives copy-paste-ready tool calls with literal parameter values ("DepMap_get_cell_lines(tissue='Lung', page_size=20)", "cBioPortal_get_mutations(study_id='ccle_broad_2019', gene_list='EGFR,KRAS,TP53')"), executable bash for the bundled script, and numeric decision thresholds (Chronos < -0.5 = essential, weighted criteria with max = 27). This matches the 5 anchor: fully executable guidance covering the common cases (5 use patterns, 5 phases).

5 / 5

Workflow Clarity

A clear five-phase sequence, each phase with an explicit Goal and OUTPUT, plus an Error Handling table for recovery paths and a Completeness Checklist that functions as a final validation step — matching the 5 anchor (clear sequence, explicit validation, error-recovery guidance). Operations are read-only lookups, so the destructive-operation cap does not apply.

5 / 5

Progressive Disclosure

The single bundle file is clearly signaled and one level deep ("use the bundled script scripts/depmap_gene_dependency.py", verified to exist and behave as described), sections are well organized, and there are no nested references. It is not a 5 because there is no references/ directory at all — the 25-line Phase 0 tool parameter table and the Quick Reference cell-line table are inlined API/lookup material that would fit a references/ file, per the 4 anchor ("most content is appropriately placed; minor organization gaps").

4 / 5

Total

18

/

20

Passed

Description

92%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 what the skill does with a comprehensive list of concrete capabilities, gives explicit natural-language trigger questions, uses third person, and occupies a distinct niche. The only weakness is modest keyword coverage — a few common synonyms users might say (authentication, STR, drug response) are missing.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "identity verification, mutation/CNV profile, gene dependencies, drug sensitivities, and druggable targets" — covering the full workflow comprehensively, matching the top anchor ("Lists multiple specific concrete actions; comprehensive coverage"). It is not a 4 because coverage spans input query through ranked output with no notable gaps.

5 / 5

Completeness

Both "what" ("Cross-references DepMap, Cellosaurus, COSMIC, PharmacoDB to deliver identity verification, mutation/CNV profile, gene dependencies, drug sensitivities, and druggable targets") and "when" ("Use to answer 'which cell line should I use for studying gene X?' or 'is this cell line a good model for cancer Y?'") are explicit, with concrete trigger phrases — exactly the 5 anchor. Voice is third person throughout ("Cross-references", "Outputs"), so no voice penalty applies.

5 / 5

Trigger Term Quality

Natural trigger phrases are present in users' own words: "which cell line should I use for studying gene X?" and "is this cell line a good model for cancer Y?", plus keywords like mutation, drug sensitivities, DepMap. It falls short of the 5 anchor because common variations users would say are absent (e.g., "cell line authentication", "STR profiling", "drug response", "IC50", "CRISPR screen").

4 / 5

Distinctiveness Conflict Risk

A clear niche — cancer cell-line selection/profiling — anchored by named databases (DepMap, Cellosaurus, COSMIC, PharmacoDB) and domain-specific trigger questions, so it is clearly distinguishable from other skills with minimal conflict risk, matching the 5 anchor.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

mims-harvard/ToolUniverse

Path

plugin/skills/tooluniverse-cell-line-profiling/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.