issue-manage
Interactive issue management with menu-driven CRUD operations. Use when managing issues, viewing issue status, editing issue fields, performing bulk operations, or viewing issue history. Triggers on "manage issue", "list issues", "edit issue", "delete issue", "bulk update", "issue dashboard", "issue history", "completed issues".
70
63%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/issue-manage/SKILL.mdQuality
Discovery
100%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 is a strong skill description that clearly communicates what the skill does (interactive issue management with CRUD operations), when to use it (explicit 'Use when' clause), and includes a comprehensive list of trigger terms. The description is concise, uses third person voice, and provides enough specificity to distinguish it from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: menu-driven CRUD operations, managing issues, viewing status, editing fields, performing bulk operations, and viewing issue history. | 3 / 3 |
Completeness | Clearly answers both 'what' (interactive issue management with menu-driven CRUD operations) and 'when' (explicit 'Use when...' clause plus a 'Triggers on' list with specific phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'manage issue', 'list issues', 'edit issue', 'delete issue', 'bulk update', 'issue dashboard', 'issue history', 'completed issues'. These are natural phrases a user would type. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around interactive, menu-driven issue management with specific triggers like 'issue dashboard', 'bulk update', and 'issue history' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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.
The skill provides comprehensive coverage of issue management operations with good CLI command references, but suffers from significant verbosity—ASCII art mockups, decorative tables, and implementation guide code that could be split into separate files or removed entirely. The bulk operations section lacks validation checkpoints for destructive actions, and the entire content would benefit from being restructured into a concise overview with references to detailed sub-documents.
Suggestions
Remove or drastically reduce the Implementation Guide section—Claude doesn't need JavaScript routing patterns spelled out; the CLI endpoints are sufficient for actionability.
Remove ASCII art UI mockups (filter boxes, issue detail boxes, workflow diagrams) which consume tokens without adding actionable information.
Add explicit validation/confirmation steps to bulk operations (e.g., 'Preview affected issues before executing', 'Confirm count matches expected', 'Verify results after batch update').
Split into multiple files: keep SKILL.md as a concise overview with CLI commands and flows, move implementation patterns to IMPLEMENTATION.md and data file schemas to DATA.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~200+ lines with extensive ASCII art diagrams, implementation guide code that Claude doesn't need (JavaScript patterns for menu routing, filter patterns, edit patterns), and visual mockups of UI elements. Much of this is decorative rather than instructional, and the implementation guide essentially re-explains how to use the CLI commands already listed. | 1 / 3 |
Actionability | The CLI endpoints section provides concrete, executable commands which is strong. However, the JavaScript implementation examples are pseudocode-like patterns (e.g., `AskUserQuestion` with no real import/setup, `Bash()` calls without context), and the edit pattern shows comments like '// Read → Parse → Update → Write' instead of actual code. | 2 / 3 |
Workflow Clarity | Each operation has a clear flow with numbered steps, and the issue lifecycle is well-defined. However, bulk operations (destructive batch deletes, status changes) lack explicit validation/confirmation checkpoints and feedback loops for error recovery, which should cap this at 2 per the rubric's scoring notes. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files despite being complex enough to warrant splitting (e.g., implementation guide, data file schemas, queue management could each be separate documents). Everything is inlined into one massive file with no bundle files to support it. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Repository
- catlog22/Claude-Code-Workflow
- Commit
227244f
- Reviewed
Table of Contents
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.