CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-data-integration-analysis

Integrate computed statistical results (DEGs, GWAS hits, associations) with biological context from ToolUniverse databases (UniProt, GO, Reactome, ClinVar, OpenTargets). Use for adding gene function/pathway/disease annotations to a result list, building biological narrative around statistical findings, and going beyond p-values to mechanism.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./plugin/skills/tooluniverse-data-integration-analysis/SKILL.md
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.

A well-structured methodology skill with a clear step sequence, useful lookup tables, and genuine validation thinking, but it under-delivers on execution: database queries are named rather than shown, and the causal-inference primer spends tokens re-teaching concepts Claude already knows. The three tables and evidence-grading scheme are its strongest assets.

Suggestions

Add one executable example of an actual ToolUniverse database query (e.g., a short Python snippet retrieving OpenTargets or Reactome evidence for one finding), since find_tools discovery strings alone don't show how to perform the skill's core operation.

Trim the causal-inference primer in Step 3 (confounder/mediator/collider definitions, basic MR logic, 'association is not causation') down to the domain-specific prescriptions (F-statistic > 10, MR-Egger intercept check, triangulation recipe) that Claude would not produce on its own.

Close the validation loop explicitly in Step 4: state that when genetic evidence contradicts the analysis direction (or the negative control shows an association), the finding must be downgraded or the contradiction resolved before the Step 5 report is written.

DimensionReasoningScore

Conciseness

Mostly efficient with dense tables, but Step 3 re-explains concepts Claude already knows ('Statistical association is not causation', definitions of confounders/mediators/colliders, basic MR logic), which is more than the minor trimming of the anchor above.

3 / 5

Actionability

Concrete elements exist (find_tools query strings, F-statistic > 10 threshold, report template), but the skill's central operation is left abstract ('Query GWAS Catalog or OpenTargets', 'Search PubMed/EuropePMC') with no executable example of an actual database query — key details are missing.

3 / 5

Workflow Clarity

A clear five-step sequence with an explicit falsification stage ('Before reporting a finding as robust, attempt to falsify it') and structured output templates, but there is no explicit fix-and-recheck loop after a failed cross-validation, keeping it below the full validation-loop anchor.

4 / 5

Progressive Disclosure

No bundle files exist and the single-file body is cleanly sectioned with no nested or buried references, fitting the good-structure anchor; it does not reach the top anchor because the causal-reasoning frameworks could reasonably live in a reference file and no well-signaled references exist.

4 / 5

Total

14

/

20

Passed

Description

80%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 that states concrete capabilities with specific inputs and databases and includes an explicit 'Use for' clause. Its main gaps are the absence of user-moment trigger phrases (e.g., 'when the user asks what results mean') and missing common synonyms such as 'interpret'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Integrate computed statistical results', 'adding gene function/pathway/disease annotations', 'building biological narrative') anchored by specific entities (DEGs, GWAS hits, UniProt, GO, Reactome, ClinVar, OpenTargets), matching the comprehensive-coverage anchor rather than the minor-gaps anchor.

5 / 5

Completeness

Has a clear 'what' (integrate statistical results with biological context) and an explicit 'Use for...' clause, so above the missing-when cap of 3, but the 'when' lists tasks rather than concrete user-moment triggers ('when the user asks what a result means'), fitting the anchor where 'when' could be more explicit.

4 / 5

Trigger Term Quality

Natural domain terms like 'DEGs', 'GWAS hits', 'gene function', 'pathway', 'p-values' are present, but common user phrasings such as 'interpret results' or 'functional annotation' are missing, fitting the good-coverage-with-a-few-gaps anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche (statistical-result interpretation via named ToolUniverse databases) with distinctive triggers, but it overlaps with closely related sibling skills (gene-enrichment, variant-interpretation) without explicitly disambiguating them in the description, matching the minor-overlap anchor rather than minimal-conflict.

4 / 5

Total

17

/

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-data-integration-analysis/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.