protein-structure
Skill67 starsChanged 19 days agoMITView on GitHub
Analyzes protein structures from PDB files: parses ATOM/HETATM records with a dependency-free pure-Python parser, computes radius of gyration, gyration tensor and dipole moments, assigns secondary structure via DSSP or a built-in Kabsch-Sander hydrogen-bond implementation, and optionally retrieves UniProt metadata. This skill should be used when secondary structure assignment, Rg, shape analysis, DSSP, PDB parsing or protein structure annotation is requested.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- alphafold-dbSkill
- bio-database-fetchSkill
- bioproject-searchSkill
- bulk-rnaseqSkill
- ena-downloadSkill
- literature-searchSkill
- ml-peptide-generationSkill
- molecular-dynamicsSkill
- paper-fulltext-extractSkill
- peptide-designSkill
- protein-docking-hdockSkill
- protein-docking-lightdockSkill
- protein-interactionsSkill
- pymol-structure-visualizationSkill
- scientific-figuresSkill
- single-cell-rnaseqSkill
The file
Files
Protein Structure Analysis
Overview
This skill turns raw PDB coordinates into quantitative structural descriptors without
requiring heavyweight dependencies. It ships a self-contained PDB parser that handles
ATOM / HETATM records, multi-model files, alternate locations and insertion codes,
plus a built-in secondary-structure assigner based on the Kabsch-Sander hydrogen-bond
energy model. Geometry (radius of gyration, gyration tensor principal axes, shape
descriptors, dipole moment) is computed in pure Python, and UniProt metadata can be
attached on request.
When to Use This Skill
- Secondary structure assignment of a protein (
DSSP,H/E/Ccontent, helix percentage) - Radius of gyration, radius of gyration tensor, shape anisotropy of a folded protein
- Parsing PDB files without installing Biopython
- Batch statistics over a directory of PDB files (length distribution, average Rg)
- Attaching UniProt protein names, organism and function to structural results
- Preliminary characterisation of AlphaFold models or predicted structures
Quick Start
# 单个结构:解析 + 几何 + 二级结构
python scripts/analyze_structure.py --input 1crn.pdb --output results/
# 强制使用内置 DSSP 实现(系统未装 mkdssp 时)
python scripts/analyze_structure.py --input 1crn.pdb --output results/ --dssp-method builtin
# 批量处理整个目录(4 线程)
python scripts/batch_analyze.py --input ./pdb_data --output results/ --workers 4
# 附加 UniProt 元数据(需要网络)
python scripts/analyze_structure.py --input P69905.pdb --output results/ --query-uniprotWorkflow
- Parse —
pdb_parser.pyreads fixed-column PDB records into aStructure → Model → Chain → Residue → Atomtree. Alternate locations keep only the primary conformer (' ','A','1');MODEL/ENDMDLsplits multi-model files. - Summarise — chain/residue/atom counts, element composition, heteroatom inventory, per-chain one-letter sequences.
- Geometry —
geometry.pycomputes mass-weightedRg(andRgover Cα only), the gyration tensor with a Jacobi eigen-decomposition, shape descriptors (asphericity, acylindricity, relative shape anisotropy) and a partial-charge dipole estimate. - Secondary structure —
secondary_structure.pyeither shells out tomkdsspor runs the built-in assigner: rebuild missing amide hydrogens, evaluate Kabsch-Sander hydrogen-bond energies, and classifyH/G/I/E/B/T/S/-. - Annotate — optionally query
rest.uniprot.orgfor protein name, organism, sequence length and function via the sharedhttp_session(retry + rate limit). - Report — write
structure_analysis.jsonandstructure_analysis.csv.
Parameters
| Parameter | Script | Default | Description |
--input | both | required | PDB file or directory of PDB files |
--output | both | results/ | Output directory for reports |
--dssp-method | both | auto | auto / external / builtin secondary-structure backend |
--dssp-executable | both | auto-detected | Path to mkdssp or dssp |
--hbond-energy | both | -0.5 | Hydrogen-bond energy threshold (kcal/mol) for the built-in assigner |
--model | analyze | 1 | Which model to analyse (1-based) |
--query-uniprot | both | off | Enable UniProt metadata lookup (network access) |
--format | analyze | both | json / csv / both |
--workers | batch | 4 | Worker threads for batch processing |
--pattern | batch | *.pdb | Glob pattern for batch discovery |
--recursive | batch | off | Recurse into subdirectories |
--min-residues | batch | 0 | Skip structures shorter than this |
--max-files | both | 0 | Cap the number of files (0 = unlimited) |
Outputs
| File | Content |
structure_analysis.json | Full nested report: structure summary, chains, geometry, per-residue secondary structure, UniProt annotation |
structure_analysis.csv | Flat one-row-per-structure table (Rg, shape class, helix/sheet percentages) |
batch_summary.json | Aggregate statistics over a directory plus per-structure detail |
batch_results.csv | Flat table of the batch run |
Validation
- Hydrogen-bond geometry: in a genuine alpha helix the
O(i)···N(i+4)distance must be ~2.9-3.1 Å. The built-in assigner only reportsHwhen that contact exists. - Backbone sanity:
Cα(i)-Cα(i+1)should be ~3.8 Å andC(i)-N(i+1)~1.33 Å. Distances far from these indicate a malformed or non-standard PDB. - Helix content: globular proteins typically show 20-50% helix. A reported value near 0% or 100% for a folded protein is a red flag for the hydrogen-bond threshold.
- Cross-check: compare
builtinagainstexternalDSSP on the same file (--dssp-method builtinvs--dssp-method external). Agreement within a few percent on helix content is expected; large divergence usually means the structure lacks resolved hydrogens or is highly non-standard. - Rg plausibility: for a 100-residue globular domain
Rgis roughly 11-14 Å (Rg ≈ 2.2 × N^0.38Å is a common empirical rule). - Element counts: hydrogen atoms are usually absent from X-ray structures, so
element_countscontaining only C/N/O is expected, not a parse failure.
References
references/methodology.md— algorithms, formulas and parameter selection rationalereferences/troubleshooting.md— common failures and how to diagnose them
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

