tooluniverse-electron-microscopy
Search and analyze electron microscopy data — cryo-EM density maps (EMDB), fitted atomic models (PDB), raw micrograph datasets (EMPIAR), and cryo-electron tomography volumes (CryoET Data Portal). Use for finding 3D structural data on a protein/complex, comparing experimental EM resolution to AlphaFold confidence, and accessing raw EM data for re-processing.
What this skill does
# Electron Microscopy Structure Analysis
Pipeline for discovering and analyzing electron microscopy data across the full resolution spectrum: from 3D density maps (EMDB) to fitted atomic models (PDB), raw micrograph datasets (EMPIAR), and cryo-electron tomography volumes (CryoET Data Portal). Connects EM data to structural biology context via PDB and AlphaFold.
**Guiding principles**:
1. **Resolution awareness** -- always report and interpret map resolution; sub-4A enables atomic modeling, 4-8A enables domain fitting, >8A is shape-level
2. **Map before model** -- the density map is the primary experimental data; fitted models are interpretations
3. **Method matters** -- single particle analysis, tomography, 2D crystallography, and helical reconstruction have different strengths and limitations
4. **Raw data value** -- EMPIAR raw data enables reprocessing with newer algorithms; always note availability
5. **Cross-reference structures** -- connect EMDB maps to PDB entries and AlphaFold predictions for completeness
6. **English-first queries** -- use English terms in tool calls
EM resolution determines what you can see. TEM resolves individual protein complexes (~2nm). Cryo-EM achieves near-atomic resolution (<4Å) for large complexes. SEM shows surface topology. Choose the right EM modality for the question.
## LOOK UP, DON'T GUESS
When uncertain about any scientific fact, SEARCH databases first rather than reasoning from memory. A database-verified answer is always more reliable than a guess.
---
## COMPUTE, DON'T DESCRIBE
When analysis requires computation (statistics, data processing, scoring, enrichment), write and run Python code via Bash. Don't describe what you would do — execute it and report actual results. Use ToolUniverse tools to retrieve data, then Python (pandas, scipy, statsmodels, matplotlib) to analyze it.
## When to Use
Typical triggers:
- "Find cryo-EM structures of [protein/complex]"
- "What EMDB maps are available for [target]?"
- "Get raw micrograph data for [structure]"
- "Find tomography datasets for [organelle/cell type]"
- "What is the resolution of [EMDB entry]?"
- "Cross-reference this EM map with PDB models"
- "Find cryo-ET datasets for [sample]"
**Not this skill**: For X-ray crystallography or NMR structures, use PDB search tools directly. For protein structure prediction, use `tooluniverse-protein-structure`.
---
## Core Databases
| Database | Content | Best For |
|----------|---------|----------|
| **EMDB** | 3D EM density maps (>40K entries) | Finding processed maps, resolution data, fitting info |
| **EMPIAR** | Raw micrograph/tilt series datasets | Accessing original image data for reprocessing |
| **CryoET Data Portal** | Cryo-electron tomography data | Tomographic volumes, cellular context, in-situ structures |
| **PDB (RCSB)** | Atomic models fitted to EM maps | Structural models derived from EM data |
| **AlphaFold** | AI-predicted protein structures | Complementary models when EM resolution is limited |
---
## Workflow Overview
```
Phase 0: Query Parsing
Identify target protein/complex, method preference, resolution needs
|
Phase 1: Map & Image Search (EMDB)
Find EM density maps, resolution, method, sample details
|
Phase 2: Structure Fitting (EMDB + PDB)
Identify fitted atomic models, fitting quality
|
Phase 3: Raw Data Access (EMPIAR)
Find raw micrographs, tilt series, particle stacks
|
Phase 4: Tomography (CryoET Data Portal)
Search cryo-ET datasets, reconstructed volumes
|
Phase 5: Cross-Reference & Context (PDB + AlphaFold)
Connect to atomic models, predicted structures, literature
|
Phase 6: Report Synthesis
Integrated EM data landscape for the target
```
---
## Phase Details
### Phase 0: Query Parsing
Identify from the user's request:
- **Target**: protein name, complex name, or organism
- **Method preference**: single particle, tomography, micro-ED, helical
- **Resolution needs**: atomic modeling (<4A), domain fitting (4-8A), shape (>8A)
- **Data type**: processed maps, raw data, fitted models, or all
### Phase 1: Map & Image Search (EMDB)
**Objective**: Find EM density maps matching the query.
**Tools**:
- `EMDB_search_structures` -- search EMDB by keyword, organism, resolution
- Input: `query` (search term), optional `resolution_min`, `resolution_max`, `method`, `limit`
- Output: entries with EMDB ID, title, resolution, method, sample
- `EMDB_get_structure` -- get full details for an EMDB entry
- Input: `emdb_id` (e.g., "EMD-1234")
- Output: map details, resolution, sample, processing info, citations
- `EMDB_get_map_info` -- get map-specific info (resolution, contour, dimensions)
- Input: `emdb_id`
- `EMDB_get_sample_info` -- get sample preparation details
- Input: `emdb_id`
**Workflow**:
1. Search EMDB for the target protein/complex
2. Sort results by resolution (best first)
3. For top entries, get full details including sample preparation and processing
4. Note the EM method used (single particle, tomography, helical, etc.)
5. Record associated PDB and EMPIAR accessions
**Resolution interpretation**:
- < 2.5A: near-atomic; side chains visible
- 2.5-4.0A: atomic; backbone and large side chains traceable
- 4.0-8.0A: domain level; secondary structure elements visible
- > 8.0A: shape; overall architecture only
### Phase 2: Structure Fitting (EMDB + PDB)
**Objective**: Find atomic models fitted into EM maps and assess fitting quality.
**Tools**:
- `EMDB_get_validation` -- get fitting/validation data for an EMDB entry
- Input: `emdb_id`
- Output: fitted PDB models, fitting statistics, validation scores
- `RCSBData_get_entry` -- get PDB entry details
- Input: `entry_id` (PDB ID)
- Output: structure details, resolution, method, citation
- `RCSBAdvSearch_search_structures` -- advanced PDB search
- Input: `query` (search term), optional `experimental_method`, `resolution_max`, `limit`
- Output: PDB entries matching criteria
**Workflow**:
1. For each EMDB entry from Phase 1, check for fitted atomic models
2. Get fitting statistics (cross-correlation, real-space R-factor if available)
3. Retrieve the PDB entry for structural details
4. If no model is fitted, search PDB for related structures by name
**Fitting quality indicators**:
- Cross-correlation coefficient > 0.7 suggests reasonable fit
- Multiple independently fitted models increase confidence
- Map-model FSC consistency check validates the fit
### Phase 3: Raw Data Access (EMPIAR)
**Objective**: Locate raw micrograph data for potential reprocessing.
**Tools**:
- `EMPIAR_search_entries` -- search EMPIAR archive
- Input: `query` (search term), optional `limit`
- Output: entries with EMPIAR ID, title, data type, size
- `EMPIAR_get_entry` -- get detailed entry information
- Input: `empiar_id` (e.g., "EMPIAR-10028")
- Output: data description, file formats, associated EMDB entries, download links
**Workflow**:
1. Search EMPIAR for entries related to the target
2. Cross-reference with EMDB entries found in Phase 1 (many EMDB entries link to EMPIAR)
3. Note data types: micrographs, particle stacks, tilt series, gain references
4. Record dataset size (can be 100s of GB to TBs)
**Data types in EMPIAR**:
- **Micrographs**: raw detector frames or motion-corrected images
- **Particle stacks**: extracted particle images
- **Tilt series**: serial images at different tilt angles (for tomography)
- **Reconstructed volumes**: 3D volumes from tomographic reconstruction
### Phase 4: Tomography (CryoET Data Portal)
**Objective**: Find cryo-electron tomography datasets for cellular and in-situ structural biology.
**Tools**:
- `CryoET_list_datasets` -- search CryoET Data Portal
- Input: `query` (search term), optional `organism`, `limit`
- Output: datasets with ID, title, organism, sample type
- `CryoET_get_dataset` -- get dataset details
- Input: `dataset_id`
- Output: sample details, tilt series parameters, tomogram info
- `CryoET_list_runs` -- search individuaRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.