CtrlK
BlogDocsLog inGet started
Tessl Logo

devtu-code-optimization

Code quality patterns and guidelines for ToolUniverse tool development. Apply when writing, fixing, or refactoring tool Python code in the ToolUniverse project. Encodes lessons from 80+ debug rounds. Use alongside devtu-fix-tool and devtu-self-evolve. Triggers: implementing tool fixes, writing new tool classes, reviewing tool code quality, checking schema correctness, looking up API-specific bug fixes.

73

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 is an exemplar of lean, actionable skill content: a validation-gated pre-commit checklist, a signal-to-reference lookup table, and copy-paste shell commands, all supported by appropriately split one-level-deep reference files. It wastes no tokens and gives Claude exact steps to execute.

DimensionReasoningScore

Conciseness

Lean and efficient throughout — a compact pre-commit checklist, a signal-to-reference table, and bare shell commands with no conceptual padding or explanation of things Claude already knows, matching the 5 anchor.

5 / 5

Actionability

Fully executable, copy-paste-ready guidance: concrete commands like `python3 -c "import json; json.load(open('f.json'))"`, `ruff check src/tooluniverse/<file>.py`, `git rebase origin/main`, and `gh pr view <N> --json mergeable` cover the common cases exactly.

5 / 5

Workflow Clarity

The Pre-Commit Checklist is an explicit validation-gated sequence where each checkbox is a checkpoint (including the closing "Ran Skill(skill='simplify')" step), and the Git workflow includes a feedback loop (must be MERGEABLE before done), matching the 5 anchor with validation present.

5 / 5

Progressive Disclosure

A concise overview body with well-signaled, one-level-deep references to real files (references/api-fixes.md, references/code-patterns.md), each labeled with its scope, plus a table mapping signals to reference sections — clear navigation with no nested indirection.

5 / 5

Total

20

/

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.

The description is well-crafted: it states a clear purpose, an explicit Apply-when clause, and a concrete Triggers list, making both the what and the when unambiguous. It is concise, third-person, and tightly scoped to a distinct niche.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ("writing, fixing, or refactoring tool Python code", "reviewing tool code quality", "checking schema correctness", "looking up API-specific bug fixes"), but they are scoped to one project rather than maximally comprehensive, sitting just below the 5 anchor.

4 / 5

Completeness

Explicitly states both what it does ("Code quality patterns and guidelines for ToolUniverse tool development") and when to use it ("Apply when..." plus an enumerated "Triggers:" list), matching the 5 anchor that requires concrete trigger phrases.

5 / 5

Trigger Term Quality

Rich natural trigger phrases ("writing new tool classes", "reviewing tool code quality", "checking schema correctness", "looking up API-specific bug fixes") that users would plausibly say, with only a few common synonyms missing, fitting the 4 anchor.

4 / 5

Distinctiveness Conflict Risk

Tightly scoped to ToolUniverse tool development with named sibling skills (devtu-fix-tool, devtu-self-evolve) giving it a clear niche, but there is minor overlap risk among those closely related sibling skills, so it sits at 4 rather than 5.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 8 missing

Warning

Total

15

/

16

Passed

Repository
mims-harvard/ToolUniverse
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.