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.4k5mo agoReviewMountCreate a free account to mount
Query the Reactome database (Analysis and Content Services). Use when the user asks about pathway analysis, gene list enrichment, retrieving results by token, finding unmapped or not-found identifiers, mapping identifiers, reaction participants (inputs, outputs), pathway hierarchy (including top-level pathways), diagram export, cross-reference mapping, or searching the knowledgebase.
10 projects use a version of this
3.4k5mo agoReviewMountCreate a free account to mount
Query the STRING database for protein-protein interactions (PPIs), functional enrichment, and homology. Use when the user asks about interactions between specific proteins, interaction evidence, confidence scores, protein interaction partners, or pathway enrichments.
Fetch Evolutionary Conservation scores (phyloP, phastCons) and Transcription Factor Binding Sites (TFBS) from the UCSC Genome Browser. Use when analyzing whether genomic variants or regions are evolutionarily conserved, functionally important, or bounded by TF regulators across major projects (ENCODE, JASPAR, ReMap).
3.4k5mo agoReviewMountCreate a free account to mount
Queries the UniBind database for experimentally validated transcription factor (TF) binding sites. Use when retrieving direct TF-DNA interaction datasets, downloading binding site coordinates (BED/FASTA) for local analysis, or listing available datasets by species, cell line, or TF name. Don't use to query specific intervals, locations, genes, motif models or expression data.
3.4k5mo agoReviewMountCreate a free account to mount
Access protein metadata, function, taxonomy, and sequences across UniProtKB, UniParc, and UniRef. Use when searching for proteins, mapping identifiers, or retrieving functional annotations and publications. Don't use for sequence alignment, protein folding, or sequence similarity search (use specialized skills for those tasks).
Checks whether the uv Python package manager is installed and installs it if missing. Ensures uv is on PATH. Use when another skill requires uv as a prerequisite.
3.4k5mo agoReviewMountCreate a free account to mount
Distills a completed user workflow or interaction into a reusable agent skill. Use when the user asks to turn their workflow, interaction, or multi-step process into a skill, or when they say "make this a skill", "create a skill from what we just did", "package this workflow" or similar. Do not use for creating skills from scratch without an existing workflow (use a generic skill-creator for that).
3.4k5mo agoReviewMountCreate a free account to mount
- Always use uv run, not bare python. Pass explicit --extra flags (e.g. --extra rl, --extra so101, --extra yam) to uv run rather than --no-sync; pyproject.toml (Python 3.12–3.13) configures PyPI as the default index, CMAKE_CXX_STANDARD=17 for reaf, and cross-platform override-dependencies (evdev on Linux only, ruckig>=0.15.3). - Always use absl (from absl import app, flags, logging) for scripts, tools, and entrypoints. NEVER use argparse. - Dependencies are managed with uv. Default make sync installs --extra rl --group dev with CUDA 13…
Steady2 mentions in 2 weeks
No other project uses it yet
2.3k9d agoReviewMountCreate a free account to mount
See README.md for development setup. @CONTRIBUTING.md - PR body should be plain, concise prose. Describe the problem, what the change does, and any non-obvious tradeoffs. Bullet points listing changes are fine, but avoid section headers, structured templates, and emojis. A good PR description reads like a short paragraph to a colleague, not a form. - PR and commit messages are rendered on GitHub, so don't hard-wrap them at 88 columns. Let each sentence flow on one line.
No other project uses it yet
1.6k37d agoReviewMountCreate a free account to mount
Formal Conjectures states open mathematical problems in Lean 4. It is a statement repository, not a proof repository: almost every problem is sorry. CONTRIBUTING.md is the reference for conventions, folders, and attributes. Also follow any README.md in the directory that you change. Use these detailed guides when the task needs them: Follow the style of an existing file. Start by copying one from the same directory. Search Mathlib, FormalConjecturesForMathlib/, and nearby problem files before you add a definition, API, or…
Steady3 mentions in 2 weeks
No other project uses it yet
1.4k31d agoReviewMountCreate a free account to mount
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.