agent-issue-tracker

Agent skill for issue-tracker - invoke with $agent-issue-tracker

2.61x

Quality

13%

Does it follow best practices?

Impact

81%

2.61x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-issue-tracker/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 deficient across all dimensions. It provides only a label ('issue-tracker') and invocation syntax without explaining capabilities, use cases, or trigger conditions. The description would fail to help Claude select this skill appropriately from a pool of available skills.

Suggestions

Add specific concrete actions the skill performs (e.g., 'Creates, updates, and closes issues in the project tracker. Assigns issues to team members, adds labels, and tracks status changes.')

Include an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user mentions bugs, tickets, issues, tasks, or needs to track problems in a project.')

Remove the invocation syntax from the description as it doesn't help with skill selection, and replace with capability-focused content.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for issue-tracker' is completely abstract and does not describe what the skill actually does (e.g., create issues, track bugs, assign tasks).	1 / 3
Completeness	The description fails to answer both 'what does this do' and 'when should Claude use it'. It only provides invocation syntax ('invoke with $agent-issue-tracker') which is not a usage trigger.	1 / 3
Trigger Term Quality	The only potential trigger term is 'issue-tracker' which is technical jargon. Missing natural user terms like 'bug', 'ticket', 'task', 'create issue', 'track problem', etc.	1 / 3
Distinctiveness Conflict Risk	The description is too vague to be distinctive. 'Issue-tracker' could overlap with project management, bug tracking, task management, or ticketing systems without any clear differentiation.	1 / 3
	Total	4 / 12 Passed

Implementation

27%

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

This skill is significantly over-engineered and verbose, explaining concepts Claude already understands while providing pseudo-executable code rather than truly actionable commands. The content would benefit from aggressive trimming (removing template examples, best practices sections, and metrics descriptions) and splitting detailed reference material into separate files. The core functionality is buried under excessive documentation.

Suggestions

Reduce content by 70%+ by removing template examples, best practices, and metrics sections - move these to separate reference files (e.g., TEMPLATES.md, BEST_PRACTICES.md)

Convert pseudo-JavaScript MCP tool calls to actual executable syntax or clearly document the correct invocation format

Add explicit validation steps after batch operations (e.g., 'Verify issues created: gh issue list --repo :owner/:repo --limit 5')

Remove explanatory text about what issues are and what swarm coordination does - Claude knows these concepts

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive repetition of concepts Claude already knows. The skill explains what issues are, includes lengthy template examples that could be referenced externally, and repeats similar patterns multiple times (e.g., swarm initialization appears in nearly every example).	1 / 3
Actionability	Provides concrete code examples with specific tool calls, but uses JavaScript-like pseudocode syntax that isn't actually executable (e.g., `mcp__claude-flow__swarm_init { topology: "star" }` is not valid syntax). The gh CLI commands are executable, but the MCP tool invocations are illustrative rather than copy-paste ready.	2 / 3
Workflow Clarity	Steps are listed in sequences but lack explicit validation checkpoints. For batch operations creating multiple issues, there's no verification that issues were created successfully before proceeding. The 'Complete Issue Management Workflow' lacks error handling or validation steps.	2 / 3
Progressive Disclosure	Monolithic wall of text at ~250 lines with no references to external files. Templates, best practices, and detailed examples should be split into separate reference files. Everything is inline despite the content being far too long for a skill overview.	1 / 3
	Total	6 / 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: b2618f9

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.