knowledge-management-category-structure
Sub-skill of knowledge-management: Category Structure (+1).
Best use case
knowledge-management-category-structure is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of knowledge-management: Category Structure (+1).
Teams using knowledge-management-category-structure should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/category-structure/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How knowledge-management-category-structure Compares
| Feature / Agent | knowledge-management-category-structure | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of knowledge-management: Category Structure (+1).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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
Related Skills
domain-knowledge-sweep
Systematic multi-source research of an engineering domain. Spawns parent issue → 6 research subissues (Standards, Academic, Industry, LinkedIn-marketing, Code-audit, Synthesis) → gap implementation subissues. Replaces LinkedIn-only extraction with defensible comprehensive sourcing.
public-knowledge-graph-governance
Maintain public-safe knowledge graph artifacts for llm-wiki and similar markdown knowledge bases. Use when changing graph generators, validators, schema docs, weekly freshness checks, or public/private source-scope boundaries.
workspace-knowledge-doc-contracts
Class-level workspace knowledge, LLM-wiki, repo mission contracts, stale doc references, semantic taxonomy, and knowledge-source reconnaissance.
repo-structure
Canonical source layout, test mirroring, root cleanliness, gitignore, docs classification, and committed artifact rules for all workspace-hub tier-1 repos. Consult before creating directories or files in any submodule.
github-issue-structure-for-personal-finance-tracking
Pattern for organizing financial analysis work across multiple repos (data/config vs. logic separation)
cron-job-management
Patterns for creating, testing, debugging, and maintaining cron-driven automation in workspace-hub, including log strategy, failure analysis, and safe git-aware job design.
github-repo-management
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
knowledge-pipeline
Workflow for maintaining workspace-hub knowledge and learning pipelines across scripts/knowledge, scripts/learning, and docs/superpowers, including indexing, archive synthesis, issue updates, and pipeline troubleshooting.
knowledge-base-builder
Build searchable knowledge bases from document collections (PDFs, Word, text files). Use for creating technical libraries, standards repositories, research databases, or any large document collection requiring full-text search.
data-management
Comprehensive DataFrame loading, filtering, transformation, and data pipeline management from Excel, CSV, and multiple sources with YAML-driven configuration.
knowledge-source-recon
Reconnaissance pattern to inventory all knowledge sources across the workspace-hub ecosystem's existing intelligence infrastructure. Maps raw sources for LLM Wiki ingestion planning. Leverages pre-built registries and indexes rather than re-scanning directories.
task-management
Simple task management using a shared TASKS.md file for tracking commitments and action items.