query-variants
Skill4 starsChanged 7 months agoMITView on GitHub
Answer targeted questions about genes, rsIDs, coordinates, or variant
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
- 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 41
Prefer exact local evidence over speculative interpretation.
- Distinctive: line 43
If nothing matches, say so directly.
- Distinctive: line 48
Do not turn a simple query into a full report unless asked.
- Distinctive: line 49
If a query depends on annotation that is not yet available, state that dependency.
≈ “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
Query variants
Answer targeted questions about genes, rsIDs, coordinates, or variant panels from local genome files. Use for focused exploration before full reporting.
When to use
- the user asks about a gene, variant, or coordinate range
- you need quick local evidence without running a full pipeline
Do not use when
- a full end-to-end report is required
Expected outputs
query_results.tsvquery_notes.md
Goal
Answer targeted local questions quickly and with file-level provenance.
Procedure
- Convert the user request into a precise local query:
- gene
- rsID
- coordinate interval
- panel list
- Prefer exact local evidence over speculative interpretation.
- Return raw hits, file locations, and concise caveats.
- If nothing matches, say so directly.
Guardrails
- Keep scope narrow.
- Do not turn a simple query into a full report unless asked.
- If a query depends on annotation that is not yet available, state that dependency.
Output contract
Emit query results plus a short note describing how the query was executed.
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.

