1-triage-issues

Triage backlog, scan open issues, rank what to tackle first, or which PRs are production-ready.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/1-triage-issues/SKILL.md

Quality

Content

85%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 body is highly actionable with executable commands, explicit validation checkpoints, and a clear five-step workflow. It is concise and well-structured, with only minor room to externalize long inline reference material.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes competence — concrete gh commands, inline tables, and terse scoring rubrics with no padding or explanations of concepts Claude already knows; only a few sentences (e.g. the contributor-audit prose) could be tightened, keeping it just below 5.	4 / 5
Actionability	It provides fully executable, copy-paste-ready gh/CLI commands with exact JSON fields, grep patterns, and a concrete output template covering common cases, matching the score-5 anchor; no gaps in executable guidance.	5 / 5
Workflow Clarity	A clear five-step sequence (Gather → Packet admission → Score issues → Score PRs → Rank/report) with explicit validation checkpoints ('This step is complete when...', read-only non-negotiables, hard-fail criteria) and feedback guidance; this is a read-only skill so the destructive-cap rule does not apply.	5 / 5
Progressive Disclosure	Well-organized sections with clear headers and inline pointers to sibling skills (/2-repro-issue, /3-verify-pr-fix) and repo docs; however no bundle files exist and several long inline references (scoring rubrics, contributor audit) could live in separate files, so it sits below 5.	4 / 5
	Total	18 / 20 Passed

Description

50%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 states a clear 'what' but omits an explicit 'Use when...' trigger clause, which caps completeness. It is specific enough to be actionable yet lacks comprehensive concrete actions and natural trigger synonyms.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers (e.g. 'Use when prioritizing the issue backlog, deciding which open issues to investigate, or judging if a PR is ready to merge').

List more concrete actions (scan, rank, score severity/reach, audit PR readiness) to lift specificity from 1-2 actions to several.

Include natural trigger synonyms like 'prioritize issues', 'triage bugs', and 'which PR to merge' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Phrases like 'Triage backlog, scan open issues, rank what to tackle first' name the domain and 1-2 concrete actions (scan, rank), but the actions are generic ('rank what to tackle first') and not comprehensive, matching the score-3 anchor; it does not reach 4 because it lacks several specific concrete actions.	3 / 5
Completeness	There is a clear 'what' (triage/scan/rank issues and PRs) but no explicit 'when' / 'Use when...' clause, and the judging guidelines cap completeness at 3 when trigger guidance is missing; it does not drop to 2 because the 'what' is clearly stated.	3 / 5
Trigger Term Quality	Terms like 'backlog', 'open issues', 'PRs', 'production-ready' are relevant, but it misses common natural variations users would say ('prioritize issues', 'triage bugs', 'which PR to merge'); not enough coverage for a 4.	3 / 5
Distinctiveness Conflict Risk	The triage/PR-readiness niche is fairly distinct from generic skills and the named sibling skills (/2-repro-issue, /3-verify-pr-fix) bound it, with only minor overlap risk against general review skills; it is not a 5 because the description itself does not sharply differentiate triggers.	4 / 5
	Total	13 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: stickerdaniel/linkedin-mcp-server
Path: .agents/skills/1-triage-issues/SKILL.md
Commit: f4fc67d

Reviewed: 9 hours ago

Table of Contents

Discovery Implementation Validation

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.