issue-triage
Triages new GitHub issues — classifies, reproduces bugs, attempts conservative fixes, and comments. Use when a new issue is opened and needs automated triage.
90
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
85%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 well-crafted skill description that clearly articulates specific capabilities and includes explicit trigger guidance. The description uses proper third-person voice and covers the complete triage workflow. Minor improvement could be made by expanding trigger terms to include more natural user language variations.
Suggestions
Add more natural trigger term variations such as 'bug report', 'ticket', 'issue tracker', or 'newly filed issue' to improve discoverability
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'classifies, reproduces bugs, attempts conservative fixes, and comments' - these are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Triages new GitHub issues — classifies, reproduces bugs, attempts conservative fixes, and comments') and when ('Use when a new issue is opened and needs automated triage') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'GitHub issues', 'triage', 'bugs', and 'new issue is opened', but missing common variations like 'issue tracker', 'bug report', 'ticket', or specific issue actions users might mention. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on GitHub issue triage with distinct triggers; the combination of 'new issue opened' and 'automated triage' creates a specific use case unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill with excellent actionability and workflow clarity. It provides concrete, executable commands at every step, clear decision trees for different scenarios, and explicit validation checkpoints. The comment templates are comprehensive but add length that could be externalized.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, assuming Claude's competence with git, GitHub CLI, and Rust tooling. No unnecessary explanations of basic concepts; every section serves a clear purpose. | 3 / 3 |
Actionability | Provides fully executable commands throughout (gh, git, cargo), specific commit message formats, complete PR body templates, and copy-paste ready comment templates for every scenario. | 3 / 3 |
Workflow Clarity | Clear 6-step sequence with explicit validation checkpoints (run test to confirm failure, run full test suite before committing, monitor CI until green). Includes feedback loops for CI failures and clear decision points for when to fix vs. create reproduction-only PR. | 3 / 3 |
Progressive Disclosure | References `/running-in-ci` appropriately, but the comment templates section is quite long and could potentially be split into a separate file. The skill is well-organized but borders on monolithic for the templates portion. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
- Repository
- max-sixty/worktrunk
- Commit
a45fa7f
- 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.