FAQ from support questions
Turn repeated support questions into a short FAQ, each answer checked against the product as it is today.
In Lobstack: Skills › Library › Add
What your agent will do.
The same questions keep arriving, and there is no page to point people to, or the page that exists has drifted from the product.
- 01
Collect the questions from the inbox, the support channel and search_history. Group the ones that ask the same thing in other words.
- 02
Keep the groups with at least three askers. Rank by how often.
- 03
For each, write the question in the customer's words and an answer under 80 words. Check the answer against the product and the docs, and link the source. Mark anything you could not confirm.
- 04
Note the questions that point at a product problem rather than a missing answer — those belong to whoever owns the product.
- 05
Post it as a document, ready to publish, with the count behind each entry.
An FAQ answer that is wrong costs more than none: leave out what you could not 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: faq-from-ticketsdescription: "Turn repeated support questions into a short FAQ, each answer checked against the product as it is today."metadata: title: "FAQ from support questions" category: support tags: [support, docs]--- ## When to use this The same questions keep arriving, and there is no page to point people to, orthe page that exists has drifted from the product. ## How 1. Collect the questions from the inbox, the support channel and search_history. Group the ones that ask the same thing in other words.2. Keep the groups with at least three askers. Rank by how often.3. For each, write the question in the customer's words and an answer under 80 words. Check the answer against the product and the docs, and link the source. Mark anything you could not confirm.4. Note the questions that point at a product problem rather than a missing answer -- those belong to whoever owns the product.5. Post it as a document, ready to publish, with the count behind each entry. An FAQ answer that is wrong costs more than none: leave out what you couldnot 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
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
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