setup-workstation
Skill4 starsChanged 7 months agoMITView on GitHub
Prepare or validate a local genome-analysis workstation. Use before the
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
- nextflow-runnerSkill
- pharmacogenomicsSkill
- polygenic-riskSkill
- prioritize-findingsSkill
- query-variantsSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 37
Check whether expected tools are present:
- Very specific: line 45
Verify that runs/ exists and that raw genome paths are not inside .git/.
≈ “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
Setup workstation
Prepare or validate a local genome-analysis workstation. Use before the first run on a machine or when toolchain drift is suspected.
When to use
- new clone or new machine
- tool versions changed
- permissions or hook behavior need validation
Do not use when
- routine analysis on an already validated machine
Expected outputs
workstation_report.jsontool_versions.json
Goal
Validate that the local machine is ready for safe, reproducible genome analysis.
Procedure
- Detect the OS, shell, Python version, and writable workspace.
- Check whether expected tools are present:
python3samtoolsbcftoolsvepplink2nextflow(optional in the MVP)
- Record versions and missing tools into a workstation report.
- Verify that
runs/exists and that raw genome paths are not inside.git/. - Confirm hook scripts are executable where relevant.
Output contract
Emit a compact machine-readable report and a plain-language summary. Missing tools should be reported explicitly instead of guessed around.
Escalate when
- required tools are missing
- the repo is not trusted
- permissions or sandbox settings are unexpectedly broad
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.

