CtrlK
BlogDocsLog inGet started
Tessl Logo

tool-assistant

Tool-calling assistant with backend functions for time, city time, weather, and temperature conversion, plus cost metering and approval workflows. Use when a question needs real-time data via tool calls.

56

Quality

64%

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 ./modules/skills/src/main/resources/META-INF/skills/tool-assistant/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 skill gives clear, sectioned behavioral guidance for an instruction-only assistant, but suffers from a duplicated tool list, missing tool signatures, and no explicit workflow with validation/retry checkpoints.

Suggestions

Remove the duplicated tool list — keep tool definitions in one place (e.g. only the '## Tools' section) and reference them from the intro.

Add tool signatures or parameter details (e.g. 'get_weather(city: str) -> report') so Claude knows how to invoke each tool.

Add an explicit error-recovery workflow, e.g. 'If a tool call fails, retry once with corrected arguments; if it still fails, report the error plainly to the user.'

DimensionReasoningScore

Conciseness

Mostly short, but the four tools are listed twice (intro bullets and the '## Tools' section) and the '## Skills' section restates capabilities already implied, so it could be tightened by consolidating.

3 / 5

Actionability

Behavioral guidance is concrete (when to use tools, chain calls, report cost/latency, explain failures), but no tool signatures or parameters are given, so Claude lacks the execution details needed to actually invoke each tool.

3 / 5

Workflow Clarity

Capabilities like chaining tool calls are mentioned but not sequenced into a clear workflow, and the failure guidance ('explain what went wrong plainly') provides no explicit validation or retry feedback loop.

3 / 5

Progressive Disclosure

The body is under 50 lines with no external references needed and is organized into clear sections (Skills, Tools, Guardrails); minor organization gaps from the duplicated tool list keep it just below the well-organized anchor.

4 / 5

Total

13

/

20

Passed

Description

75%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 clearly states concrete capabilities and includes an explicit 'Use when' trigger, covering both what and when. It could be sharper by listing concrete trigger domains and adding user-natural synonyms.

Suggestions

Replace the generic 'Use when a question needs real-time data via tool calls' with concrete triggers, e.g. 'Use when the user asks about the current time, time in a city, weather, or temperature conversions.'

Add natural synonyms users actually say ('forecast', 'current time', 'Celsius/Fahrenheit') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names several concrete capabilities ('time, city time, weather, and temperature conversion, plus cost metering and approval workflows'), but 'cost metering and approval workflows' are stated generically rather than as concrete named actions, leaving minor gaps versus the comprehensive anchor.

4 / 5

Completeness

Explicitly answers 'what' (named backend functions) and 'when' ('Use when a question needs real-time data via tool calls'), but the trigger is generic rather than enumerating the concrete domains (asking about weather, time, or temperature), so it falls short of the concrete-trigger-phrases anchor.

4 / 5

Trigger Term Quality

Includes natural domain terms ('time', 'city time', 'weather', 'temperature conversion', 'real-time data') that users would actually say, but misses common synonyms like 'forecast', 'current time', or 'Celsius/Fahrenheit'.

4 / 5

Distinctiveness Conflict Risk

The time/weather/temperature niche is fairly distinct, but the broad 'tool-calling assistant' framing and generic 'real-time data via tool calls' trigger create minor overlap risk with other tool-using skills.

4 / 5

Total

16

/

20

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

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
Atmosphere/atmosphere
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.