openhands/linear-triage
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.
$ install --global
skillsauthnpx skillsauth add openhands/skills linear-triageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 5, 2026, 6:05 AM198.7s3 files scanned
SKILL.md
- name:
- linear-triage
- description:
- >
- - /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:
- Teams/projects — which Linear teams or projects should be triaged (e.g.
Engineering,Support) - Label taxonomy — what labels are used for classification? (e.g.
bug,feature,support,chore) - Priority conventions — how does the team use priority levels? Any mapping rules?
- Auto-apply or suggest — should the automation apply labels/priority/assignee directly, or post a triage comment with suggestions for human approval?
- 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
Read the Automation backend URL and auth from <RUNTIME_SERVICES>:
- Use the Automation backend
url_from_agentasOPENHANDS_HOST - Auth:
X-Session-API-Key: $OPENHANDS_AUTOMATION_API_KEY
Use 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>
}'
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}
Related Skills
openhands/github-pr-reviewer
tools
VerifiedTrustedCommunity
Create an automation that reviews GitHub pull requests when a configurable trigger label is applied. Polls GitHub deterministically, starts one OpenHands review conversation per label event, inspects full repository and PR context, and posts the final review comment back to GitHub.
112SKILL.mdUpdated Jun 5, 2026
openhands/slack-channel-monitor
tools
VerifiedTrustedCommunity
This skill should be used when the user asks to "monitor a Slack channel", "watch Slack for messages", "create a Slack bot that responds to mentions", "set up an OpenHands Slack integration", "trigger OpenHands from Slack", "respond to @openhands in Slack", or "poll Slack channels for a trigger phrase". Guides the user through creating a cron automation that watches up to 10 Slack channels and starts an OpenHands conversation whenever a configurable trigger phrase is detected.
112SKILL.mdUpdated May 23, 2026
openhands/openhands-sdk
tools
VerifiedTrustedCommunity
Reference skill for the OpenHands Software Agent SDK - the Python framework for building AI agents that write software. Use when you need to build agents with the SDK, create custom tools, configure LLMs, manage conversations, delegate to sub-agents, or deploy agents locally or remotely.
112SKILL.mdUpdated Apr 24, 2026
openhands/github-repo-monitor
tools
VerifiedTrustedCommunity
This skill should be used when the user asks to "monitor a GitHub repository", "watch GitHub for issues or PRs", "respond to @OpenHands mentions on GitHub", "set up an OpenHands GitHub integration", "trigger OpenHands from a GitHub comment", or "poll a GitHub repo for a trigger phrase". Guides the user through creating a cron automation that polls a single repository and starts an OpenHands conversation whenever a configurable trigger phrase is detected in an issue or PR comment.
110SKILL.mdUpdated May 23, 2026