Name: agent-challenges
Rating: 72.6 (1 reviews)
Author: ruvnet

Blog Docs Log in Get started

agent-challenges

Agent skill for challenges - invoke with $agent-challenges

1.59x

Quality

58%

Does it follow best practices?

Impact

99%

1.59x

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-challenges/SKILL.md

The canonical home for this skill is agent-challenges in ruvnet/claude-flow

Quality

Content

57%Weight 40%Scale 1-5

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

The content provides concrete, executable MCP tool examples and a clear section structure, but it is padded with persona prose, lacks validation checkpoints in its workflows, and inlines reference-style material that would benefit from separation. Tightening the prose and adding validation steps would raise the lowest dimensions.

Suggestions

Trim persona/marketing prose (e.g. "vibrant learning community", "foster collaboration") to lean, action-oriented guidance that assumes Claude's competence.

Add explicit validation/feedback steps to the challenge curation and submission workflow — e.g. verify submission results before reporting success and retry on validation failure.

Move the toolkit API reference and category catalog into a separate reference file and link to it from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly useful but padded with marketing-style persona language ("vibrant learning community", "foster collaboration") and gamification philosophy Claude already understands, fitting the score-3 anchor of mostly efficient with some unnecessary explanation.	3 / 5
Actionability	Concrete executable MCP calls with parameters (challenges_list, challenge_submit, achievements_list, leaderboard_get) cover the common cases, though the surrounding curation steps and category lists are high-level, matching the score-4 anchor of mostly executable guidance with minor gaps.	4 / 5
Workflow Clarity	The six-step curation approach provides a sequence but has no validation checkpoints, and challenge submission is a scored/batch-style operation, so per the feedback-loops guideline workflow clarity is capped at 3.	3 / 5
Progressive Disclosure	There are no bundle files and no external references; the single SKILL.md inlines content that could be split (toolkit reference, category catalog), fitting the score-3 anchor of some structure with content that should be separate kept inline.	3 / 5
	Total	13 / 20 Passed

Description

58%Weight 40%Scale 1-5

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 description clearly conveys what the skill does with several concrete actions and a recognizable niche, but it lacks any explicit "Use when..." trigger guidance and misses common synonym keywords. Adding a trigger clause and natural phrasing would lift the completeness and trigger-term dimensions.

Suggestions

Append a 'Use when...' clause naming concrete triggers, e.g. 'Use when users want coding challenges, to submit or validate solutions, or to view leaderboards and achievements.'

Add natural synonym keywords users actually say — 'competition', 'ranks', 'submissions', 'badges' — to broaden trigger coverage.

Clarify the rUv-credit reward action as a concrete capability to round out specificity.

Dimension	Reasoning	Score
Specificity	"Manages challenge creation, solution validation, leaderboards, and achievement systems" lists four concrete actions, matching the score-4 anchor of several specific actions with minor coverage gaps (e.g., rewards/feedback not framed as actions).	4 / 5
Completeness	It has a clear "what" but no "Use when..." or equivalent trigger clause, so per the judging guideline a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Contains relevant keywords like "coding challenges", "leaderboards", and "achievements" but omits natural synonyms such as competition, ranks, or submissions, fitting the score-3 anchor of some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	The Flow Nexus niche and specific challenge/gamification framing make it mostly distinct with only minor overlap risk against general coding-assistant skills, matching the score-4 anchor.	4 / 5
	Total	14 / 20 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/ruflo
Path: .agents/skills/agent-challenges/SKILL.md
Commit: fa13ee4

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.