CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-network-pharmacology

Compound-target-disease network construction and analysis for drug repurposing, polypharmacology discovery, and multi-target drug design. Uses STRING, BioGRID, ChEMBL, DGIdb, OMIM, OpenTargets. Use for off-target effect prediction, network-based drug repurposing, and identifying molecules with desired multi-target profile.

Quality

81%

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

71%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-organized, operationally rich pipeline document: clear 9-phase workflow, exact tool and parameter guidance, scoring rubric with thresholds, and fallback chains. The main defect is bundle integrity — most of the referenced detail files are missing, so the progressive-disclosure structure promises content it cannot deliver.

Suggestions

Add the six missing reference files (ANALYSIS_PROCEDURES.md, REPORT_TEMPLATE.md, SCORING_REFERENCE.md, TOOL_REFERENCE.md, USE_PATTERNS.md, QUICK_START.md) to the bundle, or remove/collapse the links that point to them — dead links break navigation at exactly the points where the model needs detail.

Include one minimal end-to-end example invocation inline (e.g., a single OpenTargets lookup plus Network_proximity call with sample parameters) so the common case is executable even if the reference files are unavailable.

Tighten the Network_proximity sub-bullets in Phase 3 by moving the tool's parameter aliases and testing notes into TOOL_REFERENCE.md, keeping only the Z-score guidance and the large-interactome warning in SKILL.md.

DimensionReasoningScore

Conciseness

The body is dense operational content — per-phase tool lists, parameter gotchas, fallback chains, scoring thresholds — with no padding explaining concepts Claude already knows. Not 5 because a few passages could be trimmed, e.g., the three long Network_proximity sub-bullets re-explaining testing details.

4 / 5

Actionability

Highly actionable: exact tool names per phase, exact required parameters ("ALL require query, case_sensitive, exact_match, limit"; "Use medicinalproduct NOT drug_name"), concrete thresholds (Z < -2, p < 0.01), and per-lookup fallback chains. Not 5 because there are no inline example invocations — code examples are delegated to ANALYSIS_PROCEDURES.md, which is absent from the bundle.

4 / 5

Workflow Clarity

Phases 0-8 are clearly sequenced with a reasoning-first step (entity disambiguation before analysis), explicit error recovery in the Fallback Strategies section, and a completeness checklist in Phase 8. Not 5 because process-level validation checkpoints are mostly implicit — Phase 7 gathers scientific validation evidence rather than verifying intermediate outputs.

4 / 5

Progressive Disclosure

The structure is well-designed — one-level-deep references clearly signaled at point of need and consolidated in a Reference Files section — but scored against the actual bundle, six of the seven referenced paths (ANALYSIS_PROCEDURES.md, REPORT_TEMPLATE.md, SCORING_REFERENCE.md, TOOL_REFERENCE.md, USE_PATTERNS.md, QUICK_START.md) do not exist; only scripts/network_proximity.py is present. Clearly signaled but broken references cap this below 4.

3 / 5

Total

15

/

20

Passed

Description

83%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: third-person voice, explicit what-and-when structure, concrete trigger phrases, and named source databases. The only weaknesses are incomplete synonym coverage (e.g., missing the phrase 'network pharmacology') and some overlap risk with sibling drug-repurposing skills.

DimensionReasoningScore

Specificity

Lists several concrete actions ("network construction and analysis", "off-target effect prediction", "identifying molecules with desired multi-target profile") plus the specific databases used. Not 5 because "analysis" is generic and the action coverage has minor gaps rather than being comprehensive.

4 / 5

Completeness

Explicitly answers both: the what ("Compound-target-disease network construction and analysis for drug repurposing, polypharmacology discovery, and multi-target drug design") and the when ("Use for off-target effect prediction, network-based drug repurposing, and identifying molecules with desired multi-target profile") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Contains natural user phrases like "drug repurposing", "polypharmacology", "multi-target drug design", and "off-target effect prediction". Not 5 because common synonyms are missing — notably the phrase "network pharmacology" itself and lay variants like "side effects" — while coverage clearly exceeds the 'some relevant keywords' anchor.

4 / 5

Distinctiveness Conflict Risk

The C-T-D network framing and named databases (STRING, BioGRID, ChEMBL, DGIdb, OMIM, OpenTargets) define a clear niche, but "network-based drug repurposing" overlaps with the sibling tooluniverse-drug-repurposing skill, so minor overlap risk with a closely related skill remains.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 10 missing, 5 suspicious

Warning

Total

15

/

16

Passed

Repository

mims-harvard/ToolUniverse

Path

plugin/skills/tooluniverse-network-pharmacology/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.