CtrlK
BlogDocsLog inGet started
Tessl Logo

github-project-triage

GitHub issue/PR triage: queues, CI, blockers, risk, proof, next actions.

59

Quality

67%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/github-project-triage/SKILL.md
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 rich, highly actionable maintainer-triage skill with strong executable commands and well-sequenced validation-gated workflows. Its main weaknesses are length/repitition and a monolithic structure that keeps detail inline instead of delegating it to reference files.

Suggestions

Move the Fast Queue Map, Detail Pass, Triage Heuristics, and Output Shape blocks into separate reference files (e.g. references/queue-maps.md, references/output-shapes.md) and link to them one level deep, leaving SKILL.md as a leaner overview.

Tighten the repeated scope/autonomy-bounds statements (currently restated in Scope Rule, Autonomous Work Mode, and the closing line) into a single canonical scope statement.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and stays action-dense, but at ~312 lines it restates scope/autonomy rules and repeats some heuristics that could be tightened.

2 / 3

Actionability

It provides copy-paste-ready, fully executable commands — `repobar_cmd` invocations, `gh issue/pr list/view/diff` with exact JSON fields, the git status gate, and jq summaries — with no pseudocode gaps.

3 / 3

Workflow Clarity

Multi-step flows are explicitly sequenced with validation checkpoints: the Local Repo Gate (branch=main, pull succeeds, clean worktree or stop) and the numbered 1–7 Autonomous Work Mode with verify → Codex review → CI-green feedback loops.

3 / 3

Progressive Disclosure

Sections are well-organized with clear headers and the one bundle (`scripts/github-activity.sh`) is real and clearly signaled with a fallback path, but most detail (queue maps, heuristics, output shapes) is inline rather than split into separate reference files.

2 / 3

Total

10

/

12

Passed

Description

57%

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 specific to a clear GitHub triage niche with good distinctiveness, but it reads as a terse keyword list of topics rather than actions and lacks an explicit "Use when..." trigger clause. It is solid but not exemplary.

Suggestions

Add an explicit "Use when..." clause naming the trigger, e.g. "Use when the user says triage, or asks to review open GitHub issues/PRs for a repo."

Reframe the colon-separated topics as concrete actions, e.g. "Queue, classify, and assess GitHub issues/PRs — CI state, blockers, risk, proof, and next actions."

DimensionReasoningScore

Specificity

It names the domain and several facets ("queues, CI, blockers, risk, proof, next actions"), but these are noun-topics rather than concrete action verbs, falling short of listing specific actions like the score-3 anchor.

2 / 3

Completeness

It clearly answers the *what* (GitHub issue/PR triage covering queues/CI/blockers/risk/proof/next actions) but includes no "Use when..." clause, so per the guideline completeness is capped at 2.

2 / 3

Trigger Term Quality

"triage" is a strong natural trigger and "GitHub issue/PR", "CI", "blockers" are relevant, but as a terse colon-separated keyword list it misses common phrasing variations a user might say.

2 / 3

Distinctiveness Conflict Risk

"GitHub issue/PR triage" is a clear, specific niche with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

9

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
steipete/agent-scripts
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.