AC github-triage
Review GitHub repositories, group issues and pull requests by urgency, and take safe triage actions (add labels, comment, propose closure) after confirmation. Use this skill when users want help reviewing, sorting, and acting on GitHub issues and PRs without manually navigating between pages — groups items by urgency, proposes next actions, and applies safe triage operations after approval.
Review GitHub repositories, group issues and pull requests by urgency, and take safe triage actions (add labels, comment, propose closure) after confirmation.
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (github-triage) differs from the folder (github-triage-workflow)
- 55Failures and branches. 1 branches
- 85Steps. 64 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 2432 tokens
- 100Progress reporting. Reports progress
- low 13 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 393: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 64 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.