skills/linear-triage/SKILL.md
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.
npx skillsauth add openhands/skills linear-triageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Set up an automation that triages new Linear issues — classifying, labeling, and suggesting owners automatically.
Ask the user for:
Engineering, Support)bug, feature, support, chore)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.
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).
Construct a prompt that includes:
Read the Automation backend URL and auth from <RUNTIME_SERVICES>:
url_from_agent as OPENHANDS_HOSTX-Session-API-Key: $OPENHANDS_AUTOMATION_API_KEYUse the prompt preset endpoint:
curl -s -X POST "${OPENHANDS_HOST}/api/automation/v1/preset/prompt" \
-H "X-Session-API-Key: $OPENHANDS_AUTOMATION_API_KEY" \
-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} / $OPENHANDS_AUTOMATION_API_KEY with $env:OPENHANDS_HOST / $env:OPENHANDS_AUTOMATION_API_KEY if running it natively.
Tell the user:
✅ Linear Issue Triage is running!
- Automation ID:
{id}- Teams:
{team list}- Mode:
{auto-apply or suggest}- Trigger:
{trigger description}
tools
Iterate on a GitHub pull request — drive it through CI, code review, and QA until it is merge-ready. Poll verification layers with `gh` CLI, diagnose and fix CI failures, address review feedback, retry flaky checks, push fixes, and repeat. The agent is the orchestration loop.
development
Guides technical explanations toward flowing, direct, conversational prose. This skill should be used for engineering chat, design discussion, architecture analysis, code-review explanations, and technical recommendations that should be concise without becoming fragmented or vague.
tools
This skill should be used when the user asks to "set up a Jira automation to create pull requests", "poll Jira for create-pr issues", "automatically create GitHub PRs from Jira tickets", "deploy a Jira issue-to-PR automation", "create a Jira to GitHub PR workflow", or mentions automating GitHub PR creation from a Jira label. Deploys a cron-based OpenHands automation that watches a Jira Cloud project for issues labeled with a configurable label (default: "create-pr") and spawns an agent conversation to create a GitHub pull request for each new issue found. The target GitHub repository is read from the body of the Jira ticket - no repo parameter is required at deploy time.
tools
This skill should be used when the user asks to "create an automation", "schedule a task", "set up a cron job", "webhook integration", "event-triggered automation", or mentions automations, scheduled tasks, cron scheduling, or webhook events in OpenHands Cloud.