Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →decebals/issue-triage
Triage and categorize GitHub issues with priority labels.
Passed 15 of 20 test cases with the skill, and 15 of 20 without it.
2 fixed15 passed either way4 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are setting up an automated cleanup query to find stale open tickets in our GitHub project. What specific threshold of inactivity in days and what required label filter should be specified for auto-closing stale tickets?
| Checked | Without skill | With skill |
|---|---|---|
| Sets the inactivity threshold to 90 days. | Missed | Passed |
| Filters for issues tagged with the needs-more-info label. | Missed | Passed |
The instructions your model reads when the skill loads.
Efficiently triage GitHub issues for Java projects with categorization and prioritization.
Recommended: GitHub MCP server configured for optimal token usage
claude mcp add github --transport http \
https://api.githubcopilot.com/mcp/
Alternative: Use gh CLI (less token-efficient)
With GitHub MCP (recommended):
Tool: list_issues
Parameters: {
"state": "open",
"sort": "updated",
"per_page": 10
}
With gh CLI:
gh issue list --state open --limit 10 --json number,title,labels,body,url
test cases passed, vs 15 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.