CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-protein-interactions

Protein-protein interaction (PPI) network analysis — STRING (predicted + experimental), BioGRID (curated), SASBDB (small-angle scattering), Complex Portal (curated complex membership and stoichiometry, includes CORUM data). Distinguishes physical interactions (binding) from functional associations (co-expression, co-regulation). Use for interactome queries, complex partner identification, curated complex composition lookup, and pathway-level interaction analysis.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is tooluniverse-protein-interactions in mims-harvard/ToolUniverse

SKILL.md
Quality
Evals
Security

Quality

Content

60%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.

The body delivers strong, concrete, live-verified tool guidance (database coverage, parameters, edge fields, per-tool gotchas, and explicit workflows), but it is undermined by a missing bundle: both referenced files (python_implementation.py, KNOWN_ISSUES.md) do not exist, so the progressive-disclosure structure is broken and the promised runnable examples are unavailable. Additionally, several 'Domain Reasoning' sections teach generic biochemistry (valency/avidity, coiled-coils, detergents, amyloid clearance) unrelated to the skill's tools and inflate the token budget.

Suggestions

Fix progressive disclosure: either add the referenced python_implementation.py and KNOWN_ISSUES.md files or remove the dead references, and split the extended tool catalogs (SIGNOR, EBI Proteins, Extended Analysis Tools) into one-level-deep reference files with clearly signaled links from SKILL.md.

Trim conciseness: remove or compress the textbook 'Domain Reasoning' sections on multimeric binding statistics, coiled-coil prediction, detergent effects, and protein-identification trivia — Claude already knows this biochemistry, and none of it is specific to the ToolUniverse tools.

Improve actionability: inline at least one complete runnable example (imports, ToolUniverse setup, a full call sequence) for the 4-phase workflow so users are not dependent on the missing python_implementation.py.

DimensionReasoningScore

Conciseness

Most of the body is lean and tool-specific (database table, parameter tables, edge-field definitions, verified gotchas like "ComplexPortal_get_complex can return complex_id: null"), but roughly a quarter of it (~50 lines) teaches textbook biochemistry Claude already knows: "Avidity vs affinity", Hill/Scatchard plot explanations, heptad-repeat coiled-coil packing rules, mild-vs-harsh detergent effects, and an amyloid-clearance trivia section. This matches 'Mostly efficient but includes some unnecessary explanation or could be tightened' — not score 2, since the padding is confined to discrete sections rather than pervading the document, and not score 4, because entire off-topic sections (Multimeric Assemblies, Coiled-Coil, Detergent Effects, Protein Identification) explain concepts unrelated to the skill's tools.

3 / 5

Actionability

Guidance is mostly executable: concrete calls with parameters and example values such as "SIGNOR_connect_proteins(proteins=["P00533", "P28482"], level=2)", "ComplexPortal_search_complexes(query=..., species=..., number=...)", a copy-paste snippet "interaction_ids = result.get("metadata", {}).get("interaction_ids", [])", and verified output expectations. It stops short of 'fully executable / copy-paste ready covering common cases' because "See python_implementation.py for runnable examples (example_tp53_analysis(), analyze_protein_network())" points to a file that does not exist in the skill bundle — the promised runnable examples are not actually available — and there is no import/setup context for the ToolUniverse functions.

4 / 5

Workflow Clarity

The core "4-Phase Workflow" is clearly sequenced (identifier mapping → network retrieval → enrichment → optional structural data), Complex Portal and SIGNOR each get their own explicit multi-step flows, and the Troubleshooting section provides recovery feedback loops ("No interactions found: verify protein names (case-sensitive), try confidence_score=0.4"; "BioGRID not working: set BIOGRID_API_KEY"). It sits at 'Clear sequence with most checkpoints present; minor validation gaps' rather than 5 because validation checkpoints are advisory and scattered (e.g., check escore for binding evidence) rather than formalized as explicit gates in the workflow steps themselves.

4 / 5

Progressive Disclosure

The skill has no bundle files at all (no references/, scripts/, or assets/), yet the body points to "python_implementation.py" and "(see KNOWN_ISSUES.md)" — both nonexistent, i.e., broken references. Meanwhile ~230 lines are inlined monolithically, including extended tool catalogs (the SIGNOR section with its tables and workflows, the EBI Proteins/Gotcha sections, Extended Analysis Tools) and textbook domain sections that clearly belong in separate reference files. This matches the anchor 'Minimal structure; content that clearly belongs in separate files is inlined; or references are buried' — the section headers give some structure, but the split-file organization the document itself assumes is not actually present.

2 / 5

Total

13

/

20

Passed

Description

92%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.

The description is excellent: specific, database-scoped capabilities, an explicit physical-vs-functional interaction distinction, and a clear 'Use for...' clause covering the main query types. The only minor gap is a few natural trigger phrasings (e.g., 'binding partners', 'does protein X interact with protein Y') that would broaden trigger coverage.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions with comprehensive coverage: "network analysis", "Distinguishes physical interactions (binding) from functional associations (co-expression, co-regulation)", and use cases "interactome queries, complex partner identification, curated complex composition lookup, and pathway-level interaction analysis", each tied to named databases (STRING, BioGRID, SASBDB, Complex Portal) with their specific roles. It matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage'; nothing is vague or generic.

5 / 5

Completeness

Both questions are answered explicitly and concretely: the 'what' ("Protein-protein interaction (PPI) network analysis — STRING... BioGRID... SASBDB... Complex Portal... Distinguishes physical interactions (binding) from functional associations") and the 'when' ("Use for interactome queries, complex partner identification, curated complex composition lookup, and pathway-level interaction analysis"). This matches the top anchor: clearly and explicitly answers both what AND when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good keyword coverage with the key synonym expansion "Protein-protein interaction (PPI)", plus natural domain terms like "interactome", "complex", "stoichiometry", "pathway", and "binding". It falls just short of the comprehensive anchor because a few natural user phrasings are missing (e.g., "binding partners", "does X interact with Y", "protein association"), placing it at 'Good keyword coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (PPI network analysis with named databases and interaction-type distinctions) with distinct trigger phrases like "interactome queries" and "curated complex composition lookup". Only a skill in the same narrow domain would collide, so conflict risk is minimal — matching the anchor 'Clear niche with distinct triggers; minimal conflict risk'.

5 / 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

plugins/tooluniverse/skills/tooluniverse-protein-interactions/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.