/docs-management

name: docs-management
description: Single source of truth and librarian for ALL Claude official documentation. Manages local documentation storage, scraping, discovery, and resolution. Use when finding, locating, searching, or resolving Claude documentation; discovering docs by keywords, category, tags, or natural language queries; scraping from sitemaps or docs maps; managing index metadata (keywords, tags, aliases); or rebuilding index from filesystem. Run scripts to scrape, find, and resolve documentation. Handles doc_id resolution, keyword search, natural language queries, category/tag filtering, alias resolution, sitemap.xml parsing, docs map processing, markdown subsection extraction for internal use, hash-based drift detection, and comprehensive index maintenance.
allowed-tools: Read, Glob, Grep, Bash, Skill

Claude Docs Management

🚨🚨🚨 MANDATORY: Hybrid Parallel Pattern 🚨🚨🚨

> **STOP - Before using this skill for ANY Claude Code documentation query:** > > **IF YOU ARE THE MAIN AGENT**, you MUST invoke BOTH sources **in the same message**: > > 1. **This skill** (`docs-management`) - local cache, token-efficient > 2. **`claude-code-guide` subagent** - live web search > > ```text > [Skill tool: docs-management] > "Find documentation about {topic}" > > [Task tool: claude-code-guide] (SAME MESSAGE - USE THIS EXACT PROMPT) > "First WebFetch https://code.claude.com/docs/en/claude_code_docs_map.md to find > relevant doc pages about {topic}. Then WebFetch those specific pages. Use WebSearch > only if needed for additional context. Do NOT use Skill tool (not available). > Return key findings with source URLs." > ``` > > **⚠️ CRITICAL:** claude-code-guide does NOT have Skill tool access. Always prompt it > to use **WebSearch/WebFetch explicitly**. If you see "No such tool: Skill" error, > you prompted it wrong. > > **This is AUTOMATIC. Do NOT wait for user to ask for it.** > > **IF YOU ARE A SUBAGENT**: Note in your response that main agent should also query `claude-code-guide`.

---

🚨 CRITICAL: Path Doubling Prevention - MANDATORY

**ABSOLUTE PROHIBITION: NEVER use `cd` with `&&` in PowerShell when running scripts from this skill.**

**The Problem:** If your current working directory is already inside the skill directory, using relative paths causes PowerShell to resolve paths relative to the current directory instead of the repository root, resulting in path doubling.

**REQUIRED Solutions (choose one):**

1. **✅ ALWAYS use helper scripts** (recommended - they handle path resolution automatically) 2. **✅ Use absolute path resolution** (if not using helper script) 3. **✅ Use separate commands** (never `cd` with `&&`)

**NEVER DO THIS:**

• ❌ Chain `cd` with `&&`: `cd <relative-path> && python <script>` causes path doubling
• ❌ Assume current directory
• ❌ Use relative paths when current dir is inside skill directory

**For all scripts:** Always run from repository root using relative paths, OR use helper scripts that handle path resolution automatically.

🚨 CRITICAL: Large File Handling - MANDATORY SCRIPT USAGE

⚠️ ABSOLUTE PROHIBITION: NEVER use read_file tool on the index.yaml file

The file exceeds 25,000 tokens and will ALWAYS fail. You MUST use scripts.

**✅ REQUIRED: ALWAYS use manage_index.py scripts for ANY index.yaml access:**

python scripts/management/manage_index.py count
python scripts/management/manage_index.py list
python scripts/management/manage_index.py get <doc_id>
python scripts/management/manage_index.py verify

All scripts automatically handle large files via `index_manager.py`.

Available Slash Commands

This skill provides three slash commands for common workflows:

• **`/claude-ecosystem:scrape-docs`** - Scrape all configured Claude documentation sources, then refresh index and validate
• **`/claude-ecosystem:refresh-docs`** - Refresh the local index and metadata without scraping from remote sources
• **`/claude-ecosystem:validate-docs`** - Validate the index and references for consistency and drift without scraping

Overview

This skill provides automation tooling for documentation management. It manages:

• **Canonical storage** (encapsulated in skill) - Single source of truth for official docs
• **Subsection extraction** - Token-optimized extracts for skills (60-90% savings)
• **Drift detection** - Hash-based validation against upstream sources
• **Sync workflows** - Quarterly maintenance automation
• **Documentation discovery** - Keyword-based search and doc_id resolution
• **Index management** - Metadata, keywords, tags, aliases for resilient references

**Core value:** Prevents link rot, enables offline access, optimizes token costs, automates maintenance, and provides resilient doc_id-based references.

When to Use This Skill

This skill should be used when:

• **Scraping documentation** - Fetching docs from sitemaps or docs maps
• **Finding documentation** - Searching for docs by keywords, category, or natural language
• **Resolving doc references** - Converting doc_id to file paths
• **Managing index metadata** - Adding keywords, tags, aliases, updating metadata
• **Rebuilding index** - Regenerating index from filesystem (handles renames/moves)

Hybrid Parallel Documentation Strategy

> **CRITICAL: This section is the authoritative source for Claude Code documentation access patterns.**

Architecture Constraint

**Skills cannot spawn subagents.** Only the main conversation thread can use the Task tool.

This means:

• When **main agent** loads this skill → Main agent must also invoke `claude-code-guide` in parallel
• When **subagent** loads this skill → Subagent should note in response that main agent should invoke `claude-code-guide` for live coverage
• When **command** invokes this skill → Same as main agent (commands run in main context)

Caller-Aware Guidance

**If you are the main agent:**

• You MUST invoke both this skill AND `claude-code-guide` subagent in the SAME message
• This is th