# Support Kb Note

> Writes a short knowledge-base note after a support fix. Use when the user resolved a bug, updated a workaround, or asks to document a fix, KB article, or handoff so the team does not rediscover the same issue.

- Skill: `kelvint-cli/support-kb-note` (Agent Skill)
- Install (CLI): `npx skillmds@latest add kelvint-cli/support-kb-note`
- Raw SKILL.md: https://api.skillmd.com/api/skills/kelvint-cli/support-kb-note/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: kelvint-cli (https://skillmd.com/u/kelvint-cli)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/kelvint-cli/support-kb-note

---


# Support knowledge-base note

Write a note a teammate can follow on the next ticket. Keep it short. Do not invent a root cause.

## Template

```markdown
# [Short title]

Symptom: what the user saw.
Who is affected: role, app, or device class. Skip names.
Cause: what you confirmed. Say "unknown" if it is still unknown.
Fix: the steps that worked, in order.
When to escalate: the exact condition that means engineering is needed.
```

## Rules

- Prefer the user's words for the symptom.
- If the user applied a support-side fix, document that and the KB update.
- If engineering was required, document who tested the fix and what "good" looked like.
- No internal hostnames, ticket IDs, or company product codenames unless the user included them and asked to keep them.