community-automations/linear-support-triage

Sales & CRM

PublicClaude subagent

Linear Support Triage

Bugs get reported in Slack and then vanish. Someone types out the problem, a few people react, and the thread scrolls away before anyone files it. The same issue gets reported again next week because no record was ever made.

sonnet3 daysSlackLinearOpenAI
ClaudeClaude
ROI for
README.md

Why this subagent

Bugs get reported in Slack and then vanish. Someone types out the problem, a few people react, and the thread scrolls away before anyone files it. The same issue gets reported again next week because no record was ever made.

This agent reads issues reported in your support channel and files a clean Linear ticket in the right queue, with severity and repro steps pulled from the message. It replies in the thread with the link, so the reporter can track it. Nothing depends on someone remembering to copy it over by hand.

How it runs

    • Read

      Used at step 01 to kick off the pipeline.

    • Write

      Used at step 01 to kick off the pipeline.

    • WebFetch

      Used at step 01 to kick off the pipeline.

    • WebSearch

      Used at step 01 to kick off the pipeline.

Sample output

json
// Sample output
// (generated when the pipeline finishes)

From a Slack-reported issue, return a Linear issue with title, team, priority, and a description built from the reported details.

Unlock the rest

The full agent definition, install snippet, and starter task are gated for community members.

Members get the full `.md` agent file, the npm / pnpm install one-liners, a starter prompt that we've tuned against real runs, and the open-source repo when this automation ships there. One email, magic link, done.