docs-build

Return only JSON objects, no other text or formatting.

2|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/clawperator/clawperator --skill docs-build-clawperator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-build
Source: https://github.com/clawperator/clawperator/tree/main/.agents/skills/docs-build
Command: npx skills add https://github.com/clawperator/clawperator --skill docs-build-clawperator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Builds and validates the Clawoperator public docs site from authored markdown and code-derived inputs, coordinating deterministic assembly and artifact generation.

Core Features & Use Cases

  • Deterministic docs staging assembly and validation
  • Code-derived page generation and marker expansion
  • llms-full.txt generation for indexing and distribution
  • Clear guidance for authors to separate docs and build logic

Quick Start

Run the docs-build skill to assemble the docs staging, run MkDocs build, and generate the llms-full.txt artifact.

Frequently Asked Questions about docs-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate an MkDocs build from authored markdown and code-derived inputs?

You can automate an MkDocs build by running a deterministic docs pipeline that assembles staging content from authored markdown and code-derived inputs. The process coordinates staging assembly, validates content, and executes the build to produce the final site.

What is llms-full.txt generation and when do I need it for documentation?

llms-full.txt generation creates a consolidated text artifact for indexing and distribution. You need it when your documentation pipeline must expose code-derived and authored content to automated tools, ensuring deterministic artifact generation during the build process.

How do I separate docs authoring logic from build logic in a documentation pipeline?

You separate docs authoring from build logic by using a deterministic assembly process with defined artifact generation hooks. Authors focus on markdown content while scripts handle staging assembly, code-derived page generation, and marker expansion.

Does the docs-build pipeline require PyYAML to run MkDocs builds?

Yes, PyYAML is a required dependency for the pipeline. The build process relies on it to parse and validate configuration during staging assembly and the subsequent MkDocs build execution.

What is the best way to validate documentation staging before generating build artifacts?

The best way to validate staging is through a deterministic assembly process that checks authored markdown and code-derived inputs before running the MkDocs build. This ensures content integrity prior to artifact and llms-full.txt generation.

Can I expand code-derived page markers automatically during a documentation build?

Yes, code-derived page generation and marker expansion are handled automatically during the staging assembly phase. The pipeline applies deterministic rules to expand markers and integrate code-derived content into the final MkDocs build.