tooluniverse-protein-structure-retrieval
Protein structure retrieval from RCSB PDB, PDBe, and AlphaFold with disambiguation, quality assessment (resolution, R-factor, pLDDT), and metadata. Distinguishes high-quality experimental (X-ray under 2 Angstrom) vs predicted vs medium-quality structures. Use for fetching protein structures, structure-quality comparison, and selecting structures for drug design or modeling.
What this skill does
# Protein Structure Data Retrieval Retrieve protein structures with disambiguation, quality assessment, and comprehensive metadata. **IMPORTANT**: Always use English terms in tool calls. Respond in the user's language. **LOOK UP DON'T GUESS**: Never assume PDB IDs, resolution, or availability. Always query RCSB/PDBe and AlphaFold to confirm. ## Domain Reasoning Not all structures are equal. X-ray <2 A is high-quality for drug design. Cryo-EM 3-4 A is good for fold but not side chains. AlphaFold is excellent for well-folded domains but unreliable for disordered regions. Always check pLDDT (AlphaFold) or resolution (experimental) before drawing conclusions. ## Workflow ``` Phase 0: Clarify (if needed) → Phase 1: Disambiguate Protein → Phase 2: Retrieve Structures → Phase 3: Report ``` --- ## Phase 0: Clarification (When Needed) Ask ONLY if: protein name ambiguous (e.g., "kinase"), organism not specified, unclear if experimental vs AlphaFold needed. Skip for: specific PDB IDs, UniProt accessions, unambiguous protein+organism. --- ## Phase 1: Protein Disambiguation ```python # By PDB ID: direct retrieval # By UniProt: get AlphaFold + search experimental structures af_structure = tu.tools.alphafold_get_prediction(uniprot_id=uniprot_id) # By protein name: search result = tu.tools.PDBeSearch_search_structures(protein_name=protein_name) ``` ### Identity Checklist - Protein name/gene identified, organism confirmed - UniProt accession (if available), isoform/variant specified (if relevant) --- ## Phase 2: Data Retrieval (Internal) Retrieve silently. Do NOT narrate the process. ```python pdb_id = "4INS" # Search, metadata, quality, ligands, similar structures result = tu.tools.PDBeSearch_search_structures(protein_name=name) metadata = tu.tools.get_protein_metadata_by_pdb_id(pdb_id=pdb_id) exp = tu.tools.RCSBData_get_entry(pdb_id=pdb_id) quality = tu.tools.PDBeValidation_get_quality_scores(pdb_id=pdb_id) ligands = tu.tools.PDBe_KB_get_ligand_sites(pdb_id=pdb_id) similar = tu.tools.PDBeSIFTS_get_all_structures(pdb_id=pdb_id, cutoff=2.0) # PDBe additional data summary = tu.tools.pdbe_get_entry_summary(pdb_id=pdb_id) molecules = tu.tools.pdbe_get_entry_molecules(pdb_id=pdb_id) # AlphaFold (when no experimental structure, or for comparison) af = tu.tools.alphafold_get_prediction(uniprot_id=uniprot_id) ``` ### Fallback Chains | Primary | Fallback | |---------|----------| | RCSB search | PDBe search | | get_protein_metadata | pdbe_get_entry_summary | | Experimental structure | AlphaFold prediction | | get_protein_ligands | PDBe_KB_get_ligand_sites | --- ## Phase 3: Report Structure Profile Present as a **Structure Profile Report**. Hide search process. Include: 1. **Search Summary**: query, organism, experimental + AlphaFold structure counts 2. **Best Structure**: PDB ID, UniProt, organism, method, resolution, date, quality assessment 3. **Experimental Details**: method, resolution, R-factor, R-free, space group 4. **Composition**: chains, residues (coverage%), ligands, waters, metals 5. **Bound Ligands**: ligand ID, name, type, binding site 6. **Binding Site Details** (for drug discovery): location, key residues, druggability 7. **Alternative Structures**: ranked by quality with resolution, method, ligands 8. **AlphaFold Prediction**: UniProt, model version, pLDDT confidence distribution, use cases 9. **Structure Comparison**: resolution, completeness, ligands across structures 10. **Download Links**: PDB/mmCIF/AlphaFold formats, database URLs --- ## Quality Assessment ### Experimental Structures | Tier | Criteria | |------|----------| | Excellent | X-ray <1.5A, complete, R-free <0.22 | | High | X-ray <2.0A OR Cryo-EM <3.0A | | Good | X-ray 2.0-3.0A OR Cryo-EM 3.0-4.0A | | Moderate | X-ray >3.0A OR NMR ensemble | | Low | >4.0A, incomplete, or problematic | ### Resolution Use Cases <1.5A: atomic detail, H-bond analysis. 1.5-2.0A: drug design. 2.0-2.5A: structure-based design. 2.5-3.5A: overall architecture. >3.5A: domain arrangement only. ### AlphaFold Confidence (pLDDT) >90: very high, experimental-like. 70-90: good backbone. 50-70: uncertain/flexible. <50: likely disordered. --- ## Error Handling | Error | Response | |-------|----------| | "PDB ID not found" | Verify 4-char format, check if obsoleted | | "No structures" | Offer AlphaFold, suggest similar proteins | | "Download failed" | Retry once, provide alternative link | | "Resolution unavailable" | Likely NMR/model, note in assessment | --- ## Tool Reference **RCSB PDB**: `PDBeSearch_search_structures` (search), `get_protein_metadata_by_pdb_id` (basic info), `RCSBData_get_entry` (details), `PDBeValidation_get_quality_scores` (quality), `PDBe_KB_get_ligand_sites` (ligands), `PDBeSIFTS_get_all_structures` (homologs) **PDBe**: `pdbe_get_entry_summary` (overview), `pdbe_get_entry_molecules` (entities), `pdbe_get_entry_experiment` (experimental), `PDBe_KB_get_ligand_sites` (pockets) **AlphaFold**: `alphafold_get_prediction` (get prediction), `alphafold_get_summary` (search)
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.