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

polygenic-risk

Skill4 starsChanged 7 months agoMITView on GitHub

Run optional polygenic or trait-style scoring workflows and label all

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Run optional polygenic or trait-style scoring workflows and label all outputs as probabilistic.

    line 17
  2. Distinctive:

    Run optional PRS-style analysis without letting probabilistic signals look clinical.

    line 32
  3. Distinctive:

    Keep PRS outputs in their own file and summary block.

    line 39
  4. Very specific:

    Never merge PRS output into verified findings.

    line 43
  5. Distinctive:

    Never present a timeline or certainty.

    line 44
  6. Distinctive:

    If score portability is unclear, say so explicitly.

    line 45

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

Polygenic risk

Run optional polygenic or trait-style scoring workflows and label all outputs as probabilistic. Use only when requested and keep results separate from direct variant findings.

When to use

  • the user explicitly requests PRS or broad predisposition scoring

Do not use when

  • the user expects diagnosis-like certainty
  • the toolchain or reference score set is not available

Expected outputs

  • prs_scores.json
  • prs_notes.md

Goal

Run optional PRS-style analysis without letting probabilistic signals look clinical.

Procedure

  1. Confirm that the user explicitly wants this class of output.
  2. Record which score set or method was used.
  3. Present results as relative or exploratory signals only.
  4. Keep PRS outputs in their own file and summary block.

Guardrails

  • Never merge PRS output into verified findings.
  • Never present a timeline or certainty.
  • If score portability is unclear, say so explicitly.

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.