What problem does it solve? FGCZ-specific knowledge — paths, hostnames, tool relationships, and conventions — is tribal knowledge that agents and new staff must rediscover every session. This skill grounds all other FGCZ skills in a shared institutional substrate so downstream workflows do not re-derive context. ## Core Features & Use Cases - Institutional substrate: Documents what FGCZ is, its five organizational groups, user personas, and the canonical data flow from B-Fabric metadata through sequencing, demultiplexing, SUSHI analysis, and gStore delivery. - Tech stack reference: Maps the full operational stack — B-Fabric LIMS, SUSHI, ezRun, Draugr, gStore/gtools, SLURM, GitLab, ShinyProxy — including how the components compose and who owns them. - Convention defaults: Codifies agent rules such as gStore read-only semantics (write only via g-req copynow), read-only gi_* conda environments, GPU --constraint=L40S preference, and ezRun report styling (300 DPI, polychrome, qs2). - Use Case: At the start of a session involving a SUSHI app or a pXXXXX project path, load this skill so the agent correctly interprets /srv/gstore/projects/pNNNNN/, knows not to rm in gStore, and routes deliverables through gtools. ## Quick Start Load the fgcz-context skill at the start of any FGCZ-related session before invoking other marketplace skills.