github-bug-report-triage
Triage GitHub bug reports for actionability. Use when evaluating whether a bug issue has sufficient detail and identifying missing information from the reporter.
Install with Tessl CLI
npx tessl i github:warpdotdev/oz-skills --skill github-bug-report-triage88
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
75%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 solid description with clear 'what' and 'when' clauses that establish a distinct niche for bug report triage. The main weaknesses are moderate specificity in listing concrete actions and limited trigger term coverage that could miss natural user phrasings.
Suggestions
Add more specific concrete actions like 'checks for reproduction steps, validates environment details, categorizes severity levels'
Expand trigger terms to include variations like 'issue triage', 'incomplete bug report', 'reproduction steps', 'bug template validation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (GitHub bug reports) and some actions (triage, evaluating, identifying missing information), but doesn't list comprehensive concrete actions like categorizing severity, checking reproducibility steps, or validating environment details. | 2 / 3 |
Completeness | Clearly answers both what ('Triage GitHub bug reports for actionability') and when ('Use when evaluating whether a bug issue has sufficient detail and identifying missing information from the reporter') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'bug reports', 'bug issue', 'missing information', but misses common variations users might say such as 'issue triage', 'bug validation', 'incomplete bug', 'reproduction steps', or 'bug template'. | 2 / 3 |
Distinctiveness Conflict Risk | Has a clear niche focused specifically on GitHub bug report triage and actionability assessment, which is distinct from general GitHub skills, code review skills, or generic issue management. | 3 / 3 |
Total | 10 / 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 well-crafted skill that provides clear, actionable guidance for triaging GitHub bug reports. The workflow is logical with explicit decision criteria, and the four examples effectively demonstrate the evaluation process across different scenarios. The content is appropriately concise while being comprehensive enough to handle edge cases.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows (like what GitHub issues are). Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete evaluation criteria, specific file paths to check for templates, clear decision framework (ready vs needs info), and four detailed examples showing exact evaluation patterns with real markdown issue content. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence (locate template → evaluate → determine → provide feedback) with explicit decision points. The 'Be reasonable' section provides appropriate judgment guidelines, and the examples demonstrate the complete evaluation workflow. | 3 / 3 |
Progressive Disclosure | References an external file (references/ISSUE_TEMPLATE.md) appropriately, but the examples section is quite long and could potentially be split into a separate EXAMPLES.md file. The structure is good but the skill is on the longer side for inline content. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
93%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 15 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
Total | 15 / 16 Passed | |
- 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.