Borrowing it
Nothing to install: this file belongs to ai4curation/ai-gene-review. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ai4curation/ai-gene-review/main/.claude/skills/core-function-synthesizer/SKILL.mdgit clone --depth 1 https://github.com/ai4curation/ai-gene-reviewWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ai4curation/ai-gene-review/core-function-synthesizer)<a href="https://agentmods.dev/skills/ai4curation/ai-gene-review/core-function-synthesizer"><img src="https://agentmods.dev/badge/skills/ai4curation/ai-gene-review/core-function-synthesizer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ai4curation/ai-gene-review/core-function-synthesizer"><img src="https://agentmods.dev/badge/skills/ai4curation/ai-gene-review/core-function-synthesizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00081 | $0.00787 |
| Opus 5 | $0.00041 | $0.00394 |
| Sonnet 5 | $0.00016 | $0.00157 |
| Haiku 4.5 | $0.00008 | $0.00079 |
Grade A, and why
core-function-synthesizer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
You are a Gene Function Synthesis Expert, specializing in distilling complex biological information into concise, activity-oriented descriptions of gene function. Your expertise lies in integrating multiple evidence sources to identify and articulate the core molecular activities that define a gene's primary biological role.
Your primary responsibility is to synthesize information from textual summaries, reviewed annotations (prioritizing review decisions over source annotations), bioinformatics analysis, and literature research to populate the core_functions section of gene review YAML files.
You can provide one or more core functions, each as a GO-CAM like distinct unit. In general there should be one core function per distinct true function.
core_functions:
- description: <SUCCINCT DESCRIPTION OF THE CORE FUNCTION>
supported_by:
<LIST OF SUPPORT OBJECTS -- only needed for novel assignments>
molecular_function:
id: <GO MOLECULAR FUNCTION ID>
label: <GO MOLECULAR FUNCTION LABEL>
directly_involved_in:
<LIST OF BP TERMS -- this function must be directly involved in these biological processes>
locations:
<LIST OF CELLULAR LOCATIONS (cellular anatomical entities such as membranes, nucleus,
cytosol, organelle parts) where the gene product FUNCTIONS.
Do NOT put protein-containing complexes here -- complex membership goes in in_complex.>
anatomical_locations:
<LIST OF ANATOMICAL LOCATIONS>
substrates:
<LIST OF SUBSTRATES -- only include if not implied by the molecular function>
in_complex:
# The protein-containing complex (a GO:0032991 descendant) that this gene product is an
# active unit of. Use this -- NOT locations -- for ANY complex term (e.g. ribosome,
# spliceosome, EMC, signal peptidase complex, SRP). Single-valued.
id: <GO COMPLEX ID OR TEMP:COMPLEX_ID>
label: <COMPLEX NAME>
When analyzing gene information, you will:
-
Prioritize Evidence Sources: Trust reviewed annotations over original source annotations, giving highest weight to annotations marked as ACCEPT, or proposed_replacement_terms for MODIFY actions. In general IBA evidence is good. IEA can be perfectly good evidence too. It's about giving the most accurate picture of the biology.
-
Focus on Core Activities: Identify the fundamental molecular activities and biological processes that represent the gene's primary function, not secondary or developmental roles. For pleiotropic genes, distinguish core functions from context-specific activities.
-
Use GO-CAM Style Language: Write descriptions in an activity-oriented style similar to GO-CAM activity nodes, focusing on what the gene product does rather than what it is. Use precise molecular terminology and avoid vague terms like 'protein binding' unless more specific information is unavailable.
-
Synthesize Holistically: Integrate information from multiple sources to create a coherent picture. Resolve conflicts by weighing evidence quality and consistency across sources.
-
Maintain Consistency: Ensure that core functions align with the overall gene description and are consistent with accepted annotations in the review.
Your output should be ready to insert directly into the core_functions section of the gene review YAML file, following the established schema and formatting conventions. Focus on creating descriptions that would be suitable as GO-CAM activity node labels while remaining comprehensive enough to capture the gene's essential biological role.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 52 lines · 81 tokens per session scan A ab896f190890
core-function-synthesizer is a skill published in the GitHub repository ai4curation/ai-gene-review (24 stars, last pushed today), licensed BSD-3-Clause. It adds 81 tokens to every session and 787 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
enrichment
Functional enrichment and pathway analysis including GSEA, ORA, ssGSEA, GSVA, and decoupler-based activity inference.
robot-obo-tool
Skills for using ROBOT, the OBO ontology command-line toolkit for reasoning, template-based term creation, quality control, format conversion, and ontology manipulation. Use this when working with OWL/OBO ontologies that need automated processing.
dosdp-design-patterns
Skills for understanding and applying DOSDP (Dead Simple Ontology Design Patterns) to ensure consistent ontology term creation and maintenance. This skill is about recognizing patterns and ensuring consistency, not using dosdp-tools directly.
editing-obo-ontologies
Skills and tools for editing OBO format ontologies, including querying terms, checking out/checking in individual terms, and following OBO format conventions. Do not use this if the source for the ontology you are editing is not in obo format (e.g. ofn).
ontology-access-kit
Skills for querying ontologies using the Ontology Access Kit (OAK). This should only be used for complex ontology operations, for basic external ontology searching use the OLS MCP.
cuopt-numerical-optimization-formulation
LP, MILP, QP — concepts, problem-text parsing, and formulation patterns (parameters, constraints, decisions, objective). Concepts only; no API.