agentleFS
45ck45ck/open-genome-agent/.claude/skills/pharmacogenomics/SKILL.md

pharmacogenomics

Skill4 starsChanged 7 months agoMITView on GitHub

Generate a clearly separated pharmacogenomics section with conservative

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
  1. Distinctive:

    Start from already validated variant or haplotype inputs.

    line 33
  2. Distinctive:

    Keep the output in its own artifact and section.

    line 36
  3. Distinctive:

    Never tell the user to change medication directly from this output.

    line 40
  4. Distinctive:

    Never mix pharmacogenomics entries into the same summary bucket as disease findings.

    line 41
  5. Distinctive:

    If genotype-to-phenotype translation is incomplete, say so.

    line 42

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Start from already validated variant or haplotype inputs.
  2. Present outputs as medication-response clues, not prescriptions.
  3. Attach strong caveats and a human-review flag to every entry.
  4. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.