Skip to content
Automation
Skill

/bio-database-evidence

Unified biological database evidence owner. Use for gene annotation, variant clinical significance, cancer mutation evidence, GWAS trait associations, pathway mapping, target-disease evidence, protein structures, protein interaction networks, reference single-cell census

From plugin
vibe-skills
2.7k200 skills8 agents3 commands
Install
$ npx -y skills add foryourhealth111-pixel/Vibe-Skills --skill bio-database-evidence --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/bio-database-evidence

Context preview

The summary Claude sees to decide when to auto-load this skill.

Unified biological database evidence owner. Use for gene annotation, variant clinical significance, cancer mutation evidence, GWAS trait associations, pathway mapping, target-disease evidence, protein structures, protein interaction networks, reference single-cell census

SKILL.md

bio-database-evidence.SKILL.md
name: bio-database-evidence
description: "Unified biological database evidence owner. Use for gene annotation, variant clinical significance, cancer mutation evidence, GWAS trait associations, pathway mapping, target-disease evidence, protein structures, protein interaction networks, reference single-cell census queries, and cross-database biological ID mapping. Do not use for full single-cell analysis, bulk RNA-seq differential expression, BAM/VCF processing, protein embedding models, metabolic flux modeling, genomic interval ML, or flow-cytometry file parsing."

Bio Database Evidence

Use This Skill For

Use this skill when the main task is biological database lookup, annotation, or evidence gathering across one or more biological sources:

  • Gene annotation, identifiers, RefSeq, Ensembl IDs, orthologs, VEP, GO, and genomic coordinates.
  • Variant clinical significance, VUS interpretation support, ClinVar review status, cancer mutations, and COSMIC evidence.
  • GWAS Catalog trait associations, rs IDs, p-values, summary statistics, and genetic epidemiology evidence.
  • Pathway mapping, ID conversion, KEGG pathways, Reactome enrichment, disease pathways, and pathway evidence.
  • Target-disease association evidence, tractability, safety, known drugs, and Open Targets evidence.
  • Protein structure evidence from AlphaFold DB or RCSB PDB, including UniProt IDs, mmCIF/PDB downloads, pLDDT, PAE, and structure metadata.
  • Protein-protein interaction evidence, STRING networks, hub proteins, and enrichment evidence.
  • Reference single-cell data lookup from CELLxGENE Census when the user asks for census metadata or expression data, not full downstream analysis.
  • Cross-database biological ID mapping and evidence tables across multiple resources.

Do Not Use This Skill For

  • Single-cell RNA-seq analysis, clustering, UMAP, marker genes, cell annotation, AnnData/h5ad container editing, or scVI/scANVI batch-correction planning. Use `scanpy`.
  • Bulk RNA-seq differential expression. Use `pydeseq2`.
  • BAM, SAM, CRAM, VCF, pileup, coverage, or region extraction as a primary file-processing task.
  • deepTools signal-track processing and heatmaps.
  • Protein language models, embeddings, inverse folding, or protein-design workflows.
  • Constraint-based metabolic modeling, FBA, or metabolic-engineering simulation.
  • BED/genomic interval embeddings, genomic-region ML, or gene regulatory network inference.
  • FCS or flow-cytometry file parsing.

Workflow

1. Identify the biological entity type: gene, transcript, variant, pathway, target, protein structure, protein interaction, trait association, or reference cell population. 2. Pick the narrowest source that answers the evidence question. 3. Preserve source names, query terms, access dates, identifiers, and API caveats in the result. 4. Return evidence in a table when comparing multiple sources. 5. State when authentication, license, rate limits, or non-public access restricts a source.

Source Guide

See `references/database-evidence-sources.md` for source-specific boundaries and query notes.

Read more
Ships withvibe-skills

VibeSkills is a general-purpose Skill that automatically routes local Skills and intelligently orchestrates harness workflows.

Get the whole plugin

Other skills on vibe-skills.