CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, domain-rich pipeline: clear phase sequencing, named tools with parameters, a decision matrix, quality checklist, and thoughtful edge-case fallbacks. It loses points on conciseness (repeated resolution guidance, a basic EM-modality primer, a tangential IDR section) and on progressive disclosure, where a ~290-line monolith inlines tool API details and an off-topic related-resource guide that belong in reference files.

Suggestions

State the resolution bands once (Phase 1's interpretation table is the best home) and have the guiding principles and decision matrix reference them instead of restating them.

Move the per-tool input/output documentation for Phases 1-5 and the entire IDR section into references/ files (e.g., references/tools.md and references/idr.md), keeping SKILL.md as a phase-and-workflow overview with one-level-deep pointers.

Drop or compress the 'TEM resolves individual protein complexes (~2nm)... SEM shows surface topology' paragraph — it is textbook EM knowledge Claude already has — and add one runnable tu.run_tool example per phase so tool invocation syntax is explicit.

DimensionReasoningScore

Conciseness

Mostly efficient domain-specific content (tool names, FSC 0.143 vs 0.5 cutoff, cross-correlation > 0.7 thresholds), but with real tightening opportunities: resolution bands are stated three times ('sub-4A enables atomic modeling, 4-8A enables domain fitting, >8A is shape-level' in the principles, the Phase 1 'Resolution interpretation' table, and the Phase 6 decision matrix), the 'EM resolution determines what you can see. TEM resolves... SEM shows surface topology' paragraph is basic knowledge Claude already has, and the ~25-line IDR light-microscopy section is tangential to an EM skill. This matches 'Mostly efficient but includes some unnecessary explanation or could be tightened' rather than a 4, where only minor trimming would be needed.

3 / 5

Actionability

Concrete, callable guidance: every phase names its tools with inputs and outputs ('EMDB_search_structures -- Input: query, optional resolution_min, resolution_max, method, limit'), and the IDR section even gives a runnable invocation ('tu.run_tool("IDR_search_studies", {"key": "Gene Symbol", "value": "TP53"})'). Not a 5 because the EM/PDB/CryoET tool listings stop at parameter tables — none include an actual call example in the tu.run_tool form that the IDR section demonstrates, leaving the exact invocation syntax implicit for ~15 tools.

4 / 5

Workflow Clarity

A clearly sequenced 7-phase pipeline with per-phase numbered workflows, a decision matrix ('Which map should I use?'), a quality assessment checklist, and an Edge Cases & Fallbacks section covering failure paths ('No EMDB entries' → search PDB with method filter). Not a 5: while the Phase 6 checklist and fallback branches approximate validation, there are no explicit verify-then-retry loops (e.g., confirming a returned EMDB entry actually matches the queried target before building on it), and not a 3 since checkpoints like the FSC-cutoff and fitting-statistics checks are explicit rather than absent.

4 / 5

Progressive Disclosure

The skill is a single ~290-line file with no bundle files at all; the per-tool API documentation (inputs/outputs for ~15 tools across Phases 1-5) and the entire IDR section are inline material that would naturally live in references/ files. Section headers and tables give it real structure — above anchor 2's '300 lines of API reference with no section headers' — but it matches anchor 3: 'Some structure... content that should be separate is inline'. Not a 4/5: the guideline's exception for well-organized single files applies to skills under 50 lines; this one has clear separation candidates it doesn't use.

3 / 5

Total

14

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete actions, explicit 'Use for' triggers, natural terminology, and third-person voice throughout. Its only weakness is minor overlap risk with general PDB/protein-structure skills via the '3D structural data on a protein/complex' and 'fitted atomic models (PDB)' phrasing.

Suggestions

Narrow the broad trigger 'finding 3D structural data on a protein/complex' to something EM-specific like 'finding cryo-EM maps or fitted models for a protein/complex' to reduce overlap with general protein-structure skills.

Consider replacing 'fitted atomic models (PDB)' with 'atomic models fitted to EM maps (PDB)' so generic PDB queries route to a PDB skill instead.

DimensionReasoningScore

Specificity

The description lists multiple concrete, specific actions — 'Search and analyze electron microscopy data', 'finding 3D structural data on a protein/complex, comparing experimental EM resolution to AlphaFold confidence, and accessing raw EM data for re-processing' — each tied to named resources (EMDB, PDB, EMPIAR, CryoET Data Portal). This matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage'. It is not a 4 because coverage is comprehensive across the full data spectrum with no minor gaps; it is not below because no action is generic.

5 / 5

Completeness

It explicitly answers 'what' ('Search and analyze electron microscopy data — cryo-EM density maps (EMDB), fitted atomic models (PDB), raw micrograph datasets (EMPIAR), and cryo-electron tomography volumes') and 'when' via an explicit 'Use for...' clause with three concrete trigger scenarios ('finding 3D structural data on a protein/complex, comparing experimental EM resolution to AlphaFold confidence, and accessing raw EM data for re-processing'). This matches the anchor-5 good example structure exactly; a 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Natural user vocabulary is well covered: 'electron microscopy', 'cryo-EM', 'density maps', 'micrograph', 'tomography', '3D structural data', 'protein/complex', 'AlphaFold', 'EM resolution', 'raw EM data'. These match the phrases a structural biology user would actually say, satisfying the anchor 'Comprehensive coverage of natural terms including synonyms'. Not a 4: no common variations (cryo-EM / EM / electron microscopy; micrograph; tomography) are missing.

5 / 5

Distinctiveness Conflict Risk

The EM niche (EMDB/EMPIAR/CryoET) is clearly staked out with distinct triggers, but two phrases create minor overlap risk with closely related structural-biology skills: 'fitted atomic models (PDB)' and 'Use for finding 3D structural data on a protein/complex' — the latter is broad enough to also fit a protein-structure-prediction or PDB-search skill. This fits 'Mostly distinct; minor overlap risk with closely related skills'; not a 5 because the PDB/3D-structure phrasing is shared territory, not a 3 because the EM-specific framing dominates.

4 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

mims-harvard/ToolUniverse

Path

plugin/skills/tooluniverse-electron-microscopy/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.