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 functions more as an invocation instruction ('invoke with $agent-issue-tracker') than a meaningful skill description. It provides no information about what the skill does, when it should be used, or what distinguishes it from other skills.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Creates, updates, searches, and closes issues in the issue tracker. Assigns tickets, adds comments, and manages labels.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions bugs, tickets, issues, tasks, tracking work items, or managing project issues.'

Remove the invocation instruction ('invoke with $agent-issue-tracker') from the description and replace it with capability and trigger information that helps Claude select this skill appropriately.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for issue-tracker' is extremely vague and does not describe what the skill actually does (e.g., create issues, assign tickets, search bugs).	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states it's an 'agent skill' and how to invoke it, providing no functional or trigger information.	1 / 3
Trigger Term Quality	The only potentially relevant term is 'issue-tracker', but it reads more like an internal tool name than a natural keyword a user would say. Missing terms like 'bug', 'ticket', 'issue', 'task', 'Jira', 'tracking', etc.	1 / 3
Distinctiveness Conflict Risk	The description is so generic that it could overlap with any project management, task tracking, or bug reporting skill. There are no distinct triggers or specific capabilities to differentiate it.	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 excessively verbose, mixing marketing-style descriptions with actual instructions. While it provides some concrete tool call examples, they use non-executable pseudo-syntax and hardcoded values. The content would benefit enormously from being cut by 60-70%, moving templates to separate files, and adding validation steps to the batch operations workflow.

Suggestions

Cut the file to under 80 lines by removing the redundant Capabilities/Purpose sections, the 'Metrics and Analytics' section (which describes nothing actionable), and the 'Integration with Other Modes' section (which is just a list of names).

Move the two issue templates (Integration and Bug Report) to separate referenced files like TEMPLATES.md, and link to them with a single line each.

Add validation steps after batch issue creation (e.g., `gh issue list --repo :owner/:repo --state open --limit 5` to verify issues were created) to create proper feedback loops.

Replace the pseudo-JavaScript syntax with either actual executable bash commands using `gh` CLI or clearly document the exact MCP tool call format that Claude should use.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~200+ lines. Repeats capabilities in multiple sections (frontmatter, Purpose, Capabilities). Includes extensive templates, vague 'best practices' lists, and marketing-style sections ('Metrics and Analytics', 'Integration with Other Modes') that add no actionable value. Explains concepts Claude already knows and pads with unnecessary context like emoji decorations and placeholder text.	1 / 3
Actionability	Provides concrete code examples with specific tool calls and gh CLI commands, which is good. However, the code uses a pseudo-JavaScript syntax that isn't actually executable (e.g., `mcp__claude-flow__swarm_init { topology: "star" }` is not valid JS), hardcodes specific repo names/issue numbers making examples non-generalizable, and templates contain placeholder text like '[Brief description]' rather than truly executable guidance.	2 / 3
Workflow Clarity	The 'Complete Issue Management Workflow' shows a sequence of steps, and there's some logical ordering in the usage patterns. However, there are no validation checkpoints - no verification that issues were created successfully, no error handling for failed gh commands, and no feedback loops for the batch operations section which involves potentially destructive/bulk operations.	2 / 3
Progressive Disclosure	Monolithic wall of text with everything inline. The two full issue templates (~40 lines each) should be in separate files. The 'Metrics and Analytics' and 'Integration with Other Modes' sections are vague references with no actual linked content. No content is split into referenced files despite the skill being well over 200 lines.	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: 01070ed

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