Triage support requests
Sort incoming support requests by urgency and type, draft a reply for each, and flag the ones a person must answer.
In Lobstack: Skills › Library › Add
What your agent will do.
A queue of customer messages — an inbox, a channel, a helpdesk — needs sorting before anyone answers.
- 01
Read every open request, oldest first. Note who, what they need, and how long they have waited.
- 02
Sort each into: broken for them now, billing or account, how-do-I, feature request, other. Urgent means blocked, paying, or waiting over a day.
- 03
For each, draft a reply that answers what was asked, in plain words, with the next step and when they will hear back. Link to docs where they exist.
- 04
Flag for a person, without drafting a promise: refunds, legal, security, angry customers, anything about money moving.
- 05
Post one summary: counts by type, the urgent list, and the drafts.
Drafts only. Sending is the person's call unless they have said otherwise. Never guess at a fix; say what you will check.
The whole SKILL.md: 28 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: support-ticket-triagedescription: "Sort incoming support requests by urgency and type, draft a reply for each, and flag the ones a person must answer."metadata: title: "Triage support requests" category: support tags: [support, email]--- ## When to use this A queue of customer messages -- an inbox, a channel, a helpdesk -- needs sortingbefore anyone answers. ## How 1. Read every open request, oldest first. Note who, what they need, and how long they have waited.2. Sort each into: broken for them now, billing or account, how-do-I, feature request, other. Urgent means blocked, paying, or waiting over a day.3. For each, draft a reply that answers what was asked, in plain words, with the next step and when they will hear back. Link to docs where they exist.4. Flag for a person, without drafting a promise: refunds, legal, security, angry customers, anything about money moving.5. Post one summary: counts by type, the urgent list, and the drafts. Drafts only. Sending is the person's call unless they have said otherwise.Never guess at a fix; say what you will check.
- Support
Customer reply
Draft a reply to a customer that answers what they actually asked, in their register, with the next step clear. Left unsent for review.
SKILL.md · App - Support
FAQ from support questions
Turn repeated support questions into a short FAQ, each answer checked against the product as it is today.
SKILL.md · App - Support
Community replies
Draft replies for a community channel — Discord, Telegram, Slack — that welcome people, answer from the docs, and hand anything about money, bugs or accounts to a person.
SKILL.md · App - Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App - Engineering
Review what a linter cannot
Review a change for what a linter cannot see: whether it is correct, what it breaks elsewhere, and which parallel list it forgot to update.
SKILL.md · App