# Knowledge Management Category Structure

> Sub-skill of knowledge-management: Category Structure (+1).

- Skill: `vamseeachanta/knowledge-management-category-structure` (Agent Skill)
- Install (CLI): `npx skillmds@latest add vamseeachanta/knowledge-management-category-structure`
- Raw SKILL.md: https://api.skillmd.com/api/skills/vamseeachanta/knowledge-management-category-structure/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: vamseeachanta (https://skillmd.com/u/vamseeachanta)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/vamseeachanta/knowledge-management-category-structure

---


# Category Structure (+1)

## Category Structure


Organize articles into a hierarchy that matches how customers think:

```
Getting Started
├── Account setup
├── First-time configuration
└── Quick start guides

Features & How-tos
├── [Feature area 1]
├── [Feature area 2]
└── [Feature area 3]

Integrations
├── [Integration 1]
├── [Integration 2]
└── API reference

Troubleshooting
├── Common errors
├── Performance issues
└── Known issues

Billing & Account
├── Plans and pricing
├── Billing questions
└── Account management
```


## Linking Best Practices


- **Link from troubleshooting to how-to**: "For setup instructions, see [How to configure X]"
- **Link from how-to to troubleshooting**: "If you encounter errors, see [Troubleshooting X]"
- **Link from FAQ to detailed articles**: "For a full walkthrough, see [Guide to X]"
- **Link from known issues to workarounds**: Keep the chain from problem to solution short
- **Use relative links** within the KB -- they survive restructuring better than absolute URLs
- **Avoid circular links** -- if A links to B, B shouldn't link back to A unless both are genuinely useful entry points