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.
In Lobstack: Skills › Library › Add
What your agent will do.
A community channel is busy and questions wait hours for an answer, or new members arrive and nobody says hello.
- 01
Read the thread and the last day of the channel, so you do not answer what someone already did.
- 02
Answer only from the docs, the changelog and pinned messages, and link the page you used. Where they do not answer it, say a person will.
- 03
Welcome new members by name with one useful link, not a wall of rules.
- 04
Hand to a person, without answering, anything about billing, refunds, account access, a security report or a bug that needs a repro.
- 05
Keep the channel's tone: short, friendly, no marketing.
Draft only unless the person has said otherwise. Never promise a date, a feature or credit.
The whole SKILL.md: 27 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: community-reply-draftdescription: "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."metadata: title: "Community replies" category: support tags: [support, community]--- ## When to use this A community channel is busy and questions wait hours for an answer, or newmembers arrive and nobody says hello. ## How 1. Read the thread and the last day of the channel, so you do not answer what someone already did.2. Answer only from the docs, the changelog and pinned messages, and link the page you used. Where they do not answer it, say a person will.3. Welcome new members by name with one useful link, not a wall of rules.4. Hand to a person, without answering, anything about billing, refunds, account access, a security report or a bug that needs a repro.5. Keep the channel's tone: short, friendly, no marketing. Draft only unless the person has said otherwise. Never promise a date, afeature or credit.
- 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
Triage support requests
Sort incoming support requests by urgency and type, draft a reply for each, and flag the ones a person must answer.
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 - 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