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
92%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 description that clearly communicates capabilities, provides explicit trigger guidance, and uses natural language terms. Its main weakness is that 'issue management' is a broad domain that could overlap with platform-specific issue trackers (e.g., GitHub Issues, Jira), and the description doesn't specify which system or context it operates in, creating some conflict risk.
Suggestions
Specify the platform or system this skill operates on (e.g., local issue tracker, GitHub, Jira) to reduce overlap with other issue-management 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 multiple trigger scenarios, plus 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 natural phrases a user would type. | 3 / 3 |
Distinctiveness Conflict Risk | While it specifies 'issue management' with CRUD operations, the term 'issues' is somewhat generic and could overlap with GitHub issue skills, bug tracking skills, or project management skills. The 'menu-driven' and 'interactive' qualifiers help but don't fully disambiguate the tool or platform. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
35%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 CLI operations but suffers from significant verbosity. The ASCII art UI mockups, pseudocode implementation patterns, and workflow diagrams consume many tokens without proportional value—Claude can infer UI patterns and routing logic. The CLI command reference is the strongest section, being concrete and specific, but the surrounding content dilutes its effectiveness.
Suggestions
Cut the Implementation Guide section entirely (Entry Point, Main Menu Pattern, Filter Pattern, Edit Pattern)—Claude knows how to parse input, display menus, and route actions. This alone would save ~40% of tokens.
Remove ASCII art UI mockups (filter boxes, issue detail boxes, workflow diagram) and replace with brief text descriptions where needed.
Add explicit validation/confirmation steps for bulk operations (e.g., 'Confirm count of affected issues before executing bulk delete') to address the missing feedback loops for destructive batch operations.
Move the Data Files table and Error Handling table to a separate reference file (e.g., REFERENCE.md) and link to it, keeping SKILL.md focused on the CLI commands and operation flows.
| 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 bloated—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 commands are concrete and specific, which is good. However, the JavaScript code examples are pseudocode-level (e.g., `AskUserQuestion` is not a real function, `Bash()` is not standard), and the edit pattern ends with comments like '// Read → Parse → Update → Write' instead of executable code. The CLI reference section is the most actionable part. | 2 / 3 |
Workflow Clarity | Each operation has a labeled flow with numbered steps, and the issue lifecycle is clearly shown. However, bulk operations (destructive batch deletes, status changes) lack explicit validation/confirmation checkpoints and error recovery loops. The delete flow mentions confirmation but bulk delete has no verification step documented. | 2 / 3 |
Progressive Disclosure | The content is structured with clear sections and headers, but it's monolithic—the Implementation Guide, Data Files, and detailed operation flows could be split into separate reference files. Everything is inline in one large document with no references to external files for detailed content. | 2 / 3 |
Total | 7 / 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
0f8e801
- 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.