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.

72

Quality

88%

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

77%

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

A highly actionable, well-sequenced skill with strong validation checkpoints for a batch multi-agent operation. Its main weakness is progressive disclosure: a monolithic single file with large inline templates and report skeleton that would benefit from reference-file extraction, plus minor verbosity in the report skeleton.

Suggestions

Move the three per-item prompt templates (PR/issue/discussion) and the report skeleton into reference files under references/ (e.g. PROMPT_TEMPLATES.md, REPORT_TEMPLATE.md), keeping SKILL.md an overview that links to them one level deep — this lifts progressive_disclosure toward 3 and trims the inline token budget.

Tighten the report skeleton by collapsing the repeated P0–P3 subsection stubs into a single documented format string, and remove the repeated 'One JSON object. No commentary.' boilerplate by stating the output contract once up front.

Pull the snapshot/delta mechanics in step 4c into a short reference (e.g. DELTAS.md) so the core procedure stays scannable while the streak-propagation and edge-case rules remain available for the run that needs them.

DimensionReasoningScore

Conciseness

The ~320-line body is mostly efficient and free of concept-padding, but the full report skeleton, three large inline prompt templates, and repeated boilerplate ('One JSON object. No commentary.') could be tightened or externalized, fitting 'mostly efficient but could be tightened' rather than the lean score-3 anchor.

2 / 3

Actionability

Provides copy-paste-ready gh CLI calls with complete JSON field lists, an executable GraphQL query, exact per-item prompt templates with JSON output schemas, and a gist-publish command — fully executable rather than pseudocode.

3 / 3

Workflow Clarity

A numbered 1–7 procedure with explicit validation checkpoints (auth status, hasDiscussionsEnabled, >100 budget handling, agent parse-failure recovery, ask-before-overwrite, prior-snapshot parse handling) and error feedback loops (gist scope error → gh auth refresh), satisfying the batch-operation feedback-loop requirement that would otherwise cap at 2.

3 / 3

Progressive Disclosure

The skill ships no bundle files and keeps everything inline in one ~320-line SKILL.md; the three long prompt templates and report skeleton are content that could be split into reference files, matching 'content that should be separate is inline' rather than the one-level-deep score-3 anchor, though sections are well organized so it is not a score-1 wall of text.

2 / 3

Total

10

/

12

Passed

Description

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.

A strong, third-person description that states concrete capabilities and pairs them with an explicit, natural-language trigger clause. It cleanly satisfies the what/when/distinctiveness requirements with no fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — triage open issues/PRs/discussions, fan out up to 100 parallel subagents, and produce a single prioritized report ranking PRs/issues/discussions — matching the 'lists multiple specific concrete actions' anchor rather than the single-action score-2 example.

3 / 3

Completeness

Explicitly answers both what (parallel triage + prioritized report) and when via a 'Use when the user asks to...' clause with concrete triggers, matching the score-3 anchor and exceeding the score-2 'when only implied' case.

3 / 3

Trigger Term Quality

Surfaces natural phrases a user would actually say ('triage open issues/PRs', 'prioritize the backlog', 'what should I review first', 'sweep the repo'), giving good coverage rather than the partial set at score 2.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear GitHub-repo triage niche with distinctive trigger phrases, making overlap with unrelated skills unlikely; not generic like the score-1/2 examples.

3 / 3

Total

12

/

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.

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.