tooluniverse-spatial-transcriptomics

mims-harvard/tooluniverse · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/mims-harvard/tooluniverse --skill tooluniverse-spatial-transcriptomics
0 commentsdiscussion
summary

Comprehensive analysis of spatially-resolved transcriptomics data to understand gene expression patterns in tissue architecture context. Combines expression profiling with spatial coordinates to reveal tissue organization, cell-cell interactions, and spatially variable genes.

skill.md

Spatial Transcriptomics Analysis

Comprehensive analysis of spatially-resolved transcriptomics data to understand gene expression patterns in tissue architecture context. Combines expression profiling with spatial coordinates to reveal tissue organization, cell-cell interactions, and spatially variable genes.

LOOK UP, DON'T GUESS

When uncertain about any scientific fact, SEARCH databases first rather than reasoning from memory. A database-verified answer is always more reliable than a guess.

When to Use This Skill

Triggers:

  • User has spatial transcriptomics data (Visium, MERFISH, seqFISH, etc.)
  • Questions about tissue architecture or spatial organization
  • Spatial gene expression pattern analysis
  • Cell-cell proximity or neighborhood analysis requests
  • Tumor microenvironment spatial structure questions
  • Integration of spatial with single-cell data
  • Spatial domain identification
  • Tissue morphology correlation with expression

Example Questions:

  1. "Analyze this 10x Visium dataset to identify spatial domains"
  2. "Which genes show spatially variable expression in this tissue?"
  3. "Map the tumor microenvironment spatial organization"
  4. "Find genes enriched at tissue boundaries"
  5. "Identify cell-cell interactions based on spatial proximity"
  6. "Integrate spatial transcriptomics with scRNA-seq annotations"

Core Capabilities

  • Data Import: 10x Visium, MERFISH, seqFISH, Slide-seq, STARmap, Xenium formats
  • Quality Control: Spot/cell QC, spatial alignment verification, tissue coverage
  • Normalization: Spatial-aware normalization accounting for tissue heterogeneity
  • Spatial Clustering: Identify spatial domains with similar expression profiles
  • Spatial Variable Genes: Find genes with non-random spatial patterns
  • Neighborhood Analysis: Cell-cell proximity, spatial neighborhoods, niche identification
  • Integration: Merge with scRNA-seq for cell type mapping (Cell2location, Tangram, SPOTlight)
  • Ligand-Receptor Spatial: Map cell communication in tissue context via OmniPath

Supported Platforms

  • 10x Visium: 55um spots (~50 cells/spot), genome-wide, includes H&E image — most common
  • MERFISH/seqFISH: Single-cell resolution, 100-10,000 targeted genes, imaging-based
  • Slide-seq/V2: 10um beads, genome-wide — higher resolution than Visium
  • Xenium: Single-cell/subcellular, 300+ targeted genes (10x platform)

Workflow Overview

Input: Spatial Transcriptomics Data + Tissue Image
    |
    v
Phase 1: Data Import & QC
    |-- Load spatial coordinates + expression matrix
    |-- Load tissue histology image
    |-- Quality control per spot/cell (min 200 genes, 500 UMI, <20% MT)
    |-- Align spatial coordinates to tissue
    |
    v
Phase 2: Preprocessing
    |-- Normalization (spatial-aware methods)
    |-- Highly variable gene selection (top 2000)
    |-- Dimensionality reduction (PCA)
    |-- Spatial lag smoothing (optional)
    |
    v
Phase 3: Spatial Clustering
    |-- Build spatial neighbor graph (squidpy)
    |-- Graph-based clustering with spatial constraints (Leiden)
    |-- Annotate domains with marker genes (Wilcoxon)
    |-- Visualize domains on tissue
    |
    v
Phase 4: Spatial Variable Genes
    |-- Test spatial autocorrelation (Moran's I, Geary's C)
    |-- Filter significant spatial genes (FDR < 0.05)
    |-- Classify pattern types (gradient, hotspot, boundary, periodic)
    |
    v
Phase 5: Neighborhood Analysis
    |-- Define spatial neighborhoods (k-NN, radius)
    |-- Calculate neighborhood composition (squidpy nhood_enrichment)
    |-- Identify interaction zones between domains
    |
    v
Phase 6: Integration with scRNA-seq
    |-- Cell type deconvolution (Cell2location, Tangram, SPOTlight)
    |-- Map cell types to spatial locations
    |-- Validate with marker genes
    |
    v
Phase 7: Spatial Cell Communication
    |-- Identify proximal cell type pairs
    |-- Query ligand-receptor database (OmniPath)
    |-- Score spatial interactions (squidpy ligrec)
    |-- Map communication hotspots
    |
    v
Phase 8: Generate Spatial Report
    |-- Tissue overview with domains
    |-- Spatially variable genes
    |-- Cell type spatial maps
    |-- Interaction networks in tissue context

Phase Summaries

Phase 1: Data Import & QC

Load platform-specific data (scanpy read_visium for Visium). Apply QC filters: min 200 genes/spot, min 500 UMI/spot, max 20% mitochondrial. Verify spatial alignment with tissue image overlay.

Phase 2: Preprocessing

Normalize to median total counts, log-transform, select top 2000 HVGs. Optional spatial smoothing via neighbor averaging (useful for noisy data but blurs boundaries).

Phase 3: Spatial Clustering

PCA (50 components) followed by spatial neighbor graph construction (squidpy). Leiden clustering with spatial constraints yields spatial domains. Find domain markers via Wilcoxon rank-sum test.

Phase 4: Spatially Variable Genes

Moran's I statistic tests spatial autocorrelation: I > 0 = clustering, I ~ 0 = random, I < 0 = checkerboard. Filter by FDR < 0.05. Classify patterns as gradient, hotspot, boundary, or periodic.

Phase 5: Neighborhood Analysis

Neighborhood enrichment analysis (squidpy) tests whether cell types/domains are co-localized beyond random expectation. Identify interaction zones at domain boundaries using k-NN spatial graphs.

Phase 6: scRNA-seq Integration

Cell type deconvolution maps single-cell annotations to spatial spots. Methods: Cell2location (recommended for Visium), Tangram, SPOTlight. Produces cell type fraction estimates per spot.

Phase 7: Spatial Cell Communication

Combine spatial proximity with ligand-receptor databases. Key ToolUniverse tools:

  • OmniPath_get_ligand_receptor_interactions — 14,000+ L-R pairs from CellPhoneDB, CellChatDB, etc. Use partners param for specific genes.
  • OmniPath_get_intercell_roles — classify proteins as ligand/receptor/ECM. Use proteins param.
  • OmniPath_get_cell_communication_annotations — CellPhoneDB/CellChatDB pathway annotations. Use proteins param.
  • OmniPath_get_signaling_interactions — intracellular signaling downstream of receptors.

Score interactions by co-expression of L-R pairs in proximal cells. Map hotspots where interaction scores peak.

Phase 7.5: Data Discovery & Gene Context (ToolUniverse API tools)

For dataset discovery and gene annotation (API-based, no local computation needed):

  • geo_search_datasets / OmicsDI_search_datasets / NCBI_SRA_search_runs — find spatial TX datasets
  • UniProt_get_function_by_accession — protein function for stroma/immune markers
  • STRING_get_network — protein interaction networks for key markers
  • kegg_search_pathway / kegg_get_pathway_info — relevant metabolic/signaling pathways
  • DGIdb_get_drug_gene_interactions — druggable targets in the spatial context
  • PubMed_search_articles — literature for spatial biology context

API tools vs. local computation: Phases 1-2 (data import, QC) and Phases 3-6 (clustering, SVGs, neighborhoods, deconvolution) require local Python with squidpy/scanpy. Phase 7 L-R databases and Phase 7.5 gene context use ToolUniverse API tools.

Phase 8: Report Generation

See report_template.md for full example output.


Integration with ToolUniverse Skills

  • tooluniverse-single-cell: scRNA-seq reference for deconvolution (Phase 6) and L-R database (Phase 7)
  • tooluniverse-gene-enrichment: Pathway enrichment for spatial domain marker genes (Phase 3)
  • tooluniverse-multi-omics-integration: Integration with other omics layers (Phase 8)

ToolUniverse Data Retrieval Tools

HuBMAP Spatial Atlas Tools

Use HuBMAP tools to discover published spatial biology datasets for reference, validation, or cross-study comparison.

Availability Note: HuBMAP_search_datasets, HuBMAP_list_organs, and HuBMAP_get_dataset may not be registered in your ToolUniverse instance. Verify with tu.list_tools() before use. If unavailable, use OmicsDI (OmicsDI_search_datasets(query="spatial transcriptomics kidney")) or CELLxGENE (CELLxGENE_get_cell_metadata) as reliable alternatives for spatial dataset discovery.

  • HuBMAP_search_datasets: Search published datasets by organ (code, e.g. "LK"=Left Kidney, "BR"=Brain), dataset_type, query, limit
  • HuBMAP_list_organs: List all organs with codes and UBERON IDs (no required params)
  • HuBMAP_get_dataset: Get detailed metadata for a specific hubmap_id (e.g. "HBM626.FHJD.938")

Organ codes: LK/RK=Kidney, LI=Large Intestine, SI=Small Intestine, HT=Heart, LV=Liver, LU=Lung, SP=Spleen, BR=Brain, PA=Pancreas, SK=Skin.

When to use:

  • Finding reference spatial datasets for a given organ/tissue
  • Identifying available spatial assay types (Visium, CODEX, MERFISH) for a tissue
  • Cross-referencing donor metadata (age, sex) for spatial datasets
  • Retrieving DOI links for published spatial atlas datasets

Fallback if HuBMAP tools unavailable:

# Use OmicsDI for spatial dataset discovery
result = tu.tools.OmicsDI_search_datasets(query="spatial transcriptomics kidney Visium")

# Use CELLxGENE for cell-level expression context
result = tu.tools.CELLxGENE_get_cell_metadata(tissue="kidney")
# Example: Find spatial datasets for kidney (if HuBMAP tools available)
result = tu.tools.HuBMAP_search_datasets(organ="LK", limit=5)
# Returns: {data: {total, returned, datasets: [{hubmap_id, title, dataset_type, organ, doi_url, ...}]}}

# Example: Get all available organs
organs = tu.tools.HuBMAP_list_organs()
# Returns: {data: {total, organs: [{code, term, organ_uberon, rui_supported}]}}

Example Use Cases

Use Case 1: Tumor Microenvironment Mapping

Question: "Map the spatial organization of tumor, immune, and stromal cells" Workflow: Load Visium -> QC -> Spatial clustering -> Deconvolution -> Interaction zones -> L-R analysis -> Report

Use Case 2: Developmental Gradient Analysis

Question: "Identify spatial gene expression gradients in developing tissue" Workflow: Load spatial data -> SVG analysis -> Classify gradient patterns -> Map morphogens -> Correlate with cell fate -> Report

Use Case 3: Brain Region Identification

Question: "Automatically segment brain tissue into anatomical regions" Workflow: Load Visium brain -> High-resolution clustering -> Match to known regions -> Validate with Allen Brain Atlas -> Report


Quantified Minimums

  • At least 500 spatial locations after QC
  • Filter low-quality spots (min 200 genes, min 500 UMI, <20% MT) and verify alignment
  • At least one spatial clustering method (graph-based with spatial constraints)
  • Spatially variable genes tested with Moran's I or equivalent (FDR < 0.05)
  • Spatial plots on tissue images for all major findings
  • Report covers: domains, spatial genes, cell type maps, key interactions

Reasoning Framework

Starting Point: What Is the Spatial Question?

Spatial data adds location to expression. The key question: is the spatial pattern driven by cell type composition (trivial) or by spatially-regulated gene expression within the same cell type (interesting)? Deconvolution helps distinguish these.

Before interpreting any spatially variable gene (SVG), ask:

  1. Does this gene simply mark a cell type that is spatially restricted? (e.g., a T-cell marker enriched in immune infiltrate zones — expected, not informative)
  2. Or is the gene differentially expressed within the same cell type depending on its spatial position? (e.g., a fibroblast gene upregulated at the tumor-stroma boundary — spatially regulated, biologically interesting)

To distinguish these: (a) run deconvolution (Cell2location, Tangram) to get cell type fractions per spot; (b) regress SVG expression against cell type fraction; (c) if the spatial pattern persists after controlling for cell type composition, it reflects genuine spatial regulation. Always look up the gene's known biology before interpreting — check UniProt function and STRING interactions rather than guessing.

Evidence Grading

  • T1: Validated by orthogonal method (IHC, smFISH, known anatomy) — e.g., spatial domain matches histology-confirmed tumor margin
  • T2: Statistically significant, biologically consistent — SVG with Moran's I > 0.3 and FDR < 0.01 in expected tissue region
  • T3: Computationally identified, awaiting validation — novel spatial domain from clustering with no histological correlate
  • T4: Exploratory or artifact-prone — low-UMI edge spots, domains driven by batch effects

Interpretation Guidance

Spatial domains: Domains represent regions of coherent gene expression, often corresponding to tissue architecture (tumor core, stroma, immune infiltrate, necrosis). A domain is biologically meaningful when its marker genes align with known cell type signatures. Domains at tissue boundaries (e.g., tumor-stroma interface) are particularly informative for microenvironment studies.

Cell-cell proximity significance: Neighborhood enrichment z-scores > 2 indicate cell types co-localize more than expected by chance. Negative z-scores indicate spatial avoidance. Interpret in biological context: immune cell enrichment near tumor cells may indicate active immune response or immunosuppressive niche depending on the cell types involved (e.g., CD8+ T cells vs. Tregs).

Spatially variable genes (SVGs): Moran's I > 0.3 with FDR < 0.05 indicates strong spatial patterning. Classify SVGs by pattern: gradients (morphogen signaling, e.g., WNT along crypt-villus axis), hotspots (focal expression in immune aggregates), boundary genes (enriched at domain interfaces, e.g., epithelial-mesenchymal transition markers). SVGs with known spatial biology roles (e.g., tissue polarity genes) are higher confidence than novel candidates.

Synthesis Questions

A complete spatial transcriptomics report should answer:

  1. What spatial domains were identified, and do they correspond to known tissue architecture?
  2. Which genes show significant spatial variability, and what pattern types do they exhibit?
  3. Are specific cell type pairs enriched or depleted in spatial proximity?
  4. What ligand-receptor interactions are active at domain boundaries or cell-cell interfaces?
  5. How do spatial findings compare to bulk or single-cell data from the same tissue type?

Programmatic Access (Beyond Tools)

When ToolUniverse tools return metadata but you need the actual expression matrices:

import scanpy as sc, pandas as pd, requests, io

# Load h5ad (most common format for spatial/single-cell)
adata = sc.read_h5ad("spatial_data.h5ad")

# Load 10X Visium output directory
adata = sc.read_visium("path/to/spaceranger_output/")

# Download from GEO supplementary files
geo_id = "GSE123456"
# Check for h5ad or MTX in supplementary files
url = f"https://www.ncbi.nlm.nih.gov/geo/query/acc.cgi?acc={geo_id}&targ=gsm&view=data"

# Load 10X MTX format (matrix + barcodes + features)
adata = sc.read_10x_mtx("filtered_feature_bc_matrix/", var_names="gene_symbols")

# HuBMAP data portal
# Search at https://portal.hubmapconsortium.org/search then download via globus or direct link
# Human Cell Atlas: https://data.humancellatlas.org/ — download h5ad/loom files

See tooluniverse-data-wrangling skill for format cookbook and bulk download patterns.


Limitations

  • Resolution: Visium spots contain multiple cells (not single-cell)
  • Gene coverage: Imaging methods have limited gene panels
  • 3D structure: Most platforms are 2D sections
  • Tissue quality: Requires well-preserved tissue for imaging
  • Computational: Large datasets require significant memory
  • Reference dependency: Deconvolution quality depends on scRNA-seq reference

References

Methods:

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/mims-harvard/tooluniverse --skill tooluniverse-spatial-transcriptomics

The skills CLI fetches tooluniverse-spatial-transcriptomics from GitHub repository mims-harvard/tooluniverse and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/tooluniverse-spatial-transcriptomics

Reload or restart Cursor to activate tooluniverse-spatial-transcriptomics. Access the skill through slash commands (e.g., /tooluniverse-spatial-transcriptomics) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.433 reviews
  • Pratham Ware· Dec 20, 2024

    Keeps context tight: tooluniverse-spatial-transcriptomics is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Lucas Dixit· Dec 16, 2024

    tooluniverse-spatial-transcriptomics has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Yuki Wang· Dec 16, 2024

    Keeps context tight: tooluniverse-spatial-transcriptomics is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Dhruvi Jain· Dec 12, 2024

    Solid pick for teams standardizing on skills: tooluniverse-spatial-transcriptomics is focused, and the summary matches what you get after install.

  • Anaya Iyer· Dec 8, 2024

    Solid pick for teams standardizing on skills: tooluniverse-spatial-transcriptomics is focused, and the summary matches what you get after install.

  • Hiroshi Desai· Nov 27, 2024

    We added tooluniverse-spatial-transcriptomics from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Omar Iyer· Nov 7, 2024

    tooluniverse-spatial-transcriptomics fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Oshnikdeep· Nov 3, 2024

    We added tooluniverse-spatial-transcriptomics from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Soo Flores· Oct 26, 2024

    We added tooluniverse-spatial-transcriptomics from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Ganesh Mohane· Oct 22, 2024

    tooluniverse-spatial-transcriptomics fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 33

1 / 4