Borrowing it
Nothing to install: this file belongs to joa23/linear-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/joa23/linear-cli/main/.claude/skills/triage/SKILL.mdgit clone --depth 1 https://github.com/joa23/linear-cliWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/joa23/linear-cli/triage)<a href="https://agentmods.dev/skills/joa23/linear-cli/triage"><img src="https://agentmods.dev/badge/skills/joa23/linear-cli/triage/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/joa23/linear-cli/triage"><img src="https://agentmods.dev/badge/skills/joa23/linear-cli/triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00058 | $0.00676 |
| Opus 5.5 | $0.00023 | $0.00270 |
| Sonnet 5.5 | $0.00012 | $0.00135 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
triage scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Skill - Backlog Analysis
Process
1. Setup
linear init # if .linear.yaml doesn't exist
2. Fetch the backlog
linear issues list --state Backlog --format full --limit 100
Verify: confirm issues are returned before proceeding. If empty, check team context with linear init.
3. Analyze dependencies
linear deps --team ENG
4. Filter by priority and labels
# Urgent (P1)
linear issues list --state Backlog --priority 1 --format full
# High priority (P2)
linear issues list --state Backlog --priority 2 --format full
# Customer issues
linear issues list --labels customer --format full
# Bugs in backlog
linear issues list --state Backlog --labels bug --format full
# Combined filters
linear issues list --state Backlog --priority 1 --labels customer --format full
5. Identify issues
Flag issues matching these patterns:
| Pattern | Criteria | Action |
|---|---|---|
| Stale | No updates 30+ days | Ping assignee or close |
| Very stale | No updates 60+ days | Close with comment |
| Blocked | Dependencies unresolved | Escalate blocker |
| Orphaned | No assignee + no activity | Assign or close |
| Priority mismatch | P1/P2 but blocked | Escalate the blocker first |
Verify: cross-check flagged issues against dependency graph from step 3. Blocked issues with completed blockers should be unblocked immediately:
linear issues update ENG-123 --priority 2
linear issues comment ENG-123 --body "Triaged: Needs unblocking before sprint"
6. Generate report
Use this output format:
BACKLOG TRIAGE: Team ENG
════════════════════════════════════════
URGENT ATTENTION (3)
────────────────────────────────────────
ENG-101 [Stale 45d] Login bug - P1 but no activity
ENG-102 [Blocked] Payment flow - blocked by ENG-99
ENG-103 [Orphaned] API refactor - no owner
RECOMMENDED ACTIONS
────────────────────────────────────────
1. Unblock ENG-102: Complete ENG-99 or remove dependency
2. Assign ENG-103: Needs owner or close if abandoned
3. Update ENG-101: Stale P1 needs attention
HEALTH SUMMARY
────────────────────────────────────────
Total issues: 45
Blocked: 8 (17%)
Stale: 12 (26%)
Healthy: 25 (55%)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 105 lines · 58 tokens per session scan A b0fab3e22748
triage is a skill published in the GitHub repository joa23/linear-cli (145 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 676 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…