agent-challenges

Agent skill for challenges - invoke with $agent-challenges

1.59x

Quality

Does it follow best practices?

Impact

99%

1.59x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-challenges/SKILL.md

Quality

Discovery

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 fails on all dimensions. It provides no concrete actions, no trigger guidance, no 'when to use' clause, and uses language so vague that it would be impossible for Claude to reliably select this skill from a pool of available options.

Suggestions

Describe the specific actions this skill performs—what kind of 'challenges' does it handle? (e.g., 'Solves coding challenges, competitive programming problems, and algorithmic puzzles')

Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks for help with coding challenges, LeetCode problems, or algorithm exercises')

Replace the invocation instruction ('invoke with $agent-challenges') with a functional description—skill descriptions should help Claude decide when to use the skill, not just how to invoke it

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for challenges' is extremely vague—it doesn't describe what the skill does, what kind of challenges, or what actions it performs.	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 functionality beyond the vague word 'challenges.'	1 / 3
Trigger Term Quality	The only keyword is 'challenges,' which is overly generic and not a natural term users would use to invoke a specific capability. The invocation command '$agent-challenges' is a technical artifact, not a natural trigger term.	1 / 3
Distinctiveness Conflict Risk	The term 'challenges' is extremely generic and could overlap with virtually any problem-solving, debugging, troubleshooting, or puzzle-related skill. There is nothing to distinguish this skill from others.	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 rather than actionable instructions. While it includes useful MCP tool call examples, the majority of the content consists of verbose lists of responsibilities, categories, quality standards, and gamification features that describe what the agent should be rather than providing concrete, executable guidance on how to accomplish specific tasks. The skill would benefit greatly from being restructured around concrete workflows with validation steps.

Suggestions

Replace the verbose responsibility lists and quality standards with concrete workflows showing step-by-step how to handle common scenarios (e.g., 'User requests a challenge' → specific tool calls → validation → response format).

Add explicit validation checkpoints for solution submission workflows, including how to handle failed submissions, edge cases, and error feedback loops.

Remove or drastically condense the category lists, gamification feature descriptions, and quality standards—these are conceptual descriptions Claude doesn't need spelled out at this length.

Add concrete examples of expected input/output for key interactions (e.g., what a challenge recommendation response should look like, how to format solution feedback).

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive descriptions of responsibilities, quality standards, gamification features, and approach that Claude already understands conceptually. The bullet-heavy lists of categories, quality standards, and gamification features add little actionable value and consume significant tokens.	1 / 3
Actionability	The MCP tool calls provide some concrete, executable guidance with parameter examples, which is useful. However, much of the content is descriptive rather than instructive—listing categories and quality standards without showing how to actually use them in practice or providing real workflow examples.	2 / 3
Workflow Clarity	The 'challenge curation approach' lists 6 steps but they are vague and abstract (e.g., 'Evaluate user's current skill level') with no concrete instructions, validation checkpoints, or error handling. There's no clear workflow for how to actually process a challenge submission end-to-end.	1 / 3
Progressive Disclosure	The content is a monolithic wall of text with no references to external files, no clear navigation structure, and no separation of overview from detailed content. Everything is dumped into a single document with no progressive disclosure strategy.	1 / 3
	Total	5 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/claude-flow
Commit: f547cec

Reviewed: 4 days 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.