detect-build-normalize
Skill4 starsChanged 7 months agoMITView on GitHub
Detect the reference build and create a normalized derived copy without
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
- generate-reportSkill
- ingest-vcfSkill
- nextflow-runnerSkill
- pharmacogenomicsSkill
- polygenic-riskSkill
- prioritize-findingsSkill
- query-variantsSkill
- setup-workstationSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 38
If build is still uncertain, mark it ambiguous rather than guessing.
- Distinctive: line 39
Create a derived normalized file in a run-specific output directory.
- Distinctive: line 46
Do not overwrite source inputs.
- Distinctive: line 47
If a liftover or reference swap would be needed, stop and surface that requirement.
≈ “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
Detect build and normalize
Detect the reference build and create a normalized derived copy without touching the raw input. Use before annotation or cross-tool comparison.
When to use
- build is unknown or ambiguous
- contig naming style differs across tools
- annotation expects normalized variants
Do not use when
- the input is already validated and normalized for the selected toolchain
Expected outputs
derived/normalized.vcf.gznormalization_notes.json
Goal
Resolve build and representation issues before downstream tools disagree.
Procedure
- Inspect contig style (
chr1vs1) and obvious build indicators. - If build is still uncertain, mark it ambiguous rather than guessing.
- Create a derived normalized file in a run-specific output directory.
- Preserve raw input hashes and link the derived file back to them.
- Record every normalization step in machine-readable notes.
Guardrails
- Derived files belong under
runs/<run_id>/derived/. - Do not overwrite source inputs.
- If a liftover or reference swap would be needed, stop and surface that requirement.
Escalate when
- the build is ambiguous
- contig naming is mixed
- normalization would drop or alter records unexpectedly
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.

