Skip to main content

linear-triage

Create an automation that triages new Linear issues. Inspects the issue title, description, team, customer, priority, and recent related issues via Linear MCP. Suggests labels, priority, likely owner, duplicates, and posts a clarifying comment.

Source facts

Repository
OpenHands/extensions
Last source activity
October 2, 2026 at 03:19
Detected SKILL.md language
English
Stars
157
Forks
102

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer
6 files

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
linear-triage
description
Create an automation that triages new Linear issues. Inspects the issue title, description, team, customer, priority, and recent related issues via Linear MCP. Suggests labels, priority, likely owner, duplicates, and posts a clarifying comment.
triggers
["/linear-triage:setup"]
# Linear Issue Triage Automation Set up an automation that triages new Linear issues — classifying, labeling, and suggesting owners automatically. --- ## Prerequisites ### Required integration - **Linear MCP** must be installed in Settings → MCP. ### Information to collect Ask the user for: 1. **Teams/projects** — which Linear teams or projects should be triaged (e.g. `Engineering`, `Support`) 2. **Label taxonomy** — what labels are used for classification? (e.g. `bug`, `feature`, `support`, `chore`) 3. **Priority conventions** — how does the team use priority levels? Any mapping rules? 4. **Auto-apply or suggest** — should the automation apply labels/priority/assignee directly, or post a triage comment with suggestions for human approval? 5. **Duplicate detection** — should it search for and flag potential duplicate issues? --- ## Setup Workflow ### Step 1 — Verify Linear MCP access Confirm the Linear MCP integration is working: ``` Use the Linear MCP to list recent issues for one of the target teams. ``` If it fails, tell the user to install the Linear MCP integration first. ### Step 2 — Determine trigger type **Event-based (recommended if publicly reachable):** Check `<RUNTIME_SERVICES>` for deployment reachability. If public, recommend an event trigger on Linear `Issue` create events. **Cron-based (local/private deployments):** Poll for recently created issues on a schedule (e.g. every 5 minutes). ### Step 3 — Build the triage prompt Construct a prompt that includes: - Target teams/projects - Label taxonomy and classification rules - Priority mapping conventions - Whether to auto-apply or suggest - Duplicate detection preference ### Step 4 — Create the automation Set `OPENHANDS_HOST` and `AUTH_HEADER` for the request below: - **OpenHands Cloud or Enterprise** - a `<HOST>` value is in your system prompt: use it as `OPENHANDS_HOST`, with `AUTH_HEADER="Authorization: Bearer $OPENHANDS_API_KEY"` - **Local Agent Canvas** - an **Automation backend** is listed in `<RUNTIME_SERVICES>`: use its `url_from_agent` as `OPENHANDS_HOST`, with `AUTH_HEADER="X-Session-API-Key: $OPENHANDS_AUTOMATION_API_KEY"` Use the **prompt preset** endpoint: ```bash curl -s -X POST "${OPENHANDS_HOST}/api/automation/v1/preset/prompt" \ -H "$AUTH_HEADER" \ -H "Content-Type: application/json" \ -d '{ "name": "Linear Issue Triage", "prompt": "<constructed triage prompt>", "trigger": <trigger config from step 2> }' ``` PowerShell note: use `curl.exe` for this exact flag syntax, and replace `${OPENHANDS_HOST}` / `$AUTH_HEADER` with `$env:OPENHANDS_HOST` / `$env:AUTH_HEADER` if running it natively. ### Step 5 — Confirm Tell the user: > ✅ **Linear Issue Triage** is running! > > - Automation ID: `{id}` > - Teams: `{team list}` > - Mode: `{auto-apply or suggest}` > - Trigger: `{trigger description}`
View on GitHub