agent-user-tools

Agent skill for user-tools - invoke with $agent-user-tools

2.80x

Quality

17%

Does it follow best practices?

Impact

84%

2.80x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-user-tools/SKILL.md

Quality

Content

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body pairs a genuinely concrete MCP toolkit block with substantial fluff: role restatement, buzzword 'advanced features', and 'user experience optimizations' that add no actionable value. The numbered list is a capability inventory rather than a validated workflow, and everything lives inline with no reference files.

Suggestions

Cut the 'Advanced features you leverage' and 'User experience optimizations you implement' sections entirely; they are marketing copy with no executable guidance.

Reframe the numbered 'support approach' as an actual sequenced workflow with a validation/check step (e.g., verify storage upload succeeded, confirm subscription active) before declaring done.

Tighten the opening to one line and move the full tool-call reference into a references/ file, keeping SKILL.md as a lean overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	Large portions are padded marketing fluff Claude does not need ('AI-powered file categorization', 'Personalized Dashboard: Customized interface...'), and the opening self-description restates the role twice, matching the verbose/padded-with-unnecessary-context anchor.	1 / 3
Actionability	The MCP toolkit code block gives concrete, parameterized tool calls, but the surrounding 'support approach' and feature lists are vague direction rather than executable guidance, landing at the some-concrete-but-incomplete anchor rather than fully copy-paste ready.	2 / 3
Workflow Clarity	The numbered 'user support approach' reads as a list of capability categories, not a sequenced task workflow, and contains no validation or verification checkpoints, matching the steps-present-but-checkpoints-missing anchor.	2 / 3
Progressive Disclosure	Content is organized into labeled sections but it is a single monolithic file with no external references and inline material (advanced features, optimizations) that could be split out, matching the some-structure-but-could-be-better-organized anchor.	2 / 3
	Total	7 / 12 Passed

Description

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 canonical frontmatter description is meta-invoke boilerplate rather than a capability statement: it tells how to invoke the skill, not what it does or when to use it. It lacks concrete actions, natural trigger terms, and any 'Use when' guidance.

Suggestions

Replace the description with concrete actions, e.g. 'Manage user profiles, storage buckets, real-time subscriptions, and platform admin operations via Flow Nexus tools.'

Add an explicit trigger clause such as 'Use when the user needs profile updates, file storage operations, real-time subscriptions, or Queen Seraphina consultations.'

Drop the '$agent-user-tools' invoke syntax from the description; that is invocation metadata, not a capability description.

Dimension	Reasoning	Score
Specificity	The description 'Agent skill for user-tools - invoke with $agent-user-tools' names only a generic domain ('user-tools') and invoke syntax, with no concrete actions named, matching the vague/no-actions anchor.	1 / 3
Completeness	It states neither what the skill concretely does nor any 'Use when...' trigger, so both what and when are weak/missing, matching the missing-what-or-when anchor.	1 / 3
Trigger Term Quality	'user-tools' is overly generic and '$agent-user-tools' is invoke syntax a user would never naturally say, matching the no-natural-keywords/technical-jargon anchor.	1 / 3
Distinctiveness Conflict Risk	'Agent skill for user-tools' is so generic it would conflict with many other skills, matching the very-generic/would-conflict anchor.	1 / 3
	Total	4 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/claude-flow
Path: .agents/skills/agent-user-tools/SKILL.md
Commit: 26c35b5

Reviewed: about 5 hours ago

Table of Contents

Discovery Implementation Validation

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.