CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tool-discovery

Discover the smallest capable tool set and confirm argument schemas before acting

Quality

77%

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 ./resources/skills/agent/tool-discovery/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 lean, well-sequenced procedure with explicit feedback and verification checkpoints that respects the token budget completely. The only gap is the absence of a worked example that would make the abstract capability-translation step concrete.

DimensionReasoningScore

Conciseness

The ~25-line body is lean with zero padding and no explanation of concepts Claude already knows; directives like 'Prefer one direct tool over a chain of indirect tools when it can complete the operation and provide evidence' earn every token, matching the anchor-5 example of assuming Claude's competence.

5 / 5

Actionability

Steps are concrete and directive ('Make a small read-only probe when the environment or target is uncertain'; 'only broaden the tool search if the result shows a concrete capability gap'), but there is no worked example of translating a request into capabilities, which anchor 5's 'specific examples cover the common cases' would require. It sits above anchor 3 because the guidance is executable as written, not pseudocode.

4 / 5

Workflow Clarity

The six-step Procedure is clearly sequenced with a pre-call parameter checkpoint (step 4), an explicit feedback loop (step 6: 'only broaden the tool search if the result shows a concrete capability gap'), and a dedicated Verification section ('evidence of the requested effect or a specific error that guides the next step'), matching the anchor-5 pattern of validation steps plus error-recovery loops. The skill is not destructive or batch, so no cap applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files (no references/, scripts/, or assets/ exist) and nothing inlined that belongs in a separate file; its four well-organized sections (When to Use, Procedure, Pitfalls, Verification) satisfy the guideline that short single-file skills can score 5.

5 / 5

Total

19

/

20

Passed

Description

53%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 communicates a clear and fairly distinctive 'what' but omits any 'use when' trigger guidance and leans on jargon rather than natural user keywords, leaving it mid-range on completeness and trigger quality. Adding an explicit trigger clause with user-facing phrasings would raise most dimensions simultaneously.

Suggestions

Add an explicit trigger clause to the description, e.g., 'Use when the right tool is unclear, many tools are available, or a previous call failed because the wrong tool or parameters were selected.'

Include natural user phrasings and synonyms such as 'find the right tool', 'pick a tool', 'check tool arguments', and 'failed tool call' alongside the jargon term 'argument schemas'.

Name one or two more concrete actions (e.g., 'inspect tool descriptions and schemas, and probe uncertain targets with a read-only call') to lift specificity beyond the current two-action coverage.

DimensionReasoningScore

Specificity

The description names the tool-selection domain with two concrete actions ('Discover the smallest capable tool set', 'confirm argument schemas before acting'), matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It does not reach 4 because there are only two actions, not several, and 'discover' is somewhat abstract.

3 / 5

Completeness

The 'what' is clearly stated (discover a minimal capable tool set, confirm argument schemas) but there is no 'Use when...' clause or equivalent trigger guidance; 'before acting' conveys sequencing, not when to invoke the skill, so per the judging guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

Terms like 'tool set' and 'argument schemas' are relevant to the domain but jargon-leaning; natural phrases a user would actually say (e.g., 'find the right tool', 'pick a tool', 'tool call failed', 'wrong parameters') and their synonyms are absent, fitting 'Some relevant keywords but missing common variations or synonyms' rather than 4's fuller keyword coverage.

3 / 5

Distinctiveness Conflict Risk

The meta-niche of tool selection and schema confirmation ('smallest capable tool set', 'argument schemas') is mostly distinct from content-domain skills, with only minor overlap risk against other agent/planning meta-skills, matching 'Mostly distinct; minor overlap risk with closely related skills'. It falls short of 5 because terms like 'tool' and 'acting' remain somewhat broad.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

odysseus-dev/odysseus

Path

resources/skills/agent/tool-discovery/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.