What problem does it solve? Running 10x Genomics SpaceRanger on FGCZ infrastructure involves many platform-specific pitfalls: wrong demultiplexing masks for VisiumHD (R1=43bp), missing slide/area/image metadata in SUSHI datasets, probe-based vs 3' polyA chemistry confusion, and Ruby API submission gotchas. This Skill encodes the exact workflows, parameters, and troubleshooting steps to get SpaceRanger jobs right the first time. ## Core Features & Use Cases - Platform decision tree: Covers standard Visium (frozen/FFPE), CytAssist, VisiumHD, and CytAssist VisiumHD (H1- and H2- slides) with correct BasesMask, probeset, and cmdOptions for each. - SUSHI dataset preparation: SQL templates for creating annotated child datasets with Slide, Area, Image, and CytaImage columns, plus JPG-to-TIFF conversion for H&E images. - Demux and submission recovery: Manual bcl2fastq workflow for VisiumHD lanes, Ruby API submission with Hash-default parameter fixes, and a troubleshooting table for common failures. - Use Case: A bioinformatician receives VisiumHD CytAssist FFPE samples, verifies chemistry via TSO scan, prepares the annotated SUSHI dataset, and submits SpaceRangerCount 4.1.0 with the correct probeset and --disable-cell-annotation flag. ## Quick Start Ask the agent to prepare and submit a SpaceRangerCount job in SUSHI for your Visium or VisiumHD samples, specifying the slide type and species.