analysis-workflow
Organize multi-step scientific analyses into reproducible, self-contained modules. Use for workflows such as QC→PCA→DEG→GSEA that produce scripts, inputs, figures, tables, and methods. Creates a stable module layout, records exact inputs/parameters/package and database versions in each module README, keeps large data as references instead of copies, and verifies outputs before completion.
Profile →npx skills add xuzhougeng/wisp-science --skill analysis-workflow --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Reproducible Analysis Modules Use this skill for a scientific workflow with two or more analysis stages or when a stage produces scripts plus result files. It defines project organization and methods capture; load `figure-style` as well whenever a stage creates or revises a plot. ## 1. Plan module boundaries Before writing outputs, list the modules and the dependency edges between them. Use stable ASCII names. Conventional acronyms such as `QC`, `PCA`, `DEG`, and `GSEA` may stay uppercase; otherwise prefer a short kebab-case name. Respect a compatible layout that already exists. Do not reorganize unrelated user files merely to impose this convention. ## 2. Default module layout Create only directories the module actually needs: ```text <module>/ ├── scripts/ ├── input/ ├── output/ │ ├── figures/ │ └── tables/ └── README.md ``` - `scripts/` contains the executable source for this module. - `input/` contains small module-specific inputs or a manifest/reference to the canonical data. Do not duplicate a large dataset by default. - `output/figures/` contains rendered figures from this module only. - `output/tables/` contains machine-readable results from this module only. - `README.md
- 1. Plan module boundaries
- 2. Default module layout
- 3. Make outputs attributable
- 4. Update README.md at module completion
- 5. Capture exact versions without dumping the world
- 6. Finish the workflow
What does the analysis-workflow skill do?
Organize multi-step scientific analyses into reproducible, self-contained modules. Use for workflows such as QC→PCA→DEG→GSEA that produce scripts, inputs, figures, tables, and methods. Creates a stable module layout, records exact inputs/parameters/package and database versions in each module README, keeps large data as references instead of copies, and verifies outputs before completion.
How do I install it?
Run `npx skills add xuzhougeng/wisp-science --skill analysis-workflow --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From xuzhougeng/wisp-science, a repository with 895 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.