CtrlK
BlogDocsLog inGet started
Tessl Logo

tooluniverse-disease-research

Generate comprehensive disease research reports using 100+ ToolUniverse tools. Creates a detailed markdown report file and progressively updates it with findings from 10 research dimensions. All information includes source references. Use when users ask about diseases, syndromes, or need systematic disease analysis.

62

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/med/tooluniverse-disease-research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

The body is highly actionable in its tool-call specifics and clearly sequenced, but it is verbose and redundant, leans on incomplete pseudocode for the core workflow, and keeps bulk reference content inline while pointing to bundle files that do not exist. It sits at the mid anchor across all four dimensions.

Suggestions

Move the full report template and the per-section tool-call lists into the referenced TOOLS_REFERENCE.md (and create that file) so SKILL.md stays a lean overview with one-level-deep references.

Replace the pseudocode workflow ('# ... continue for all dimensions', undefined helpers) with complete, executable functions, or explicitly justify the abbreviated form.

Add inline validation/feedback checkpoints between dimensions (e.g., handle empty tool results, retry with fallback terms, confirm placeholders were replaced) rather than only a final checklist, since this is a batch operation.

DimensionReasoningScore

Conciseness

The body is mostly task-specific but materially redundant — the ~200-line report template appears as a markdown block and again in Python with '[... rest of template ...]', and section expectations are restated in the 'Example Output Structure' — so it could be tightened rather than earning the lean score-3 anchor.

2 / 3

Actionability

Tool lists are concrete with exact names and parameters, but the core workflow code is incomplete pseudocode ('# ... continue for all dimensions', '[... rest of template ...]', undefined helpers like format_list_with_source), matching the score-2 anchor of some concrete guidance with pseudocode and missing details.

2 / 3

Workflow Clarity

The report-first sequence (create → research → update progressively → final checklist) is clear and ends with a verification checklist, but this batch 10-dimension / 100+-call operation lacks inline validate→fix→retry feedback loops, so per the batch-operations cap it stays at 2.

2 / 3

Progressive Disclosure

The body signals references to TOOLS_REFERENCE.md and EXAMPLES.md at the end, but those files are absent from the bundle and the bulk that belongs in them (full template + ~100 tool calls) is inline in SKILL.md, matching the score-2 anchor of content that should be separate being inline.

2 / 3

Total

8

/

12

Passed

Description

100%

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 specific, trigger-rich, complete, and distinctive — it states concrete actions and an explicit 'Use when...' clause tied to natural user phrasing about diseases and syndromes. It hits the top anchor on every dimension with no fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Generate comprehensive disease research reports', 'Creates a detailed markdown report file', 'progressively updates it with findings from 10 research dimensions', 'All information includes source references' — matching the score-3 anchor of several specific concrete actions.

3 / 3

Completeness

It explicitly answers both 'what' (generate reports, create/update markdown file, cite sources) and 'when' via an explicit 'Use when...' trigger, matching the score-3 anchor that answers both with explicit triggers.

3 / 3

Trigger Term Quality

The clause 'Use when users ask about diseases, syndromes, or need systematic disease analysis' covers natural terms a user would actually say, matching the good-coverage score-3 anchor.

3 / 3

Distinctiveness Conflict Risk

The ToolUniverse disease-report niche with 10 research dimensions and source-citation requirement is a clear, distinct scope unlikely to fire for unrelated skills, matching the score-3 clear-niche anchor.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (631 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 2 missing

Warning

Total

14

/

16

Passed

Repository
wu-yc/LabClaw
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.