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.

68

Quality

81%

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, information-dense skill body with a clear phased workflow, concrete tool usage including exact parameter requirements, and honest limitations. The primary refinement opportunities are deduplicating repeated facts (species differences, marker lists), making per-phase validation explicit, and potentially moving detailed lookup tables into reference files.

DimensionReasoningScore

Conciseness

The body is dense and table-driven with no padded prose — e.g., the Core Tools table packs usage plus parameter warnings into single rows, and the pathway table gives KEGG IDs and modulators compactly. Not 5 because of minor trimmable material: species differences are stated twice (Reasoning Strategy and Limitations), pluripotency markers appear in both Key Principles and Phase 1, and some biology Claude already knows ('KLF4 and MYC are Yamanaka factors') is restated. Not 3 because the verbosity is minor, not a pattern of unnecessary explanation.

4 / 5

Actionability

Guidance is largely executable: exact tool names with required parameters ('REQUIRES operation="search_by_cell_type", cell_name= (NOT cell_type=)'), concrete Phase 3 code (e.g., 'GEO_search_rnaseq_datasets(query="iPSC differentiation neural", organism="Homo sapiens")'), and specific compounds/KEGG IDs. Not 5 because only one code block exists and most tool guidance is tabular reference rather than copy-paste examples covering common cases.

4 / 5

Workflow Clarity

A clear six-phase sequence is laid out in the ASCII workflow diagram and expanded per phase, with checkpoints present via 'LOOK UP DON'T GUESS', the marker co-expression criterion, and the Synthesis Questions acting as an end-of-run checklist. Not 5 because per-phase validation is implicit (e.g., no explicit 'confirm identity before proceeding to Phase 2' step) and there are no error-recovery feedback loops. Not 3 because checkpoints are present, just not uniformly explicit.

4 / 5

Progressive Disclosure

The skill is self-contained with no bundle files, and the body is well organized into clearly headed sections (Reasoning Strategy, Core Tools, Workflow, Evidence Grading, Limitations) that are easy to navigate. Not 5 because at ~134 lines the detailed lookup tables (marker lists, pathway/modulator table, fidelity scoring rubric) could arguably be split into reference files to slim the always-loaded context. Not 3 because the structure and placement are good, not merely 'could be better organized'.

4 / 5

Total

16

/

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 that concretely names its domain and capabilities and includes an explicit, specific 'Use for' trigger clause. The main improvement opportunities are converting noun-phrase capabilities into more action-like language and adding common user synonyms (e.g., spelled-out 'induced pluripotent stem cells').

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — 'pluripotency markers, differentiation protocol pathways, lineage commitment factors, organoid model selection' plus 'iPSC characterization, differentiation protocol design via developmental-pathway recapitulation, and organoid-model selection' — but the phrasing is noun-heavy rather than action-oriented and omits capabilities the body covers (atlas/dataset discovery, literature search). Not 5 because of these minor coverage gaps; not 3 because it goes well beyond 1-2 concrete actions.

4 / 5

Completeness

It clearly answers both questions: 'what' via the four enumerated topic areas ('pluripotency markers, differentiation protocol pathways, lineage commitment factors, organoid model selection') and 'when' via the explicit 'Use for iPSC characterization, differentiation protocol design via developmental-pathway recapitulation, and organoid-model selection for disease modeling' clause with concrete triggers. Not 4 because the 'when' is already fully explicit and specific.

5 / 5

Trigger Term Quality

Natural keywords users would say are present — 'Stem cell', 'iPSC', 'organoid', 'pluripotency markers', 'differentiation protocol' — giving good coverage. Not 5 because common variations are missing (e.g., 'induced pluripotent stem cells' spelled out, 'pluripotent', specific organoid types like 'brain organoid' or 'mini-brain').

4 / 5

Distinctiveness Conflict Risk

A clear niche (stem cell/iPSC/organoid research via ToolUniverse) with distinct trigger phrases like 'iPSC characterization' and 'organoid-model selection for disease modeling' that would not naturally fire unrelated skills. Not 4 because no meaningful overlap risk is apparent — the triggers are domain-specific and unambiguous.

5 / 5

Total

18

/

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