agent-user-tools
Agent skill for user-tools - invoke with $agent-user-tools
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-user-tools26
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 description is critically deficient across all dimensions. It provides only an invocation command without explaining what the skill does, when to use it, or any natural trigger terms. Claude would have no basis for selecting this skill appropriately from a list of available skills.
Suggestions
Replace the entire description with concrete actions the skill performs (e.g., 'Manages user preferences, configures settings, handles authentication tokens').
Add an explicit 'Use when...' clause with natural trigger terms users would actually say (e.g., 'Use when the user asks about settings, preferences, account configuration, or login issues').
Remove the invocation syntax '$agent-user-tools' from the description - this is implementation detail, not selection criteria for Claude.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for user-tools' is completely abstract with no indication of what the skill actually does. | 1 / 3 |
Completeness | Missing both 'what' and 'when'. The description only provides an invocation command but explains neither what the skill does nor when Claude should use it. | 1 / 3 |
Trigger Term Quality | No natural keywords users would say. 'user-tools' and '$agent-user-tools' are technical jargon/internal naming conventions, not terms a user would naturally use when requesting help. | 1 / 3 |
Distinctiveness Conflict Risk | 'User-tools' is extremely generic and could conflict with virtually any skill that involves user interaction or tools. There are no distinct triggers to differentiate it. | 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 heavily padded with conceptual descriptions and feature lists that don't provide actionable guidance. While it includes useful function signatures, it lacks executable workflows, validation steps, and proper content organization. The content reads more like marketing copy than a technical skill document.
Suggestions
Remove verbose sections like 'Quality standards', 'Advanced features', and 'User experience optimizations' - these describe concepts Claude already knows
Add complete, executable workflow examples showing how to chain operations (e.g., upload file -> get URL -> verify access)
Include validation and error handling patterns for storage operations and subscriptions
Restructure into a concise quick-start section with references to separate detailed documentation for advanced topics
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive lists of features Claude already understands conceptually. Sections like 'Quality standards', 'Advanced features', and 'User experience optimizations' are padded descriptions that don't add actionable value. | 1 / 3 |
Actionability | Provides concrete JavaScript function signatures with parameters, which is useful. However, the examples use placeholder values and lack complete workflows showing how to chain operations or handle responses/errors. | 2 / 3 |
Workflow Clarity | No clear multi-step workflows or validation checkpoints. The 'user support approach' is a vague numbered list of concepts, not executable sequences. Missing feedback loops for storage operations or subscription management. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external documentation. All content is inline regardless of complexity. No clear navigation structure or separation between quick-start and advanced content. | 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.
- 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.