agent-user-tools
Agent skill for user-tools - invoke with $agent-user-tools
37
7%
Does it follow best practices?
Impact
84%
2.80xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-user-tools/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an extremely weak description that provides essentially no useful information for skill selection. It fails on every dimension: it names no concrete actions, includes no natural trigger terms, answers neither 'what' nor 'when', and is so generic it could conflict with any number of other skills.
Suggestions
Replace the entire description with concrete actions the skill performs (e.g., 'Manages user preferences, configures tool settings, lists available tools').
Add an explicit 'Use when...' clause with natural trigger terms that describe scenarios where this skill should be selected.
Specify what 'user-tools' actually refers to — name the specific tools or categories of tools to create a distinct niche and reduce conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for user-tools' is entirely vague and abstract, providing no indication of what the skill actually does. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. There is no 'Use when...' clause and no description of capabilities. | 1 / 3 |
Trigger Term Quality | There are no natural keywords a user would say. 'user-tools' is generic jargon, and '$agent-user-tools' is an invocation command, not a trigger term. No common user language is present. | 1 / 3 |
Distinctiveness Conflict Risk | 'User-tools' is extremely generic and could overlap with virtually any skill that involves user-facing tools. There is nothing to distinguish this from other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is primarily a persona description and feature catalog rather than actionable instructions. While the MCP tool signatures are a useful reference, the majority of the content consists of verbose, aspirational descriptions of capabilities and quality standards that don't help Claude perform specific tasks. The skill lacks workflows, validation steps, error handling, and concrete examples of when/how to use each tool.
Suggestions
Remove the aspirational feature lists ('Advanced features you leverage', 'User experience optimizations you implement', 'Quality standards') and replace with concrete decision logic: when to use each tool and what to do when operations fail.
Add step-by-step workflows for common multi-step operations (e.g., upload a file then verify it exists, update a profile then confirm changes) with explicit validation checkpoints.
Trim the persona/role description to 1-2 sentences—Claude doesn't need extensive identity framing to use tools correctly.
Add concrete examples showing expected inputs and outputs for each tool, including error responses and how to handle them.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive lists of features, quality standards, and optimizations that Claude already understands or that are aspirational descriptions rather than actionable instructions. Sections like 'Advanced features you leverage' and 'User experience optimizations you implement' are pure padding with no concrete guidance. | 1 / 3 |
Actionability | The tool invocation examples are concrete and show actual function signatures with parameters, which is useful. However, much of the content is descriptive rather than instructive—it lists capabilities and quality standards without showing how to actually accomplish tasks or handle specific scenarios. | 2 / 3 |
Workflow Clarity | There are no multi-step workflows, no validation checkpoints, and no error handling guidance. The numbered list under 'user support approach' describes categories of work rather than sequenced steps. For operations like storage uploads or profile updates, there's no guidance on verification or error recovery. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files and no clear hierarchy. Long lists of features and quality standards are inlined that could be separated or, more appropriately, removed entirely since they add no actionable value. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- ruvnet/claude-flow
- Commit
9d4a9ea
- 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.