CtrlK
BlogDocsLog inGet started
Tessl Logo

tooluniverse-stem-cell-organoid

Stem cell, iPSC, and organoid research — pluripotency markers, differentiation protocol pathways, lineage commitment factors, organoid model selection. Use for iPSC characterization, differentiation protocol design via developmental-pathway recapitulation, and organoid-model selection for disease modeling.

69

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, domain-rich skill body with concrete tools, parameters, and a phased workflow. It leans slightly on explaining biology Claude largely knows and inlines tables that could be externalized, but remains highly actionable.

Suggestions

Tighten the Reasoning Strategy: drop the general 'protocol must mimic embryonic signaling' explanation and keep only the tool-specific lookup directives.

Move the organoid fidelity-scoring table and Evidence Grading table into reference files (e.g., references/organoid-fidelity.md) and link to them from SKILL.md.

Add explicit per-phase validation gates (e.g., 'Verify marker co-expression before proceeding to Phase 2') to strengthen workflow feedback loops.

DimensionReasoningScore

Conciseness

Dense and mostly assumes Claude's competence (markers, KEGG IDs, modulators given without basics), but the Reasoning Strategy over-explains developmental-biology concepts Claude already knows and the fidelity/grading tables are sizable; minor trimming possible.

4 / 5

Actionability

Concrete tool calls with required parameters and gotchas ('Requires operation="search_by_cell_type", cell_name= (NOT cell_type=)'), KEGG IDs, named modulators, and executable Python snippets; minor gaps in import/error-handling completeness.

4 / 5

Workflow Clarity

Clear Phase 0–5 sequence with a 'LOOK UP DON'T GUESS' checkpoint and Synthesis Questions acting as a verification checklist, though explicit validate-then-proceed feedback loops between phases are only implicit.

4 / 5

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-sectioned, but the organoid-fidelity, evidence-grading, and pathway tables are sizable inline content that could be split into reference files.

4 / 5

Total

16

/

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 well-crafted description that names concrete capabilities and provides an explicit 'Use for' trigger clause covering characterization, protocol design, and model selection. Minor room to add a couple more natural trigger synonyms.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'pluripotency markers, differentiation protocol pathways, lineage commitment factors, organoid model selection' and 'iPSC characterization, differentiation protocol design via developmental-pathway recapitulation, and organoid-model selection for disease modeling' — with comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what (research areas, markers, pathways, model selection) and when via the 'Use for iPSC characterization, differentiation protocol design..., and organoid-model selection for disease modeling' trigger clause.

5 / 5

Trigger Term Quality

Strong natural terms users would say ('stem cell', 'iPSC', 'organoid', 'pluripotency markers', 'differentiation protocol', 'disease modeling') including synonyms, but a few common variations are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (stem cell/iPSC/organoid research) with distinct triggers unlikely to fire for unrelated skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mims-harvard/ToolUniverse
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.