nextflow-runner
Skill4 starsChanged 7 months agoMITView on GitHub
Run or prepare reproducible Nextflow workflows for heavy genomics jobs.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- annotate-variantsSkill
- detect-build-normalizeSkill
- generate-reportSkill
- ingest-vcfSkill
- nextflow-runnerSkill
- pharmacogenomicsSkill
- polygenic-riskSkill
- prioritize-findingsSkill
- query-variantsSkill
- setup-workstationSkill
- annotate-variantsSkill
- detect-build-normalizeSkill
- generate-reportSkill
- ingest-vcfSkill
- pharmacogenomicsSkill
- polygenic-riskSkill
- prioritize-findingsSkill
- query-variantsSkill
- setup-workstationSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Run or prepare reproducible Nextflow workflows for heavy genomics jobs.
- Distinctive: line 37
Prefer schema-driven configuration and captured manifests over handwritten one-off commands.
- Distinctive: line 42
Do not run large workflows implicitly.
- Distinctive: line 43
Do not treat a pipeline launch as success.
- Distinctive: line 44
Keep this skill separate from lightweight local questioning.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Nextflow runner
Run or prepare reproducible Nextflow workflows for heavy genomics jobs. Use only for explicit workflow execution, not routine question answering.
When to use
- raw-read or heavy pipeline execution is explicitly requested
- the environment is ready for Nextflow
Do not use when
- a VCF-first local analysis is sufficient
Expected outputs
workflow_run.jsonpipeline_logs/
Goal
Handle heavy pipeline execution in a reproducible way.
Procedure
- Confirm that pipeline execution is explicitly requested.
- Validate environment assumptions before running anything expensive.
- Prefer schema-driven configuration and captured manifests over handwritten one-off commands.
- Save pipeline commands, params, and logs into the run directory.
Guardrails
- Do not run large workflows implicitly.
- Do not treat a pipeline launch as success; monitor completion and surface failures.
- Keep this skill separate from lightweight local questioning.
References
See references/README.md for durable notes and scripts/ for deterministic helpers.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

