compile-docs
Use when compiling documentation for a CLI tool, API, or other system from its reference material.
What this skill does
Orchestrates a multi-phase pipeline that discovers, inventories, plans, and compiles documentation for a target system using specialized subagents.
## Orchestration Rules
- Never write documentation directly. All documentation authoring is delegated to `doc-author`.
- Delegate research tasks to the microplanner or reference agents as appropriate.
- Keep context lean. Summarize subagent results rather than reproducing their full output.
- Track progress via the master plan. Update step statuses as work is completed, blocked, or in progress.
- Minimize questions and proceed autonomously. Only escalate when a decision cannot be resolved from available context.
## Phase 1: Discover Reference Structure
- Dispatch `reference-scout` with all available info about the target (name, URLs, install location, etc.)
- Use the scouting report to inform Phase 2; do not stop to ask the user
## Phase 2: Build Reference Inventory
- Create a temp directory: `mktemp -d /tmp/compile-docs-XXXXXX`
- Dispatch `reference-explorer` with:
- The scouting report from Phase 1
- Target file: `<tmpdir>/inventory-001.md`
- If the explorer reports `status: partial`:
- Dispatch continuation explorers, each writing the next numbered file (`inventory-002.md`, `inventory-003.md`, etc.)
- Repeat until all explorers report `status: complete`
- Combine all partial inventories into `<tmpdir>/inventory-complete.md`
## Phase 3: Plan Documentation Hierarchy
- Dispatch `doc-planner` with:
- Inventory file: `<tmpdir>/inventory-complete.md`
- Output directory (default `docs/`)
- Target plan file: `<tmpdir>/hierarchy-plan.md`
- Review the returned plan for completeness: every inventory entry must appear in the File Mapping table
## Phase 4: Hand Off to create-master-plan
- Invoke `/create-master-plan` with the following inputs:
- **Reference inventory path:** `<tmpdir>/inventory-complete.md`
- **Hierarchy plan path:** `<tmpdir>/hierarchy-plan.md`
- **Style guide path:** `.claude/skills/compile-docs/style-guide.md`
- **Agent roster:** microplanner (planning), doc-author (writing), doc-editor (review)
- **Step list:** dynamically generated at runtime from the hierarchy plan's File Mapping table
- **One step per inventory entry.** The roadmap must contain exactly as many steps as there are rows in the File Mapping table. Do NOT batch, combine, or group multiple entries into a single step, even when they share an output file. Hundreds of steps is expected and correct for large inventories.
- Penultimate step: editorial review by `doc-editor`, issues written to `<tmpdir>/review-issues.md`
- Final step: `doc-author` fixes based on review issues
- **Autonomous execution guidance:** the user is not a domain expert; minimize questions; continue autonomously when no outstanding questions exist
## Agent Roster
- `reference-scout` -- reconnaissance; maps reference source structure and navigation method
- `reference-explorer` -- systematic enumeration; produces structured inventory files
- `doc-planner` -- documentation architect; designs file hierarchy from inventory
- `doc-author` -- technical writer; produces reference pages from microplans
- `doc-editor` -- senior editor; reviews completed docs for quality and completeness
- `microplanner` -- planning agent; creates per-step microplans for doc-author
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.