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 significantly over-engineered and verbose for what it accomplishes. It repeats information across multiple sections, includes large inline templates that should be separate files, and contains aspirational sections (Metrics, Analytics, Integration) with no actionable content. The code examples provide some structure but use non-executable pseudo-syntax and lack validation/error handling for batch and destructive operations.

Suggestions

Cut the content by at least 60%: remove the duplicate Capabilities/Purpose sections, move templates to separate referenced files, and eliminate the empty Metrics/Analytics and Integration sections.

Add explicit validation steps after batch issue creation (e.g., verify gh exit codes, confirm issue numbers returned) to create proper feedback loops.

Use actually executable syntax—either proper bash commands with `gh` CLI throughout, or clarify the tool-call format with a brief note on how these pseudo-calls are interpreted.

Move the Integration Issue Template and Bug Report Template into separate referenced files (e.g., TEMPLATES.md) and link to them from the main skill.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~200+ lines. Repeats capabilities in multiple sections (frontmatter, Purpose, Capabilities). Includes extensive template boilerplate, vague 'Metrics and Analytics' and 'Integration with Other Modes' sections that add no actionable value. Explains concepts like what a bug report template is, which Claude already knows.	1 / 3
Actionability	Provides concrete code examples with specific tool calls and bash commands, but the examples use pseudo-JavaScript syntax that isn't actually executable (e.g., `mcp__claude-flow__swarm_init { topology: "star" }` is not valid in any language). Templates are useful but are markdown scaffolding rather than executable guidance. Hardcoded repo names and issue numbers reduce generalizability.	2 / 3
Workflow Clarity	The 'Complete Issue Management Workflow' shows a sequence of steps, and the progress update pattern shows a retrieve-update-store flow. 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 batch operations which the rubric specifically flags.	2 / 3
Progressive Disclosure	Monolithic wall of text with everything inline. The two full issue templates (~40 lines each) should be in separate files. No references to external files for detailed content. The 'Integration with Other Modes' and 'Metrics and Analytics' sections are stubs that add length without substance and could either be removed or linked to actual documentation.	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/ruflo
Commit: 398f7c2

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.