washu-claude-skills

Review a scientific figure across three dimensions: aesthetics (Wilke/Tufte), accuracy (claims match underlying data), and interpretability (main message is visually dominant). Use when the user asks to review, critique, audit, check, or polish a figure or figure script. Also use for "does this figure work?", "what's wrong with this plot?", or "is this publication-ready?".

Prime a session with the WashU HPC computing environment (HTCF and RIS Compute2) so cluster work can be managed without re-explaining the setup. Covers connection, filesystems and quotas, conda/LMOD software, SLURM partitions and sbatch headers, containers, job monitoring, and the failure modes specific to each cluster. Use when the user asks about submitting, monitoring, or debugging jobs on HTCF or RIS, installing software on the cluster, cluster storage, or SSH/VPN access to WashU compute.

Gracefully prepare a Claude Code session for a reboot or restart. Captures durable state before context is lost: updates project memories, records running HPC jobs, checks git status, flags time-sensitive timers, and prints a restart checklist with the first action to take after coming back. Use when the user says they are about to reboot, restart, shut down, or end a session, or asks to "save state before I restart".

Verify scientific identifiers (UniProt accessions, Pfam IDs, DOIs, PMIDs, NCBI accessions) in a project against authoritative sources. Use when generating reference data (positive controls, seed lists, citations), before committing identifier lists, or auditing an existing project for hallucinated accessions. Trigger when the user says "verify references", "check accessions", "audit my IDs", or asks whether protein/paper IDs are correct.