GITHUB AGENT SKILLS / 技能收录
给你的 AI 助手
装上专业技能
我们从 GitHub 持续收录、审核并分类优质的 Agent Skills，按职业与使用场景整理，复制一行命令即可安装到 Claude Code、Cursor 等智能体。
按职业浏览 Agent Skills
为不同岗位挑选的高频技能
按使用场景浏览 Agent Skills
从你要完成的任务出发
按创作者浏览 Agent Skills
按 GitHub Stars 排序的优秀创作者
Microsoft
@microsoft
openclaw
@openclaw
OpenAI
@openai
The Apache Software Foundation
@apache
GitHub
@github
Anthropic
@anthropics
AutoGPT
@Significant-Gravitas
Garry Tan
@garrytan全部 Skills 196852
craft-and-care
Use when checking execution-quality standards for this fixture repo.
tooluniverse-sequence-analysis
Retrieve and analyze biological sequences -- gene/protein sequences from NCBI, Ensembl, and UniProt. Search nucleotide databases, fetch by accession, find orthologs, get gene summaries. Use when users ask about DNA/RNA/protein sequences, gene lookups, ortholog searches, or sequence retrieval.
doctrine
Use when grounding work in this fixture project's recorded knowledge — purpose and scope, design contracts, required behavior, topology, or the engineering bar. Routes to one pillar navigator.
spec-and-spine
Use when reading the capability spec pillar in this legacy-layout fixture.
tooluniverse-sdk
Build AI scientist systems using ToolUniverse Python SDK for scientific research. Use when users need to access 1000++ scientific tools through Python code, create scientific workflows, perform drug discovery, protein analysis, genomics analysis, literature research, or any computational biology task. Triggers include requests to use scientific tools programmatically, build research pipelines, analyze biological data, search literature, predict drug properties, or create AI-powered scientific workflows.
legends-and-lore
Use when reading the design contract pillar in this legacy-layout fixture.
lay-and-land
Use when reading the topology pillar in this legacy-layout fixture.
tooluniverse-rnaseq-deseq2
Production-ready RNA-seq differential expression analysis using PyDESeq2. Performs DESeq2 normalization, dispersion estimation, Wald testing, LFC shrinkage, and result filtering. Handles multi-factor designs, multiple contrasts, batch effects, and integrates with gene enrichment (gseapy) and ToolUniverse annotation tools (UniProt, Ensembl, OpenTargets). Supports CSV/TSV/H5AD input formats and any organism. Use when analyzing RNA-seq count matrices, identifying DEGs, performing differential expression with statistical rigor, or answering questions about gene expression changes.
heart-and-soul
Use when reading the doctrine pillar in this legacy-layout fixture.
craft-and-care
Use when checking execution-quality standards for this legacy fixture.
tooluniverse-regulatory-variant-analysis
Regulatory variant interpretation -- GWAS association lookup, eQTL analysis, chromatin state annotation, regulatory element overlap, and trait ontology resolution. Connects GWAS Catalog, GTEx, ENCODE, RegulomeDB, OpenTargets, OLS ontology, and Ensembl regulatory features. Use when users ask about non-coding variants, GWAS hits, eQTLs, regulatory elements, enhancer/promoter variants, or trait-associated SNPs.
tooluniverse-regulatory-genomics
Investigate transcription factor binding, cis-regulatory elements, chromatin accessibility, and regulatory variant annotation. Use when asked about TF binding sites, enhancers, promoters, ChIP-seq data, ATAC-seq signals, candidate cis-regulatory elements (cCREs), or the regulatory impact of genomic variants.
tooluniverse-rare-disease-genomics
Rare disease genomics research -- disease identification via Orphanet, causative gene discovery, gene-disease validity assessment via GenCC, pathogenic variant lookup via ClinVar, HPO phenotype mapping, epidemiology and prevalence data, clinical trial search, and literature review. Use when users ask about rare diseases, orphan diseases, genetic causes of rare conditions, Orphanet codes, HPO phenotypes, gene-disease validity, rare disease prevalence, or treatment options for rare genetic disorders.
project-shape
Use when analyzing or bootstrapping the five-pillar knowledge architecture of a software project: about/heart-and-soul (doctrine), about/legends-and-lore (RFCs/design contracts), about/lay-and-land (topology), about/craft-and-care (execution-quality standards), and openspec/ (capability specs at root). Use when: starting a new project's knowledge structure, auditing documentation health, onboarding, deciding where knowledge belongs, or mapping system topology. Triggers: "project shape", "bootstrap docs", "where should this go", "what's this project about", "project pillars", "heart and soul", "spec structure", "knowledge architecture", "system map", "topology", "lay of the land", "set up project structure".
tooluniverse-rare-disease-diagnosis
Provide differential diagnosis for patients with suspected rare diseases based on phenotype and genetic data. Matches symptoms to HPO terms, identifies candidate diseases from Orphanet/OMIM, prioritizes genes for testing, interprets variants of uncertain significance. Use when clinician asks about rare disease diagnosis, unexplained phenotypes, or genetic testing interpretation.
project-review
Use when auditing a repository's overall health, tech debt, maintainability, or architecture quality; or processing a third-party repo-wide audit. Triggers include "review this project", "audit the codebase", "assess project health", and "process this third-party review" — not single-PR review, spec↔code reconciliation, or backlog prioritization.
tooluniverse-proteomics-data-retrieval
Find and retrieve proteomics datasets from public repositories including MassIVE and ProteomeXchange (which aggregates PRIDE, PeptideAtlas, jPOST, and iProX). Search by species, keyword, or accession. Get detailed dataset metadata including instruments, publications, species, modifications, and file counts. Use when asked to find proteomics datasets, search for mass spectrometry data, look up ProteomeXchange or MassIVE accessions, or discover publicly available proteomics experiments for a given organism or topic.
project-feature-request
Use when one concrete feature or project request is still fuzzy and needs a signed-off behavior specification before planning or implementation, or when implementation reveals its governing spec is wrong, ambiguous, or incomplete. Triggers: "I want to add X", "spec this feature", "turn this idea into requirements", "what would it take to build X", "write a spec for X", "the spec is wrong", "the spec doesn't match what I'm building".