pharmacogenomics
Skill4 starsChanged 7 months agoMITView on GitHub
Generate a clearly separated pharmacogenomics section with conservative
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
- 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
- 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 26
Start from already validated variant or haplotype inputs.
- Distinctive: line 29
Keep the output in its own artifact and section.
- Distinctive: line 33
Never tell the user to change medication directly from this output.
- Distinctive: line 34
Never mix pharmacogenomics entries into the same summary bucket as disease findings.
- Distinctive: line 35
If genotype-to-phenotype translation is incomplete, say so.
≈ “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
Pharmacogenomics
Generate a clearly separated pharmacogenomics section with conservative language and explicit human-review flags. Use only when the user requests drug-response analysis.
When to use
- the user explicitly requests drug-response or medication-response clues
Do not use when
- the user only wants ancestry or general variant analysis
Expected outputs
pharmacogenomics.json
Goal
Produce a conservative drug-response section that remains clearly separate from diagnosis.
Procedure
- Start from already validated variant or haplotype inputs.
- Present outputs as medication-response clues, not prescriptions.
- Attach strong caveats and a human-review flag to every entry.
- Keep the output in its own artifact and section.
Guardrails
- Never tell the user to change medication directly from this output.
- Never mix pharmacogenomics entries into the same summary bucket as disease findings.
- If genotype-to-phenotype translation is incomplete, say so.
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.

