build-docs

Name: build-docs
Availability: InStock
Author: olorehq

Package documentation from configs into installable skills with metadata.

67|4|Updated Jan 21, 2026

Search Tags:#automation #workflow #documentation #config #metadata #docs-packaging

Ready to run

npx skills add https://github.com/olorehq/olore --skill build-docs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: build-docs
Source: https://github.com/olorehq/olore/tree/main/.claude/skills/build-docs
Command: npx skills add https://github.com/olorehq/olore --skill build-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build Docs packages documentation automatically from configs in vault/configs and generate SKILL.md and TOC.md for each version to ensure consistent, offline-ready agent documentation.

Core Features & Use Cases

Config-driven packaging from vault/configs to vault/packages with automatic SKILL.md and TOC.md generation.
Per-version handling, including path overrides and selective file inclusion.
Use case: maintain up-to-date local docs for Claude Code across multiple agents without manual edits.

Quick Start

Invoke the tool to package all configurations into ready-to-install skills.

Frequently Asked Questions about build-docs

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

FAQPage Schema

How do I automate documentation packaging from configs for multiple versions?▼

Documentation packaging from configs reads vault/configs to generate installable skills with SKILL.md and TOC.md for each version. It ensures per-version source tracking and only includes configured file types.

What is config-driven documentation packaging and when do I need it?▼

Config-driven documentation packaging automatically builds offline-ready docs from configuration files into vault/packages. You need it when maintaining consistent local documentation across multiple agents or versions without manual edits.

Can I use config-driven doc packaging in CI pipelines for batch builds?▼

Config-driven doc packaging applies to CI pipelines for batch builds across many docs versions. It automatically generates build metadata in olore-lock.json to track per-version sources during automated runs.

How do I generate SKILL.md and TOC.md for each version in a multi-config repository?▼

Generating SKILL.md and TOC.md for each version in a multi-config repository requires invoking the packaging tool to read configurations and output ready-to-install skills with automatic table of contents files.

What are the limitations of config-driven documentation packaging?▼

Config-driven documentation packaging is limited to processing files from vault/configs and only includes configured file types. It does not package arbitrary unconfigured files or generate documentation without existing config definitions.