kb-article
Skill0 starsChanged 36 days agoMITView on GitHub
Turn a resolved or well-understood triage report into a draft knowledge-base article (how-to, troubleshooting, known issue or FAQ). Use after triage when the same question is likely to come up again.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- thensls/nsls-builder-toolkittheir own version, first seen Nov 8, 2026
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- Big-LAORE/Biblioth-que-de-skillstheir own version, first seen Nov 1, 2026
- anthropics/knowledge-work-pluginstheir own version, first seen Oct 13, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- anthropics/knowledge-work-plugins★ 35ksame name
- Big-LAORE/Biblioth-que-de-skills★ 1same name
- nisarth/claude-skills-store★ 1same name
- thensls/nsls-builder-toolkit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- escalationSkill
- known-issue-searchSkill
- log-evidenceSkill
- redactionSkill
- reproduction-stepsSkill
- response-draftingSkill
- support-triageSkill
- ticket-intakeSkill
- triage-reportSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
No customer-specific details are needed to understand it.
- Distinctive: line 16
Do not write one for Suspected root causes, single-customer misconfigurations, or anything involving security details that are not yet …
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
KB Article
Support teams answer the same question many times. When a triage report shows a documented limit, a workaround or a known issue, draft an article so the next customer can self-serve. The draft is for a human to review and publish; this skill never publishes anything.
When to write one
- The root cause is Confirmed by data, or Likely with a working workaround.
- The answer is not already covered by an existing docs page (if it is, suggest a docs link or a docs fix instead).
- No customer-specific details are needed to understand it.
Do not write one for Suspected root causes, single-customer misconfigurations, or anything involving security details that are not yet public.
Pick a type
| Type | Use when | Lead with |
| How-to | The customer wanted to do something supported | The goal, then numbered steps |
| Troubleshooting | A symptom has a few known causes | The symptom in the customer's words, then causes in order of likelihood |
| Known issue | A bug is acknowledged and tracked | Affected versions, workaround, fixed-in version (only if released) |
| FAQ / limit | Behavior is by design | The limit stated plainly, then the alternatives |
Shape
# <Symptom or task, in the words a customer would search for>
**Applies to:** <product area, versions, plans>
**Last reviewed:** <YYYY-MM-DD>
## Summary
<Two sentences: what happens and what to do.>
## Cause
<Plain English. No internal ticket IDs, tool names or private links.>
## Resolution
1. <step>
2. <step>
## Workaround (if no fix yet)
<steps>
## Related
- <public docs links only>Rules
- Same guardrails as customer replies: no internal links, no raw queries, no customer data, no promised dates, no unverified feature claims.
- Title it with the words a customer would search, for example "CSV export stops at 10,000 rows", not "BEACON-097".
- Save drafts under
reports/asYYYYMMDD-HHmmss-<ticket-id>-kb-draft.md. Never write to a docs repo or help center.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.