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".
56
63%
Does it follow best practices?
Impact
—
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 (with explicit 'Use when' and 'Triggers on' clauses), and includes a comprehensive set of natural trigger terms. The description is concise, uses third person voice, and is distinctive enough to avoid conflicts with 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 with specific triggers and a 'Triggers on' list). | 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 all phrases users would naturally use. | 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.
This skill provides a comprehensive reference for issue management but suffers from significant verbosity—ASCII art UI mockups, pseudocode implementation patterns, and conceptual explanations inflate the token cost without proportional value. The CLI endpoints section is the strongest part, offering concrete commands, but the surrounding content dilutes its utility. The monolithic structure with no supporting files means everything competes for attention in a single document.
Suggestions
Remove the ASCII art diagrams (menu boxes, workflow chart) and replace with brief text descriptions—Claude doesn't need visual UI mockups to understand menu flows.
Extract the 'Implementation Guide' section entirely—Claude knows how to parse JSON, route actions, and build menus; these pseudocode patterns add ~60 lines of low-value content.
Split into multiple files: keep SKILL.md as a concise overview with CLI commands and operation summaries, move data file schemas to DATA.md and error handling to ERRORS.md.
Add explicit confirmation/validation steps for bulk operations (especially bulk delete and status changes) to prevent destructive mistakes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~200+ lines with extensive ASCII art diagrams, pseudocode implementation guides, and UI mockups that Claude doesn't need. The 'Implementation Guide' section with JavaScript patterns is particularly wasteful—Claude knows how to parse JSON and route actions. The ASCII workflow diagram and menu boxes add visual noise without actionable value. | 1 / 3 |
Actionability | The CLI endpoints section is concrete and useful, providing exact commands. However, the JavaScript code examples are pseudocode-like (referencing undefined functions like `showMainMenu`, `AskUserQuestion` with unclear API), and the edit/delete flows describe conceptual steps rather than executable commands. The mix of real CLI commands and pseudo-implementation creates ambiguity. | 2 / 3 |
Workflow Clarity | Each operation has a numbered flow, and the issue lifecycle is clearly shown. However, bulk operations (destructive batch deletes, status changes) lack explicit validation/confirmation checkpoints beyond the single delete case. The bulk delete flow has no confirmation step documented, and there's no error recovery or retry guidance for failed bulk operations. | 2 / 3 |
Progressive Disclosure | Everything is crammed into a single monolithic file with no references to external files for detailed content. The implementation guide, data file documentation, error handling, and all operation details are inline. The CLI reference alone could be a separate file, and the implementation patterns should be extracted. No bundle files exist to support progressive disclosure. | 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
5ff5e86
- 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.