CtrlK
BlogDocsLog inGet started
Tessl Logo

triage-github

Triage all open GitHub issues, PRs, and discussions in the current repository by fanning out up to 100 parallel subagents (one per item), then produce a single prioritized report ranking which PRs to review first, which issues to address first, and which discussions need maintainer attention. Use when the user asks to "triage open issues/PRs", "triage discussions", "prioritize the backlog", "what should I review first", "sweep the repo", or any request to bulk-evaluate open GitHub work and recommend an order.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a tightly structured, highly actionable multi-step workflow with strong validation checkpoints appropriate to a 100-agent batch operation. It loses only slightly on conciseness (length and repetition) and progressive disclosure (large inline templates/skeleton that could be externalized).

Suggestions

Move the three per-item prompt templates and the ~80-line report skeleton into separate files under references/ and link them, keeping SKILL.md as a concise overview — this would improve both conciseness and progressive_disclosure.

De-duplicate the repeated 'One JSON object. No commentary.' closeouts and the Notes section, which restates rules already embedded in the procedure, to tighten token efficiency.

Consider extracting the category-aware discussion priority rubric into a reference table so the main body can stay focused on orchestration.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no primers on what a PR or discussion is), but at ~320 lines it carries repeated closeout lines ('One JSON object. No commentary.') and a restated Notes section that could be trimmed, fitting the score-4 'efficient; minor instances of over-explanation' anchor rather than a clean 5.

4 / 5

Actionability

Fully executable throughout — exact `gh` calls with explicit JSON field lists, copy-paste per-item prompt templates with precise single-line JSON return schemas, concrete sort tiebreakers, and the exact `gh gist create` command — matching the score-5 'fully executable; copy-paste ready' anchor.

5 / 5

Workflow Clarity

The batch operation is sequenced into 7 numbered steps with explicit validation checkpoints (auth check that stops on failure, hasDiscussionsEnabled gate, 100-item budget with user confirmation, parse-failure fallback, 'skip deltas rather than guess', 'ask before overwriting', opt-in gating on the one outward action), satisfying the score-5 anchor with feedback loops for a batch operation.

5 / 5

Progressive Disclosure

A single-file skill with no references/scripts/assets bundle and a clean sectioned hierarchy; the full report skeleton (~80 lines) and three large prompt templates are inlined rather than split into reference files, placing it at the score-4 'good structure; most content appropriately placed; minor organization gaps' anchor rather than 5 or below.

4 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is third-person, specific, and comprehensive, naming concrete actions for issues, PRs, and discussions plus a prioritized-report outcome. It pairs a clear 'what' with an explicit 'when' clause listing natural trigger phrases, leaving little ambiguity about when to invoke it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across all three domains — 'triage all open GitHub issues, PRs, and discussions', 'fanning out up to 100 parallel subagents (one per item)', and 'produce a single prioritized report ranking which PRs to review first, which issues to address first, and which discussions need maintainer attention' — comprehensive coverage matching the score-5 anchor.

5 / 5

Completeness

Explicitly answers both 'what' (fan out 100 agents to produce a prioritized ranking report) and 'when' ('Use when the user asks to...') with concrete trigger phrases, matching the score-5 anchor.

5 / 5

Trigger Term Quality

Includes natural phrases a user would actually say — 'triage open issues/PRs', 'triage discussions', 'prioritize the backlog', 'what should I review first', 'sweep the repo', 'bulk-evaluate open GitHub work' — comprehensive synonym coverage matching the score-5 anchor.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — bulk parallel triage of open GitHub work with a prioritized report — with distinctive trigger phrases ('sweep the repo', 'prioritize the backlog') and minimal overlap with single-item review skills, matching the score-5 anchor.

5 / 5

Total

20

/

20

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 11 missing

Warning

Total

15

/

16

Passed

Repository
TanStack/ai
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.