github-triage
Unified GitHub triage for issues AND PRs. 1 item = 1 background task (category: free). Issues: answer questions from codebase, analyze bugs. PRs: review bugfixes, merge safe ones. All parallel, all background. Triggers: 'triage', 'triage issues', 'triage PRs', 'github triage'.
Install with Tessl CLI
npx tessl i github:code-yeongyu/oh-my-openagent --skill github-triage90
Quality
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Quality
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 effectively communicates both capabilities and triggers. It uses third person voice, lists concrete actions for both issues and PRs, and provides explicit trigger terms. The operational details about background tasks and parallelization add useful context for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'answer questions from codebase', 'analyze bugs', 'review bugfixes', 'merge safe ones'. Also specifies operational details like '1 item = 1 background task' and 'All parallel, all background'. | 3 / 3 |
Completeness | Clearly answers both what (triage issues and PRs, answer questions, analyze bugs, review/merge PRs) and when (explicit 'Triggers:' clause with specific keywords). The explicit trigger guidance satisfies the completeness requirement. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger terms users would say: 'triage', 'triage issues', 'triage PRs', 'github triage'. These are practical keywords that match how users would naturally request this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: 'Unified GitHub triage for issues AND PRs' combined with specific triggers like 'github triage' makes it unlikely to conflict with other skills. The combination of GitHub + triage + background task processing is a clear differentiator. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable and well-structured skill for GitHub triage automation with excellent workflow clarity and explicit validation checkpoints. The main weaknesses are verbosity (some redundancy between sections) and the monolithic structure that could benefit from splitting subagent prompts into separate reference files. The skill excels at leaving nothing implicit for the 'free' category subagents.
Suggestions
Extract the 6 subagent prompt templates into a separate PROMPTS.md file and reference them from the main skill to reduce file length
Consolidate the repeated rules (e.g., '[sisyphus-bot] prefix is MANDATORY') into a single 'Universal Rules' section rather than repeating in each prompt template
Remove the XML-style tags (<role>, <fetch>, etc.) as markdown headers already provide sufficient structure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but verbose in places. The XML-style tags (<role>, <fetch>, etc.) add visual noise, and some sections repeat information (e.g., the 'CRITICAL' rules appear in both subagent prompts and the anti-patterns table). However, the verbosity is partially justified by the need for explicit subagent prompts. | 2 / 3 |
Actionability | Highly actionable with executable gh CLI commands, complete subagent prompt templates with exact output formats, and specific step-by-step instructions. The prompts are copy-paste ready and include exact command syntax for every operation. | 3 / 3 |
Workflow Clarity | Excellent workflow structure with 5 clearly numbered phases, explicit validation checkpoints (merge conditions with 6 specific criteria), and feedback loops (poll background_output, stream results as they arrive). The anti-patterns table serves as a validation checklist. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and tables, but it's a monolithic 400+ line file with no references to external documentation. The subagent prompts could be split into separate files, and the anti-patterns/rules could be consolidated into a reference document. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.