CtrlK
BlogDocsLog inGet started
Tessl Logo

tooluniverse-spatial-omics-analysis

Spatial multi-omics interpretation pipeline. Transforms spatially variable genes (SVGs), domain annotations, and tissue context into biological insights via domain-by-domain characterization, cell-type composition, spatial gene expression patterns, RNA+protein+metabolite integration. Use for Visium, MERFISH, seqFISH, Slide-seq, spatial proteomics, and spatial multi-omics interpretation. Goes beyond statistics to disease mechanisms and therapeutic opportunities.

61

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/tooluniverse/skills/tooluniverse-spatial-omics-analysis/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

60%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 is a well-organized, actionable phase-by-phase pipeline with concrete tooling, but it is undermined by a dangling reference structure — all five referenced bundle files are missing — and by redundant summary/principles sections that inflate token cost. Adding the referenced files or inlining their critical content would resolve the biggest weakness.

Suggestions

Ship the referenced bundle files (phase-procedures.md, tool-reference.md, reference-data.md, report-template.md, test_spatial_omics.py) or inline the critical decision logic and tool invocation syntax they were meant to hold — currently every 'See X.md' pointer leads to a nonexistent file.

Delete or drastically shrink the closing 'Summary' section and the 'KEY PRINCIPLES' list, which restate the phase descriptions and reference-file list already given above.

Add explicit per-phase validation checkpoints (e.g., 'if no domains meet the marker threshold, fall back to global enrichment' or 'verify gene ID resolution succeeded before Phase 2') instead of relying on a single end-of-run completeness checklist.

DimensionReasoningScore

Conciseness

Tables, tool names, and phase listings mostly earn their tokens, but the closing 'Summary' section restates the phase list almost verbatim and 'KEY PRINCIPLES' duplicates phase descriptions, so the body could be meaningfully tightened. Not 4 because an entire redundant section is pure padding; not 2 because there is no over-explanation of concepts Claude already knows.

3 / 5

Actionability

Concrete guidance throughout: named tools per phase ('STRING_functional_enrichment', 'OpenTargets_get_associated_targets_by_disease_efoId'), an input parameter table with examples, FDR cutoffs, HuBMAP parameter details, and a report filename pattern. Falls short of 5 because tool invocation syntax and decision logic are deferred to a reference file rather than shown, leaving minor gaps.

4 / 5

Workflow Clarity

Phases 0-8 are clearly sequenced with Phase 0 marked 'ALWAYS FIRST', conditional phases explicitly gated ('Cancer/Inflammation only', 'if data available'), and a completeness checklist closes the loop. Not 5 because validation checkpoints are implicit (a single end checklist rather than per-phase gates) and the detailed decision logic is delegated elsewhere.

4 / 5

Progressive Disclosure

References are clearly signaled and one level deep ('See phase-procedures.md for detailed workflows'), but the bundle contains no reference files at all — phase-procedures.md, tool-reference.md, reference-data.md, report-template.md, and test_spatial_omics.py are all absent, so every deep-dive pointer dangles and the disclosure structure is non-functional. Not 3 because the actual bundle structure breaks the navigation the body promises.

2 / 5

Total

13

/

20

Passed

Description

83%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 in third-person voice with concrete capabilities and an explicit, platform-specific 'Use for' trigger clause. Its main gaps are the missing 'spatial transcriptomics' keyword (the most natural user phrase) and slightly abstract framing around 'biological insights'.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'domain-by-domain characterization, cell-type composition, spatial gene expression patterns, RNA+protein+metabolite integration' — but phrases like 'transforms... into biological insights' and 'goes beyond statistics' remain abstract claims, so coverage is not fully comprehensive.

4 / 5

Completeness

Explicitly answers both 'what' (transforms SVGs, domain annotations, and tissue context via four named analyses) and 'when' ('Use for Visium, MERFISH, seqFISH, Slide-seq...') with concrete trigger phrases, matching the top anchor; it is not a 4 because the 'when' clause is as explicit and specific as the anchor example.

5 / 5

Trigger Term Quality

'Use for Visium, MERFISH, seqFISH, Slide-seq, spatial proteomics, and spatial multi-omics interpretation' gives strong natural platform keywords, but misses common variations users would say, most notably 'spatial transcriptomics' and 'spatial domains'.

4 / 5

Distinctiveness Conflict Risk

Clear spatial-omics niche with platform-specific triggers (Visium, MERFISH, SVGs) minimizing conflict risk, but 'disease mechanisms and therapeutic opportunities' invites minor overlap with closely related gene/disease interpretation skills; not 5 for that residual overlap, not 3 because the platform triggers are highly distinctive.

4 / 5

Total

17

/

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.