CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

linear-triage

Triage Linear issues in a team's Triage state. Categorizes issues as straightforward, needs-discussion, or stale/duplicate. Optionally scopes the straightforward ones with effort estimates via parallel sub-agents, then recommends which to delegate to the Oz Linear agent. Use when the user asks to triage a Linear team's triage inbox.

Quality

91%

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

86%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.

A tight, highly actionable skill body: exact MCP tool calls with parameters, explicit categorization criteria, and a well-gated confirmation step before delegation. The few imperfections are a circular self-reference about parsing oversized results and unspecified details like the team-query value.

Suggestions

Fix the circular reference in the Gotchas: "parse it from the persisted tool-result file (see step 3)" points at step 3, which never describes the parsing — replace with the actual recovery procedure (e.g., which file path and how to extract the issue list from it).

Specify what the `query` argument to `list_teams` should match (team name, key, or slug) so step 1 is fully deterministic.

Add a brief post-delegation verification step (e.g., re-fetch the delegated issues or check the save_issue results) to close the feedback loop on the batch operation.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: every line is either an actionable step with exact tool names and parameters, or a non-obvious gotcha (Oz is an agent not a user, proxy errors at large limits). No padding and no explanation of concepts Claude already knows.

5 / 5

Actionability

Guidance is mostly copy-paste ready — exact tool names (`mcp__claude_ai_Linear__list_issues`), parameters (`limit: 50`, `includeArchived: false`, `delegate: "Oz"`), and a required comment template. Minor gaps remain: "list_teams with a query" doesn't specify what the query matches, and the gotcha "parse it from the persisted tool-result file (see step 3)" is circular since step 3 never explains that parsing.

4 / 5

Workflow Clarity

The 8-step sequence is clear with an explicit validation checkpoint before the destructive batch operation (step 7: "present the user with a summary table... Do not proceed until the user confirms") and an error-recovery path for oversized results. It falls short of a 5 only because there is no post-delegation verification step and the persisted-file recovery is not concretely actionable.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, with no need for external references, and is well organized into two clean sections (Workflow, Gotchas) — meeting the rubric's stated condition for a 5 on simple skills.

5 / 5

Total

18

/

20

Passed

Description

92%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.

A strong description: specific third-person actions, an explicit and natural 'Use when' trigger, and a distinct niche. The only weakness is slightly narrow trigger-term coverage (no synonyms or common variations of 'triage inbox').

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with full coverage of the skill's scope: "Categorizes issues as straightforward, needs-discussion, or stale/duplicate", "scopes the straightforward ones with effort estimates via parallel sub-agents", and "recommends which to delegate to the Oz Linear agent" — all in third-person voice.

5 / 5

Completeness

It explicitly answers both questions: the 'what' (categorize into three named buckets, scope with effort estimates, recommend Oz delegation) and a concrete 'when' clause — "Use when the user asks to triage a Linear team's triage inbox."

5 / 5

Trigger Term Quality

Natural trigger terms are present ("triage", "Linear", "triage inbox", "Use when the user asks to triage a Linear team's triage inbox") but common variations like "Linear issues", "backlog", or "triage queue" are absent, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (Linear's Triage state, Oz agent delegation) with distinct trigger phrases, making conflict with other skills minimal — no other plausible skill would trigger on this wording.

5 / 5

Total

19

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

drew-tessl/repo-schedules-test

Path

plugins/development-guide/skills/linear-triage/SKILL.md

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.