Stats
Actions
Tags
From support
Write a knowledge base article from a resolved support issue, common question, or how-to topic.
How this skill is triggered — by the user, by Claude, or both
Slash command
/support:write-kb-articleThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Write a knowledge base article for $ARGUMENTS using the mandatory structure and rules below.
Write a knowledge base article for $ARGUMENTS using the mandatory structure and rules below.
Before writing, gather all necessary information:
Grep and GlobUse this exact structure. Every section is mandatory.
Write the title as the question the user would type into a search bar. Use their vocabulary, not internal terminology.
1-2 sentences that directly answer the question. This is for users who scan. It must be self-contained — a user who reads only this sentence should get the core answer.
List what the user needs before starting. Be explicit:
If there are no prerequisites, state "No special requirements."
Numbered steps. Each step MUST follow this format:
N. **[Action verb] [what to do]**
[Exactly where to click/type/navigate — be precise about UI element names, menu paths, button labels]
Expected result: [What the user should see after completing this step]
Rules for steps:
List the most common problems a user might encounter while following the steps. Format each as:
**Problem**: [What the user sees or experiences]
**Cause**: [Why this happens]
**Solution**: [How to fix it]
Include at minimum:
If there are no known issues, state: "No common issues reported. If you encounter a problem, contact support with the error message and the step where it occurred."
Link 3-5 related articles. Group them by relationship:
If related articles don't exist yet, list the titles that should be written and note them as "[To be created]".
Before finalising, verify the article against every rule:
| Rule | Check |
|---|---|
| One article, one question | Does this article answer exactly one question completely? If it answers two, split it. |
| User vocabulary | Are all terms the ones a user would use? Replace any internal jargon. |
| Scannable | Can a user find their answer without reading the whole article? (short answer, headings, bold key terms) |
| Testable | Could someone follow these steps on the live product right now and succeed? |
| Version-aware | If the answer is version-specific, is the version stated clearly at the top? |
| No assumptions | Does every step specify exactly where to go and what to click? No "navigate to the relevant section." |
| Error-path covered | Are the most common failure modes documented in Troubleshooting? |
At the end of the article, include:
---
Last verified: [today's date]
Product area: [feature area]
Applies to: [plan tiers, or "All plans"]
Tags: [3-5 searchable tags]
---
KB articles are living documents. Include this maintenance note at the bottom:
/support:triage-tickets — KB articles reduce ticket volume. When a triaged topic has high recurrence, write an article./support:feedback-synthesis — feedback synthesis identifies the topics that most need KB coverage.Searches MemPalace before answering questions about past work, people, projects, or prior decisions. Returns verbatim stored content instead of guessing from model memory.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Implements vector databases with Pinecone, Weaviate, Qdrant, Milvus, pgvector for semantic search, RAG, recommendations, and similarity systems. Optimizes embeddings, indexing, and hybrid search.
npx claudepluginhub hpsgd/turtlestack --plugin support