CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-spatial-transcriptomics

Spatial transcriptomics analysis — Visium, MERFISH, seqFISH, Slide-seq. Maps gene expression to tissue architecture, identifies spatially variable genes (SVGs), tissue-domain segmentation, and cell-cell interaction inference. Use for spatial gene-expression questions, tissue architecture analysis, and SVG identification.

Quality

81%

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

The canonical home for this skill is tooluniverse-spatial-transcriptomics in mims-harvard/ToolUniverse

SKILL.md
Quality
Evals
Security

Quality

Content

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

Strong domain-specific operational guidance with a clearly sequenced, checkpoint-bearing 8-phase workflow and genuinely useful interpretation frameworks (evidence grading, SVG vs. cell-type-marker reasoning). Weaknesses are self-duplication (workflow diagram vs. phase summaries, platform facts vs. limitations), inlined peripheral dataset-discovery material, and references to bundle files that are not present.

Suggestions

Collapse the ASCII "Workflow Overview" and the "Phase Summaries" into a single presentation — keep the diagram and fold each summary's extra specifics (PCA components, Wilcoxon, method recommendations) into it, cutting roughly 40 duplicated lines.

Move the HuBMAP biospecimen/donor discovery layer (~70 lines, peripheral to spatial analysis) into a dedicated reference file and keep only the availability note plus one fallback example inline in SKILL.md.

Ship code_examples.md and report_template.md in the bundle — or inline minimal executable snippets for Phases 1-6 — so the core analysis code the body defers to those files is actually reachable.

DimensionReasoningScore

Conciseness

Mostly dense, non-obvious operational detail (QC cutoffs "min 200 genes, 500 UMI, <20% MT", tool params, interpretation thresholds), but tightening is needed: the 8-phase workflow is rendered twice (the ASCII "Workflow Overview" diagram plus the "Phase Summaries" section), the opening paragraph restates the frontmatter description, "Limitations" repeats platform facts already in "Supported Platforms" ("Visium spots contain multiple cells"), and the HuBMAP section carries a second redundant fallback code block. Not 2 because the bulk is genuinely operational knowledge rather than padding; not 4 because the duplication is more than minor.

3 / 5

Actionability

Mostly executable guidance: concrete QC thresholds, named tools with parameters ("OmniPath_get_ligand_receptor_interactions — ... Use `partners` param for specific genes"), runnable Python snippets (scanpy loading, HuBMAP queries), and interpretation cutoffs ("Moran's I > 0.3 with FDR < 0.05", "z-scores > 2"). Not 5 because the core Phases 1-6 have no inline code — it is deferred to code_examples.md — so the end-to-end common case is not copy-paste ready in the body; not 3 because everything present is real, specific, and executable rather than pseudocode.

4 / 5

Workflow Clarity

A clear 8-phase sequence with most checkpoints explicit: QC filters and "Verify spatial alignment" (Phase 1), "Filter significant spatial genes (FDR < 0.05)" (Phase 4), "Validate with marker genes" (Phase 6), a fallback loop for unavailable HuBMAP tools, and a "Quantified Minimums" completion checklist. Not 5 because there is no error-recovery guidance (e.g., what to do when fewer than 500 spots survive QC or when deconvolution fails); not 3 because validation checkpoints are stated explicitly rather than implied.

4 / 5

Progressive Disclosure

The body is well-sectioned with clearly signaled one-level references ("See [report_template.md](report_template.md)" and the "Reference Files" section), but the two referenced bundle files (code_examples.md, report_template.md) are absent from the bundle, leaving the deferred core-phase code unreachable; additionally ~70 lines of peripheral HuBMAP sample/donor discovery material are inlined in SKILL.md where a separate reference file would fit. Not 4 because dangling references plus inlined peripheral content exceed 'minor organization gaps'; not 2 because the document is clearly structured with headers, not a monolithic wall.

3 / 5

Total

14

/

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: third-person voice, multiple concrete capabilities, named platforms, and an explicit 'Use for...' trigger clause with concrete trigger phrases. Only minor keyword gaps (Xenium, deconvolution, data formats) keep trigger-term quality below full marks.

DimensionReasoningScore

Specificity

The description lists four concrete actions — "Maps gene expression to tissue architecture, identifies spatially variable genes (SVGs), tissue-domain segmentation, and cell-cell interaction inference" — plus the named platforms (Visium, MERFISH, seqFISH, Slide-seq), giving comprehensive coverage of the domain's pipeline. It is not 4 because there is no noticeable gap: import-to-interaction analysis stages are all named concretely.

5 / 5

Completeness

Both questions are answered explicitly: the what ("Maps gene expression to tissue architecture, identifies spatially variable genes (SVGs), tissue-domain segmentation, and cell-cell interaction inference") and the when ("Use for spatial gene-expression questions, tissue architecture analysis, and SVG identification"). This matches the anchor-5 example structure of concrete actions followed by concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural terms users would say are present: "Spatial transcriptomics", "Visium", "MERFISH", "seqFISH", "Slide-seq", "spatially variable genes", "tissue architecture". It falls short of 5 because Xenium (a platform the body covers), "deconvolution"/"cell type mapping", and any data-format terms are missing; it exceeds 3 because the core user vocabulary for this domain is well represented.

4 / 5

Distinctiveness Conflict Risk

Spatial platforms and spatial-only questions ("spatial gene-expression questions", "SVG identification") establish a clear niche with minimal conflict risk. The only overlap is "cell-cell interaction inference", which lightly touches a sibling single-cell skill, but the spatial framing and platform names keep triggers unambiguous — not enough overlap to justify 4.

5 / 5

Total

19

/

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

relative_links

Relative link issues: 3 missing

Warning

Total

15

/

16

Passed

Repository

mims-harvard/ToolUniverse

Path

plugins/tooluniverse/skills/tooluniverse-spatial-transcriptomics/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.