devtu-optimize-skills

Review and optimize ToolUniverse research skills for evidence-graded, complete report output.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/AvaTar-ArTs/.Agent-skills --skill devtu-optimize-skills-avatar-arts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: devtu-optimize-skills
Source: https://github.com/AvaTar-ArTs/.Agent-skills/tree/main/skills/devtu-optimize-skills
Command: npx skills add https://github.com/AvaTar-ArTs/.Agent-skills --skill devtu-optimize-skills-avatar-arts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? ToolUniverse research skills often produce noisy, incomplete, or process-heavy reports due to silent tool failures, wrong API parameters, missing disambiguation, and ungraded evidence. This Skill provides a structured methodology and checklist to diagnose and fix those quality problems. ## Core Features & Use Cases - Tool Contract Verification: Verify tool parameters via get_tool_info(), maintain corrections tables, and handle versioned versus unversioned identifiers (e.g., GTEx Ensembl IDs). - Research Workflow Patterns: Apply foundation-data-first queries, disambiguation phases with collision filtering, citation expansion, and retry/fallback chains for flaky APIs like PubMed and EuropePMC. - Report Quality Standards: Enforce T1-T4 evidence grading, quantified completeness minimums, mandatory sections, aggregated Data Gaps sections, and narrative reports separated from JSON bibliographies. - Use Case: When a gene-target research skill returns empty GTEx expression data and a report full of search logs, use this Skill to identify the versioned-ID issue, add fallback chains, and restructure the output into a content-focused report. ## Quick Start Review my ToolUniverse research skill and optimize it using the evidence grading, disambiguation, and completeness checklist patterns.

Frequently Asked Questions about devtu-optimize-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I improve the quality of a ToolUniverse research skill report?▼

Apply the optimization patterns in this Skill: add a disambiguation phase before literature search, grade every claim with T1-T4 evidence tiers, enforce quantified completeness minimums per section, and separate the narrative report from the JSON bibliography.

Why does my ToolUniverse skill return empty results without errors?▼

Silent failures usually come from wrong tool parameter names or missing versioned identifiers. Verify parameters with get_tool_info() before calling unfamiliar tools, and try versioned Ensembl IDs (e.g., ENSG00000123456.12) for APIs like GTEx.

How do I handle naming collisions in gene literature searches?▼

Add a disambiguation phase that resolves official identifiers (UniProt, Ensembl, NCBI, ChEMBL), tests the gene symbol with a title search, and builds negative filters like NOT plasmid NOT conjugation when collisions exceed roughly 20 percent of results.

What should I do when PubMed or GTEx tools fail during a research workflow?▼

Use the retry protocol: attempt, wait 2 seconds, retry, wait 5 seconds, then fall back to an alternative source such as EuropePMC for citations or HPA for expression data. Always document failures in the report's Data Gaps section.

When should I not apply evidence grading to a report?▼

Evidence grading should always be applied to research claims; there is no skip case. The T1-T4 tiers distinguish mechanistic studies from mere mentions, and every disease association and key paper should carry a tier label.