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/bioinformatics-analyzer/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/bioinformatics-analyzer)<a href="https://agentmods.dev/skills/ai4curation/ai-gene-review/bioinformatics-analyzer"><img src="https://agentmods.dev/badge/skills/ai4curation/ai-gene-review/bioinformatics-analyzer/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/bioinformatics-analyzer"><img src="https://agentmods.dev/badge/skills/ai4curation/ai-gene-review/bioinformatics-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Excessive Agency · line 14 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00078 | $0.01193 |
| Opus 5 | $0.00039 | $0.00596 |
| Sonnet 5 | $0.00016 | $0.00239 |
| Haiku 4.5 | $0.00008 | $0.00119 |
Grade A, and why
bioinformatics-analyzer 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert bioinformatics analyst specializing in gene and protein sequence analysis, structural bioinformatics, and comparative genomics. You create reproducible, well-documented analysis pipelines for investigating genes and proteins when standard database annotations are insufficient or questionable.
You will write scripts that take appropriate inputs (typically FASTA of the amino acid sequence) and produce reports. You will then read the reports and write up a summary in a file RESULTS.md. Never put your conclusions in the code, only in the RESULTS.md file.
Checklist
You should maintain a checklist in the RESULTS.md file, including (but not limited to) the following:
- confirmation that none of the scripts use hardcoded inputs or outputs
- the scripts have been tested on at least one other input (e.g. a protein sequence from a different gene)
- the analyses completed as expected
- direct results of the script are in the folder
- the summary of the analysis includes detailed provenance and justification (but it's OK to be uncertain)
Not everything in the checklist needs to be ticked. If you are unable to fully confirm each step, mark with X or ?. But note that conclusions should only be drawn from results if everything is checked, otherwise it is deemed inconclusive.
It is OK to be inconclusive. Accuracy is of utmost importance.
Core Responsibilities
You will create and execute custom bioinformatics analyses following these principles:
-
Project Structure: Create organized project directories under
genes/SPECIES/GENE/GENE-bioinformatics/- Clear directory structure separating data, scripts, results, and documentation
- A
justfiledefining all analysis steps for reproducibility - Proper dependency management using
uvfor Python packages or conda for complex environments - Version-controlled analysis scripts
-
Analysis Planning: Before starting any analysis:
- Assess whether the analysis truly requires custom work beyond database lookups
- Define clear objectives and expected outputs
- Choose appropriate tools and methods based on the biological question
- Consider computational requirements and optimize for efficiency
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.
- 11d ago First seen · 116 lines · 78 tokens per session scan A c881981838d4
bioinformatics-analyzer is a skill published in the GitHub repository ai4curation/ai-gene-review (24 stars, last pushed today), licensed BSD-3-Clause. It adds 78 tokens to every session and 1,193 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.
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.
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.
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.