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 description is critically underspecified. It fails to communicate what the skill does, when it should be used, or what domain it operates in. The word 'challenges' is too vague to serve as a meaningful differentiator among multiple skills.

Suggestions

Specify what kind of challenges this skill handles (e.g., coding challenges, CTF challenges, puzzle-solving) and list concrete actions it performs (e.g., 'Solves competitive programming problems, analyzes test cases, optimizes solutions').

Add an explicit 'Use when...' clause with natural trigger terms users would say, such as 'Use when the user asks for help with coding competitions, LeetCode problems, or algorithmic challenges.'

Replace the generic 'Agent skill for challenges' phrasing with a third-person description of specific capabilities to make it clearly distinguishable from other skills.

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 explanation of capabilities and no 'Use when...' clause or equivalent trigger guidance.	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 trigger, not a natural language keyword.	1 / 3
Distinctiveness Conflict Risk	The term 'challenges' is extremely broad and could overlap with any skill involving problem-solving, coding challenges, puzzles, competitions, or troubleshooting. 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 reads more like a product description or persona prompt than an actionable skill document. It is heavily padded with explanatory content about concepts Claude already understands (gamification, algorithms, quality standards) while lacking concrete workflows, validation steps, and executable examples. The MCP tool calls are a positive element but are insufficient to make this skill practically useful.

Suggestions

Remove the verbose descriptive sections (challenge categories, quality standards, gamification features) and replace them with concrete workflows showing how to chain MCP calls for common tasks like 'user requests a challenge → assess level → present challenge → validate submission → update leaderboard'.

Add explicit validation and error-handling steps, e.g., what to do when challenge_submit returns an error, how to verify a solution was recorded, and how to handle timeout or invalid code scenarios.

Replace the abstract 'challenge curation approach' with a concrete decision tree or step-by-step workflow with specific conditions and actions, including example inputs and expected outputs from each MCP call.

Extract detailed category descriptions and gamification feature lists into a separate reference file if they're needed at all, keeping SKILL.md focused on the essential operational instructions.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive explanations of concepts Claude already knows (what gamification is, what algorithms are, what quality standards mean). The challenge categories, quality standards, and gamification features sections are padded descriptions that don't add actionable value. Much of this reads like a product marketing document rather than a skill instruction.	1 / 3
Actionability	The JavaScript MCP tool calls provide some concrete guidance on how to invoke the API, but they use placeholder values and lack complete workflows showing how to handle responses, error cases, or chain calls together. The 'challenge curation approach' is a list of abstract steps rather than executable instructions.	2 / 3
Workflow Clarity	The six-step 'challenge curation approach' is vague and abstract with no validation checkpoints, no error handling, and no concrete sequencing. There's no guidance on what to do when submissions fail validation, how to handle edge cases, or how to verify correct operation of any workflow.	1 / 3
Progressive Disclosure	The content is a monolithic wall of text with no references to external files and no clear separation between overview and detailed content. Everything is dumped into a single file with no navigation structure, and there are no bundle files to support progressive disclosure.	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: 9d4a9ea

Reviewed: 6 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.