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.

67

Quality

80%

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 ./plugin/skills/tooluniverse-spatial-omics-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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, actionable instruction-only skill body with a clear 9-phase workflow, concrete tool names, thresholds, and clean one-level references. Its main weaknesses are token waste from duplicated sections (Summary, report skeleton) and the absence of inline invocation examples or explicit per-phase validation/fallback loops; the referenced bundle files were not present to verify.

Suggestions

Remove or drastically shorten the Summary section and the inline report skeleton — both duplicate the Phases Overview and report-template.md, cutting the body's token cost without losing information.

Move the HuBMAP tool parameter table into tool-reference.md (keeping only a one-line pointer plus when-to-use guidance) so SKILL.md stays a lean overview of the nine phases.

Add a short per-phase fallback note (or an explicit pointer to tool-reference.md's fallback strategies at each phase heading), e.g., 'if the primary tool returns empty, use <fallback tool>', and add one example tool invocation with expected parameters to make Phase 0–2 guidance copy-paste ready.

DimensionReasoningScore

Conciseness

The body is dense and directive with no over-explanation of known concepts, but includes unnecessary duplication: the "Summary" section restates the eight analysis phases nearly verbatim from the Phases Overview, and the inline report skeleton duplicates content delegated to report-template.md. This matches the 3 anchor ("could be tightened") rather than 4 because the duplication is a noticeable, removable token cost.

3 / 5

Actionability

Guidance is mostly executable: concrete tool names per phase (e.g., `OpenTargets_get_disease_id_description_by_name`), a parameter table with examples, explicit thresholds ("Filter FDR < 0.05", "Cross-database validation 3+ DBs"), and a report filename convention. It falls short of 5 because no example tool invocations or Python snippets appear inline to cover the common cases.

4 / 5

Workflow Clarity

Nine phases are clearly sequenced with Phase 0 marked "ALWAYS FIRST" and conditional gating ("Cancer/Inflammation only", "if data available"), plus a completeness checklist as an end checkpoint. Not 5: there is no explicit validate/retry loop or fallback guidance at the phase level — fallback strategies are only deferred to tool-reference.md without per-phase pointers; not 3: sequence and most checkpoints are present.

4 / 5

Progressive Disclosure

References are well-signaled and one level deep ("See **phase-procedures.md** for detailed workflows", "See **report-template.md** for full template", plus a Reference Files section with descriptions). Not 5: the HuBMAP tool parameter table and the full report skeleton arguably belong in the referenced files rather than inline, and the five referenced files are not present in this bundle, so the structure could not be verified against actual files.

4 / 5

Total

15

/

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: concrete third-person capabilities, an explicit "Use for" trigger clause with distinctive platform names, and both what/when clearly answered. The only gap is a few natural synonyms (e.g., "spatial transcriptomics") that users would commonly say.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — "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" — with comprehensive coverage in third person voice. It matches the 5 anchor rather than 4 because coverage of actions is comprehensive, with no notable gaps.

5 / 5

Completeness

It explicitly answers both "what" (transforms SVGs, domain annotations, and tissue context into biological insights via named methods) and "when" ("Use for Visium, MERFISH, seqFISH, Slide-seq, spatial proteomics, and spatial multi-omics interpretation") with concrete trigger phrases, matching the 5 anchor exactly.

5 / 5

Trigger Term Quality

Trigger terms include "Use for Visium, MERFISH, seqFISH, Slide-seq, spatial proteomics, and spatial multi-omics interpretation" — strong platform coverage users would naturally say. It falls short of 5 because common natural synonyms such as "spatial transcriptomics" and "spatial domains" are missing; it is above 3 because keyword coverage is good rather than partial.

4 / 5

Distinctiveness Conflict Risk

The niche (spatial multi-omics interpretation) is clear and the platform-name triggers (Visium, MERFISH, seqFISH, Slide-seq) are highly distinctive, giving minimal conflict risk with adjacent gene/variant/drug-safety skills it explicitly excludes.

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