CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

get-tool-info

Get system tool detailed parameter definition (Level 2 disclosure). When you need to understand unfamiliar tool usage, check tool parameters, or learn tool examples. Call before using unfamiliar tools.

Quality

78%

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 ./skills/system/get-tool-info/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 content is a tight, well-organized single-purpose skill page: a concrete parameter table, clear use-case bullets, and no padding or unnecessary references. Its only gaps are slight redundancy between the Tip and When to Use sections and the absence of an example invocation.

DimensionReasoningScore

Conciseness

The body is lean with no concept over-explanation, but the Tip section ("在调用不熟悉的工具前,先用此工具了解其完整用法、参数说明和示例") largely restates the When to Use bullets and could be trimmed, matching anchor 4 rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

The Parameters table ("tool_name | string | 是 | 工具名称") is a concrete, complete spec that makes the single action executable, but no example invocation or sample output is given, leaving the minor gap that distinguishes anchor 4 from anchor 5.

4 / 5

Workflow Clarity

This is a simple single-task skill under 50 lines whose one action (call the tool with a tool name) is unambiguous, and the Tip states when to perform it, satisfying the simple-skill exception; no destructive or batch validation cap applies.

5 / 5

Progressive Disclosure

The body is short and cleanly sectioned (Parameters, When to Use, Tip) with no bundle files and no content that needs external references, satisfying the under-50-line exception for a top score with well-organized sections.

5 / 5

Total

18

/

20

Passed

Description

62%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 answers both what the skill does and when to use it with an explicit trigger clause, and it occupies a distinct niche. Its weaknesses are thin action specificity (one action plus unexplained "Level 2 disclosure" jargon) and narrow trigger-term coverage lacking synonyms.

Suggestions

Replace the unexplained "(Level 2 disclosure)" jargon with concrete actions, e.g. "Get a system tool's full parameter definitions, usage notes, and examples".

Broaden trigger terms with natural synonyms, e.g. "Use when encountering an unfamiliar tool, checking a tool's parameters or return format, or looking for tool usage examples".

Drop the redundant trailing sentence "Call before using unfamiliar tools" since the "When you need to..." clause already states it, or merge them into one explicit Use-when clause.

DimensionReasoningScore

Specificity

"Get system tool detailed parameter definition (Level 2 disclosure)" names the domain and one concrete action, but "(Level 2 disclosure)" is unexplained jargon and no multiple specific actions are enumerated, matching anchor 3 rather than the several-action coverage of anchor 4.

3 / 5

Completeness

Both a clear "what" ("Get system tool detailed parameter definition") and an explicit "when" ("When you need to understand unfamiliar tool usage... Call before using unfamiliar tools") are present, but the awkward construction and unexplained "Level 2 disclosure" jargon keep it below anchor 5's clearly-and-explicitly standard.

4 / 5

Trigger Term Quality

Phrases like "unfamiliar tool usage", "check tool parameters", and "learn tool examples" are natural, but coverage is narrow with no synonyms or common variations, matching anchor 3 rather than the good-but-slightly-incomplete coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

"system tool detailed parameter definition" carves a distinct niche that is unlikely to trigger for the wrong skill, though the generic "unfamiliar tools" phrasing leaves minor overlap risk with general tool-help concepts, matching anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

14

/

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

openakita/openakita

Path

skills/system/get-tool-info/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.