quickgo-database
Skill2 starsChanged 3 months agoMITView on GitHub
Query the QuickGO and Evidence & Conclusion Ontology (ECO) REST API. Use this when you need to map genes to biological processes, molecular functions, or cellular components, find genes associated with a specific pathway/GO term, or explore the Gene Ontology hierarchy. Do not use for querying drug targets (use OpenTargets) or mechanistic signaling pathway diagrams (use KEGG).
3 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- Osmosy/vector-geneedited, first seen Oct 13, 2026
- google-deepmind/science-skillsedited, first seen Jul 1, 2026
- uppifyagency/boilerplate-saas-2026edited, first seen Jun 2, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 3
- google-deepmind/science-skills★ 3.4k98% same
- uppifyagency/boilerplate-saas-2026★ 1100% same
- Osmosy/vector-gene★ 098% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository93 other files it gives its agents.
- AGENTS.mdAGENTS.md
- npm/AGENTS.mdAGENTS.md
- advanced-image-slicing-skillSkill
- agents-sdkSkill
- agent-weaver-builderSkill
- alphafold-database-fetch-and-analyzeSkill
- alphagenome-single-variant-analysisSkill
- animation-scroll-effectsSkill
- backend-api-shield-servicesSkill
- chembl-databaseSkill
- chronicle-logger-timestampSkill
- cicd-automation-deploySkill
- cinematic-animator-gsapSkill
- clinical-trials-databaseSkill
- clinvar-databaseSkill
- cloudflare-ai-resourcesSkill
- cloudflare-email-serviceSkill
- cloudflare-one-migrationsSkill
- cloudflare-oneSkill
- cloudflareSkill
- data-modeler-schemaSkill
- dbsnp-databaseSkill
- design-system-master-hslSkill
- durable-objectsSkill
- embl-ebi-olsSkill
- encode-ccres-databaseSkill
- ensembl-databaseSkill
- explode-animation-skillSkill
- find-skillsSkill
- foldseek-structural-searchSkill
- frontend-clean-coder-jsSkill
- gnomad-databaseSkill
- google-antigravity-sdkSkill
- gtex-databaseSkill
- human-protein-atlas-databaseSkill
- inner-learner-feedbackSkill
- integrative-architect-docsSkill
- intent-observer-audit360Skill
- interpro-databaseSkill
- isolated-sandbox-environmentSkill
- jaspar-databaseSkill
- k6-load-testingSkill
- lightweight-dep-managerSkill
- literature-search-arxivSkill
- literature-search-biorxivSkill
- literature-search-europepmcSkill
- literature-search-openalexSkill
- maestro-hadi-orchestrationSkill
- majlis-rulesSkill
- marketing-funnel-skillSkill
- ncbi-sequence-fetchSkill
- neuro-marketing-copywriterSkill
- nuclei-security-auditorSkill
- openfda-databaseSkill
- opentargets-databaseSkill
- owasp-zap-api-shieldSkill
- pdb-databaseSkill
- pdf-scan-layer-cleanerSkill
- premium-visual-polish-skillSkill
- protein-sequence-msaSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. 3 are common, 0 are distinctive, and 4 are very specific to this project.
3
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 31
uv: Read the uv skill and follow its Setup instructions to ensure uv is installed and on PATH. - Very specific: line 33
User Notification: If LICENSE_NOTIFICATION.txt does not already exist in this skill directory then (1) prominently notify the user to check …
- Common: line 47
Use the Wrapper: ALWAYS execute the provided helper scripts to query the database rather than accessing the database directly.
- Very specific: line 52
Output Files: Always use the --output flag to save responses to a file incrementally or parse via jq.
- Very specific: line 56
Taxon Filtering: Use --taxonId 9606 to restrict results to Human when analysing clinical or human genomic data.
- Common: line 58
Notification: If this skill is used, ensure this is mentioned in the output.
- Common: line 119
If you have a list of candidate genes and want a high-level functional summary, you can map them up to a predefined GO Slim.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
QuickGO Database Skill
GO (Gene Ontology) annotations are one of the main ways to label a gene's function. QuickGO is a fast, web-based browser for the GO and Evidence & Conclusion Ontology (ECO), maintained by the Gene Ontology Annotation (GOA) group at EMBL-EBI.
It provides a centralised resource to explore the functional attributes of gene products (proteins, RNA, and complexes). It is a primary tool for functional annotation mapping since it allows you to link a gene (e.g., USH2A) to its specific biological processes (e.g. sensory perception of light stimulus), molecular functions, and cellular components.
Prerequisites
uv: Read theuvskill and follow its Setup instructions to ensureuvis installed and on PATH.- User Notification: If LICENSE_NOTIFICATION.txt does not already exist in this skill directory then (1) prominently notify the user to check the terms at https://www.ebi.ac.uk/QuickGO/ and https://www.ebi.ac.uk/QuickGO/api/index.html, then (2) create the file recording the notification text and timestamp.
Usage
This skill provides a Python CLI wrapper scripts/quickgo_tool.py that queries
the QuickGO REST API. It handles formatting the requests, respecting rate
limits, and safely storing the potentially large JSON responses.
Core Rules
- Use the Wrapper: ALWAYS execute the provided helper scripts to query the database rather than accessing the database directly. The scripts automatically enforce the required rate limit gracefully.
- Pagination & Limits: Restrict endpoints to a maximum of 100 results per
page using
--limit 100and the--pageparameter for larger datasets. - Output Files: Always use the
--outputflag to save responses to a file incrementally or parse viajq. - Evidence Codes: Prioritize experimental evidence (
ECO:0000269) over electronic (ECO:0000501) to avoid noisy predictions. - Taxon Filtering: Use
--taxonId 9606to restrict results to Human when analysing clinical or human genomic data. - Notification: If this skill is used, ensure this is mentioned in the output.
The tool has four main subcommands:
go: For retrieving information about GO terms (e.g. definitions, ancestors, descendants, and slims). See references/go_terms.md.annotation: For finding functional annotations linking gene products to GO terms. This is your primary functional mapper. See references/annotations.md.geneproduct: For resolving gene symbols (likePROC) to their formal database identifiers. See references/gene_products.md.eco: For Evidence & Conclusion Ontology terms (used in annotations to indicate how an annotation was derived, e.g. experimental vs electronic). See references/eco_terms.md.
Common Workflows
1. Map a gene to its functions (Annotations)
To find out what a gene does, you must first resolve its symbol to a UniProtKB
ID, and then query its annotations. Often it is best to filter for experimental
evidence (e.g. ECO:0000269 for EXP, or others like IDA, IMP) to avoid noisy
electronic predictions.
# Step 1: Find the UniProtKB ID for human (9606) gene PROC
uv run scripts/quickgo_tool.py geneproduct search --query "PROC" --taxonId 9606 --limit 5 --output proc_id.json
# (Look at proc_id.json, observe the ID is e.g., UniProtKB:P04070)
# Step 2: Find experimental GO annotations for that ID
uv run scripts/quickgo_tool.py annotation search --geneProductId "UniProtKB:P04070" --taxonId 9606 --evidenceCode "ECO:0000269" --limit 50 --output proc_annotations.json2. Find all genes in a pathway
To find all genes annotated to a specific GO term (e.g., GO:0003700 for "transcription factor activity"):
# Find human genes with this specific molecular function
uv run scripts/quickgo_tool.py annotation search --goId "GO:0003700" --taxonId 9606 --limit 50 --output tf_genes.json3. Explore the GO Hierarchy
To check if a specific GO term is a descendant of a broader category, or to fetch its definition:
# Fetch term details (definitions, synonyms)
uv run scripts/quickgo_tool.py go terms --ids "GO:0003150" --output term_details.json
# Check ancestry (e.g., is GO:0001917 a child of something?)
uv run scripts/quickgo_tool.py go terms --ids "GO:0001917" --relation ancestors --output term_ancestors.json4. Create a GO Slim Summary
If you have a list of candidate genes and want a high-level functional summary, you can map them up to a predefined GO Slim. First, fetch the annotations for the genes to extract their GO IDs, then pass those IDs to the slim endpoint:
# Step 1: Find GO IDs for candidate genes (e.g., via their UniProt IDs, fetching their annotations)
# ... (output yields e.g., GO:0006915,GO:0008219)
# Step 2: Create a slim summary from those specific GO IDs
uv run scripts/quickgo_tool.py go slim --slimsToIds "GO:0005575,GO:0008150,GO:0003674" --slimsFromIds "GO:0006915,GO:0008219" --output my_slim.jsonDoes 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.

