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.
91%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
mcp__claude_ai_Linear__list_teams with a query.mcp__claude_ai_Linear__list_issue_statuses for the team; pick the entry with type === "triage".mcp__claude_ai_Linear__list_issues with team, state (the triage state ID), limit: 50, includeArchived: false. Paginate if hasNextPage.Agent calls with subagent_type: Explore (read-only). Split issues into groups and assign each sub-agent a group. Each sub-agent should:
mcp__claude_ai_Linear__save_issue with id and delegate: "Oz", in parallel.delegate field, not assignee. Confirm with the user before delegating.list_issues with large limits can fail with a proxy error. Use limit: 50; if the result is too large to read inline, parse it from the persisted tool-result file (see step 3)./linear-triage"drew-tessl/repo-schedules-test
82bbe83
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.