Alphafold Database Fetch And Analyze
google-deepmind/science-skills
Retrieve and analyze AlphaFold predicted structures for a protein.
Detects putative ligand-binding pockets and druggable cavities de novo on an apo protein structure with fpocket, P2Rank, CASTp, and DoGSiteScorer, ranking them by druggability/ligandability score.
$ npx skills add GPTomics/bioSkills --skill bio-structural-biology-binding-site-detection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install GPTomics/bioSkills bio-structural-biology-binding-site-detection --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/GPTomics/bioSkills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/structural-biology/binding-site-detection .claude/skills/bio-structural-biology-binding-site-detection && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "bio-structural-biology-binding-site-detection" agent skill from https://github.com/GPTomics/bioSkills/tree/main/structural-biology/binding-site-detection into .claude/skills/bio-structural-biology-binding-site-detection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bio-structural-biology-binding-site-detection", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/GPTomics/bioSkills/tree/main/structural-biology/binding-site-detectionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add GPTomics/bioSkills --skill bio-structural-biology-binding-site-detection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install GPTomics/bioSkills bio-structural-biology-binding-site-detection --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GPTomics/bioSkills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/structural-biology/binding-site-detection .agents/skills/bio-structural-biology-binding-site-detection && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "bio-structural-biology-binding-site-detection" agent skill from https://github.com/GPTomics/bioSkills/tree/main/structural-biology/binding-site-detection into .agents/skills/bio-structural-biology-binding-site-detection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bio-structural-biology-binding-site-detection", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add GPTomics/bioSkills --skill bio-structural-biology-binding-site-detection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install GPTomics/bioSkills bio-structural-biology-binding-site-detection --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GPTomics/bioSkills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/structural-biology/binding-site-detection .cursor/skills/bio-structural-biology-binding-site-detection && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "bio-structural-biology-binding-site-detection" agent skill from https://github.com/GPTomics/bioSkills/tree/main/structural-biology/binding-site-detection into .cursor/skills/bio-structural-biology-binding-site-detection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bio-structural-biology-binding-site-detection", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/GPTomics/bioSkills.git --path structural-biology/binding-site-detection--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add GPTomics/bioSkills --skill bio-structural-biology-binding-site-detection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install GPTomics/bioSkills bio-structural-biology-binding-site-detection --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GPTomics/bioSkills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/structural-biology/binding-site-detection .gemini/skills/bio-structural-biology-binding-site-detection && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "bio-structural-biology-binding-site-detection" agent skill from https://github.com/GPTomics/bioSkills/tree/main/structural-biology/binding-site-detection into .gemini/skills/bio-structural-biology-binding-site-detection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bio-structural-biology-binding-site-detection", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install GPTomics/bioSkills bio-structural-biology-binding-site-detectionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add GPTomics/bioSkills --skill bio-structural-biology-binding-site-detection -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/GPTomics/bioSkills.git skills-src && mkdir -p .github/skills && cp -r skills-src/structural-biology/binding-site-detection .github/skills/bio-structural-biology-binding-site-detection && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "bio-structural-biology-binding-site-detection" agent skill from https://github.com/GPTomics/bioSkills/tree/main/structural-biology/binding-site-detection into .github/skills/bio-structural-biology-binding-site-detection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bio-structural-biology-binding-site-detection", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add GPTomics/bioSkills --skill bio-structural-biology-binding-site-detection -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install GPTomics/bioSkills bio-structural-biology-binding-site-detection --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GPTomics/bioSkills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/structural-biology/binding-site-detection .opencode/skills/bio-structural-biology-binding-site-detection && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "bio-structural-biology-binding-site-detection" agent skill from https://github.com/GPTomics/bioSkills/tree/main/structural-biology/binding-site-detection into .opencode/skills/bio-structural-biology-binding-site-detection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bio-structural-biology-binding-site-detection", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
bio-structural-biology-binding-site-detectionDetects putative ligand-binding pockets and druggable cavities de novo on an apo protein structure with fpocket, P2Rank, CASTp, and DoGSiteScorer, ranking them by druggability/ligandability score.
Bio Structural Biology Binding Site Detection is an agent skill from GPTomics/bioSkills. Detects putative ligand-binding pockets and druggable cavities de novo on an apo protein structure with fpocket, P2Rank, CASTp, and DoGSiteScorer, ranking them by druggability/ligandability score. Use when detecting cavities on an apo structure with no bound ligand; choosing geometric pocket enumeration (fpocket alpha-spheres, CASTp) vs ML ligandability scoring (P2Rank, DoGSiteScorer); recognizing that a geometric cavity is a hypothesis, not automatically a functional or druggable site (may be a crystal-additive…
Its SKILL.md is about 4.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `examples/detect_pockets.py` and `usage-guide.md`).
It sits in Research & Science, covering Protein structure and design. The repository describes itself as: a set of SKILLS.md for doing bioinformatics with agents like claude code. The licence is MIT.
Read from SKILL.md and the folder at commit d91ed3d. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships script files (Python), which the agent can run.
Shell commands in SKILL.md call:
pipFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
sts.bioe.uic.eduproteins.plusFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Bio Structural Biology Binding Site Detection loads about 4.8k tokens when it runs. Until then it costs about 258 tokens; SKILL.md has 2,150 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from GPTomics/bioSkills at commit d91ed3d, republished under its MIT licence (© GPTomics). 2,150 words, ~4,805 tokens.
.claude/skills/bio-structural-biology-binding-site-detection/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.Reference examples tested with: fpocket 4.1+, P2Rank 2.4+, biopython 1.83+, numpy 1.26+
Before using code patterns, verify installed versions match. If versions differ:
pip show <package> then help(module.function) to check signatures<tool> --version then <tool> --help to confirm flagsIf code throws ImportError, AttributeError, or TypeError, introspect the installed package and adapt the example to match the actual API rather than retrying.
"Find the pockets / druggable cavities on my apo structure" -> Enumerate surface concavities de novo and rank them by a ligandability or druggability score.
fpocket -f protein.pdb (alpha-sphere / Voronoi) or prank predict -f protein.pdb (ML ligandability)"Where could a ligand bind, and how druggable is each site?" -> Detect candidate pockets, then score each for the likelihood of binding a drug-like molecule.
"Detect a cryptic pocket that is not open in this single snapshot" -> Track pocket opening across a conformational ensemble, not one static file.
mdpocket --trajectory_file traj.xtc --trajectory_format xtc -f topology.pdb over an MD trajectory or NMR ensembleA geometric cavity is NOT automatically a functional or druggable site. Pure geometry - fpocket alpha-spheres (Le Guilloux 2009 BMC Bioinformatics 10:168), CASTp surface topology (Tian 2018 Nucleic Acids Res 46:W363) - finds ALL concavities on the surface, including crystallization-additive sites (a sulfate, glycerol, or PEG cleft), non-functional surface pockets, and inter-domain crevices. A ranked pocket list is therefore a HYPOTHESIS, not a binding site. The single most reliable site is one that is already occupied: if the structure is holo (a ligand is bound), map the residues around that ligand directly - that is interface-analysis, not de-novo detection.
Druggability and ligandability SCORES (the fpocket druggability score, P2Rank probability, DoGSiteScorer SVM) rank pockets, but the ranking is not function and not a guarantee. These models were trained largely on holo, druggable reference sets (Schmidtke 2010 J Med Chem 53:5858; Volkamer 2012 J Chem Inf Model 52:360), so they systematically UNDER-detect and under-score apo, shallow, allosteric, and protein-protein-interface pockets, and they cannot see a CRYPTIC pocket at all - a cryptic site forms a pocket in the holo structure but is closed in the apo structure (Cimermancic 2016 J Mol Biol 428:709), so it only appears across an MD or conformational ensemble, never in one static apo snapshot.
Detecting on a PREDICTED model (AlphaFold, ESMFold) inherits that model's pocket-conformation unreliability. The model is usually an apo-like ground state that carries no ligand, cofactor, or metal that would shape the real site, and the side-chain rotamers lining a pocket are the LEAST reliable atoms even when the backbone pLDDT is high (see alphafold-predictions) - so a "confident" backbone can present a confidently wrong pocket. Validate and prepare the model first (structure-validation, structure-preparation). Whatever the input, state the method used and remember: ranking is not function, and the top pocket is a starting hypothesis to corroborate. The orthogonal corroboration signals are an independent detector, evolutionary conservation of the lining residues (a functional site is usually conserved, an additive/crystal cleft usually is not), hot-spot or mixed-solvent mapping (FTMap, mixed-solvent MD), a homolog holo structure, and known biology - not the geometric rank alone.
| Question / situation | Method | Best when | Fails / misleads when |
|---|---|---|---|
| Enumerate every geometric concavity, fast | fpocket (alpha-sphere/Voronoi) or CASTp (surface topology) | Apo or holo, whole-surface scan, ranked candidate list | Reports additive sites, crystal clefts, and non-functional pockets as pockets; ranking != function |
| Rank pockets by ligandability / druggability | P2Rank (ML probability), fpocket druggability score, DoGSiteScorer (SVM) | Prioritizing among many cavities on a folded globular domain | Trained on holo/druggable sets -> under-scores apo, shallow, allosteric, and PPI sites |
| Detect a cryptic or transient pocket | mdpocket over an MD trajectory or conformational ensemble | Site opens only on binding / not present in a single apo snapshot | A single static structure - a cryptic site is invisible without conformational sampling |
| A ligand is already bound (holo structure) | interface-analysis (residues around the bound ligand) | The real binding site is known - map it, do not re-detect | Running de-novo detection when the answer is already in the file |
| Surface area / volume of a defined pocket | CASTp (analytic surface + volume) or fpocket descriptors | Quantifying a known pocket's size | Treating a large computed cavity as evidence of function |
The one-line rule: geometry enumerates concavities, scores rank them, an ensemble reveals cryptic ones, and a bound ligand settles it. Reach for the cheapest method that answers the actual question.
| Structure state | What a detected pocket reveals | What it cannot reveal |
|---|---|---|
| Holo (ligand bound) | The real, occupied site - highest reliability; map it directly | Whether other detected pockets are functional (still hypotheses) |
| Apo experimental | Open, ligand-accessible pockets present in THIS conformation | Cryptic sites closed in this snapshot; induced-fit geometry |
| Predicted model (AlphaFold/ESMFold) | Candidate fold and gross concavities | Reliable pocket rotamers (least reliable atoms), cofactor/metal-shaped sites; validate first |
| MD / NMR ensemble | Transient and cryptic pockets, pocket dynamics/persistence | Which opening is biologically relevant (do not over-read rare openings) |
Apo detection answers "what could open here in this state", holo answers "what is actually bound", a predicted model answers "what might a pocket look like in the ground state", and an ensemble answers "what transiently opens". Match the claim to the state.
Goal: Enumerate candidate pockets on an apo structure and rank them by druggability, keeping the result explicitly a hypothesis list.
Approach: Run fpocket, which writes a <stem>_out/ directory beside the input containing a <stem>_info.txt descriptor file and per-pocket pockets/pocketN_atm.pdb files. Parse the info file into per-pocket descriptors and sort by the druggability score. The 0.5 druggability cutoff is a rule-of-thumb triage line, not a law (Schmidtke 2010): above it a drug-like molecule is plausible, below it the pocket is likely undruggable by conventional small molecules, but apo and cryptic sites routinely fall below it while still being real.
import subprocess
from pathlib import Path
def run_fpocket(pdb_path):
subprocess.run(['fpocket', '-f', pdb_path], check=True)
stem = Path(pdb_path).stem
return Path(pdb_path).with_name(f'{stem}_out') # fpocket writes <stem>_out/ beside the input
def parse_fpocket_info(out_dir):
info = next(Path(out_dir).glob('*_info.txt'))
pockets, current = [], None
for raw in info.read_text().splitlines():
line = raw.strip()
if line.startswith('Pocket'):
current = {'pocket': int(line.split()[1])}
pockets.append(current)
elif ':' in line and current is not None:
key, val = (part.strip() for part in line.split(':', 1))
current[key] = float(val)
return pockets
out_dir = run_fpocket('protein.pdb')
pockets = sorted(parse_fpocket_info(out_dir),
key=lambda p: p['Druggability Score'], reverse=True)
druggable = [p for p in pockets if p['Druggability Score'] >= 0.5] # 0.5 = triage, not a law
for p in pockets[:5]:
print(f"pocket {p['pocket']}: drug={p['Druggability Score']:.2f} score={p['Score']:.2f}")The pocket Score ranks how likely the cavity binds a small molecule; the Druggability Score (0-1) estimates likelihood of binding a DRUG-LIKE molecule specifically. A high-scoring pocket that coincides with a bound additive in the deposited file is a crystallization site, not a target - cross-check the pocket atoms against any HETATM in the input (structure-navigation).
Goal: Get a template-free, machine-learned ligandability ranking that does not depend on alpha-sphere geometry alone.
Approach: Run P2Rank, which scores points on the solvent-accessible surface and clusters them into ranked pockets, writing <inputname>_predictions.csv. Parse the calibrated probability per pocket. P2Rank is ML-based and template-free (Krivak 2018 J Cheminform 10:39), so it complements fpocket's pure geometry - agreement between the two on the same top pocket raises confidence; disagreement flags a site to scrutinize.
import csv
import subprocess
from pathlib import Path
def run_p2rank(pdb_path, out_dir='p2rank_out'):
subprocess.run(['prank', 'predict', '-f', pdb_path, '-o', out_dir], check=True)
return Path(out_dir) / f'{Path(pdb_path).name}_predictions.csv' # keeps the input extension
def parse_p2rank(csv_path):
with open(csv_path) as fh:
reader = csv.DictReader(fh, skipinitialspace=True) # P2Rank pads columns with spaces
rows = [{k.strip(): v.strip() for k, v in row.items()} for row in reader]
return [{'rank': int(r['rank']), 'score': float(r['score']),
'probability': float(r['probability'])} for r in rows]
predictions = parse_p2rank(run_p2rank('protein.pdb'))
top = predictions[0] # rows are already ordered by rank
print(f"top pocket: probability={top['probability']:.2f} score={top['score']:.2f}")P2Rank ranks pockets even when every probability is modest; a low top probability on an apo or PPI target is expected, not a failure to find a site.
CASTp 3.0 (Tian 2018 Nucleic Acids Res 46:W363, http://sts.bioe.uic.edu/castp/) is a web server that delineates pockets, interior cavities, and channels analytically and reports each one's molecular surface AREA and VOLUME - use it when the question is pocket geometry (size, mouth, buried volume) rather than a druggability call. DoGSiteScorer, on the ProteinsPlus server (Volkamer 2012 J Chem Inf Model 52:360, https://proteins.plus/), predicts pockets by a difference-of-Gaussians grid and returns an SVM druggability score trained on a druggable/undruggable set - a second, independent druggability opinion to compare against fpocket. Both are servers with no Python binding; submit a structure and parse the returned table. Treat a server druggability number the same way as fpocket's: trained on holo/druggable data, so it under-scores apo and cryptic sites.
Goal: Find a site that is closed in the single apo structure but opens on binding.
Approach: A cryptic pocket does not exist in one static snapshot, so run pocket detection over a conformational ENSEMBLE - an MD trajectory, an NMR ensemble, or frames from enhanced sampling that is designed to open cryptic sites (mixed-solvent MD / SWISH, accelerated MD) - and track pocket persistence and opening frequency. Generating that ensemble is the real upstream step; mdpocket (Schmidtke 2011 Bioinformatics 27:3276) then analyzes it, building a pocket-frequency grid across frames, and the -S flag adds a per-snapshot drug score so a druggable pocket that only appears transiently is visible.
import subprocess
def run_mdpocket(topology_pdb, trajectory, fmt='xtc'):
# -S adds the per-snapshot drug score so a transiently druggable pocket is flagged
subprocess.run(['mdpocket', '--trajectory_file', trajectory,
'--trajectory_format', fmt, '-f', topology_pdb, '-S'], check=True)Do not over-read a pocket that opens in a handful of frames - a rare, short-lived opening is a weaker hypothesis than a persistent one, and enhanced sampling can manufacture openings that are not physiologically populated. Once a cryptic site is chosen, the bound-state geometry (not the closed apo structure) is what a docking run needs.
A detected, ranked pocket is the INPUT to structure-based drug discovery, not the endpoint. Hand the chosen pocket (its center and lining residues) to chemoinformatics/virtual-screening to dock a library into it, and to chemoinformatics/ml-docking-rescoring to rescore poses - both of those presuppose a known site, which is exactly what this skill produces. Carry the caveat forward: docking into an apo or predicted pocket with unreliable rotamers gives confidently wrong poses unless the pocket is prepared and, ideally, cross-checked against a holo conformation.
| Symptom | Cause | Fix |
|---|---|---|
| Top-ranked pocket is a surface additive site | Geometry finds all concavities, including where a sulfate/glycerol/PEG sat | Cross-check pocket atoms against HETATM/additives in the input; strip additives first (structure-modification) |
| A known binding site is missed entirely | Site is cryptic - closed in the single apo snapshot | Run mdpocket over an MD/NMR ensemble, not one static structure |
| Druggability scores all low on a real target | Score trained on holo/druggable sets under-scores apo, shallow, allosteric, PPI sites | Low score is not "no site"; corroborate with an independent method (P2Rank/DoGSiteScorer), evolutionary conservation of the lining residues (ConSurf), hot-spot / mixed-solvent mapping (FTMap), homolog holo structures, and known biology |
fpocket finds no _info.txt | Parsed the wrong directory or fpocket failed silently | fpocket writes <stem>_out/ beside the input; check the run completed and the stem matches |
| P2Rank parse gives KeyError on column | The CSV has a space after each comma so header keys carry a leading space ( probability) | Use csv.DictReader(skipinitialspace=True) and strip keys before indexing |
| Pockets differ between apo and holo of the same protein | Induced fit - the pocket reshapes on binding | Expected; detect on the state that matches the question, do not average them |
| "Confident" AlphaFold pocket docks poorly | Pocket-lining rotamers are the least reliable atoms; model is apo-like | Validate/prepare the model (structure-validation); prefer a holo experimental structure |
| Same pocket, different rank from two tools | fpocket geometry vs P2Rank ML weight features differently | Agreement raises confidence; treat disagreement as a flag to inspect, not a tie-break |
| Reported "N druggable pockets" as a finding | Ranking treated as function | State it as a ranked hypothesis list; a score is not a validated site |
| mdpocket pocket appears in few frames trusted as real | Over-reading a rare, short-lived opening | Weight by opening frequency/persistence; rare openings are weak hypotheses |
| Detection on the asymmetric unit misses an interface pocket | Functional pocket sits across a symmetry-generated interface | Detect on the biological assembly (structure-io) when the site may be inter-chain |
© GPTomics, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files in structural-biology/binding-site-detection of GPTomics/bioSkills.
Open the folder on GitHubat commit d91ed3d
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in GPTomics/bioSkills, which our catalogue first saw on October 7, 2026.
Bio Structural Biology Binding Site Detection next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Bio Structural Biology Binding Site Detection this skillGPTomics/bioSkills | 1.2k | 1 repos | ~4.8k | Automated safety check: Pass | MIT | |
| Alphafold Database Fetch And Analyzegoogle-deepmind/science-skills | 3.2k | 2 repos | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Alphafoldadaptyvbio/protein-design-skills | 164 | 3 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Pymol VisualizationChatMol/ChatMol | 373 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Complexa Binder DesignNVIDIA-BioNeMo/bionemo-agent-toolkit | 479 | — | ~3.1k | Automated safety check: Notes | Apache-2.0 | |
| Bindcraftadaptyvbio/protein-design-skills | 164 | 3 repos | ~1.3k | Automated safety check: Pass | MIT |
google-deepmind/science-skills
Retrieve and analyze AlphaFold predicted structures for a protein.
adaptyvbio/protein-design-skills
Validate protein designs using AlphaFold2 structure prediction.
ChatMol/ChatMol
Generate publication-quality molecular visualization images using PyMOL.
NVIDIA-BioNeMo/bionemo-agent-toolkit
Run a complete protein binder design campaign with NVIDIA Proteina-Complexa: resolve a target structure and hotspots from a name/sequence/PDB, co-design binder sequence+structure with reward-guided…
adaptyvbio/protein-design-skills
End-to-end binder design using BindCraft hallucination. An agent skill from adaptyvbio/protein-design-skills.
K-Dense-AI/scientific-agent-skills
Predicts how small molecules bind to a protein with DiffDock, covering batch docking, pose ranking by confidence and checks on the results; not for binding affinity.
GPTomics/bioSkills
Read, write, and convert multiple sequence alignment files using Biopython Bio.AlignIO.
GPTomics/bioSkills
Installs the bioSkills collection of 425 bioinformatics skills in one step, or only chosen categories, so sequencing, RNA-seq, single-cell and variant tasks get specialized help.
GPTomics/bioSkills
Write biological sequences to files (FASTA, FASTQ, GenBank, EMBL) using Biopython Bio.SeqIO.
GPTomics/bioSkills
Soft- or hard-clips PCR primer footprints from aligned amplicon BAMs so primer bases stop masquerading as confirmed reference sequence.
GPTomics/bioSkills
Filters BAM alignments by FLAG bits, mapping quality and regions with samtools view or pysam, with recipes for common keep and drop cases.
GPTomics/bioSkills
Create and use BAI/CSI indices for BAM/CRAM files using samtools and pysam.
Categories
Detects putative ligand-binding pockets and druggable cavities de novo on an apo protein structure with fpocket, P2Rank, CASTp, and DoGSiteScorer, ranking them by druggability/ligandability score. Bio Structural Biology Binding Site Detection is an agent skill from GPTomics/bioSkills. Detects putative ligand-binding pockets and druggable cavities de novo on an apo protein structure with fpocket, P2Rank, CASTp, and DoGSiteScorer, ranking them by druggability/ligandability score.
Bio Structural Biology Binding Site Detection fits situations like: detecting cavities on an apo structure with no bound ligand; choosing geometric pocket enumeration (fpocket alpha-spheres; CASTp) vs ML ligandability scoring (P2Rank; recognizing that a geometric cavity is a hypothesis.
Run `npx skills add GPTomics/bioSkills --skill bio-structural-biology-binding-site-detection -a claude-code`. Or copy the skill folder (structural-biology/binding-site-detection in GPTomics/bioSkills) into .claude/skills/bio-structural-biology-binding-site-detection in your project. Claude Code loads it when a task matches its description.
Run `npx skills add GPTomics/bioSkills --skill bio-structural-biology-binding-site-detection -a codex`. Or copy the skill folder (structural-biology/binding-site-detection in GPTomics/bioSkills) into .agents/skills/bio-structural-biology-binding-site-detection in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add GPTomics/bioSkills --skill bio-structural-biology-binding-site-detection -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bio-structural-biology-binding-site-detection, .gemini/skills/bio-structural-biology-binding-site-detection, .github/skills/bio-structural-biology-binding-site-detection and .opencode/skills/bio-structural-biology-binding-site-detection in your project.
Going by SKILL.md and its folder, Bio Structural Biology Binding Site Detection needs Python for the scripts in its folder and the command-line tools its instructions call (pip). Our summary lists: Python 3.
SKILL.md names 2 domains. As links in the text: sts.bioe.uic.edu and proteins.plus. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Bio Structural Biology Binding Site Detection is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.8k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Bio Structural Biology Binding Site Detection: Alphafold Database Fetch And Analyze (google-deepmind/science-skills, 3.2k stars), Alphafold (adaptyvbio/protein-design-skills, 164 stars), Pymol Visualization (ChatMol/ChatMol, 373 stars) and Complexa Binder Design (NVIDIA-BioNeMo/bionemo-agent-toolkit, 479 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
GPTomics (a GitHub organization) maintains it in GPTomics/bioSkills, which has 1,218 GitHub stars. The repository holds 559 skills in this directory. The repository was last updated on August 15, 2026.
Source: GPTomics/bioSkills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.