Agent skill

Build Docs

Build documentation packages from configs. An agent skill from olorehq/olore.

MITAuto-check passedDatabases

Install Build Docs

skills CLI

$ npx skills add olorehq/olore --skill build-docs -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install olorehq/olore build-docs --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/olorehq/olore.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/build-docs .claude/skills/build-docs && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "build-docs" agent skill from https://github.com/olorehq/olore/tree/main/.claude/skills/build-docs into .claude/skills/build-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-docs", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/olorehq/olore/tree/main/.claude/skills/build-docs

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add olorehq/olore --skill build-docs -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install olorehq/olore build-docs --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/olorehq/olore.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/build-docs .agents/skills/build-docs && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "build-docs" agent skill from https://github.com/olorehq/olore/tree/main/.claude/skills/build-docs into .agents/skills/build-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-docs", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add olorehq/olore --skill build-docs -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install olorehq/olore build-docs --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/olorehq/olore.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/build-docs .cursor/skills/build-docs && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "build-docs" agent skill from https://github.com/olorehq/olore/tree/main/.claude/skills/build-docs into .cursor/skills/build-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-docs", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/olorehq/olore.git --path .claude/skills/build-docs

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add olorehq/olore --skill build-docs -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install olorehq/olore build-docs --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/olorehq/olore.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/build-docs .gemini/skills/build-docs && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "build-docs" agent skill from https://github.com/olorehq/olore/tree/main/.claude/skills/build-docs into .gemini/skills/build-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-docs", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install olorehq/olore build-docs

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add olorehq/olore --skill build-docs -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/olorehq/olore.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/build-docs .github/skills/build-docs && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "build-docs" agent skill from https://github.com/olorehq/olore/tree/main/.claude/skills/build-docs into .github/skills/build-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-docs", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add olorehq/olore --skill build-docs -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install olorehq/olore build-docs --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/olorehq/olore.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/build-docs .opencode/skills/build-docs && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "build-docs" agent skill from https://github.com/olorehq/olore/tree/main/.claude/skills/build-docs into .opencode/skills/build-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-docs", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: build-docs
GitHub stars: 104
Token cost: ~1k tokens
SKILL.md length: 263 words
Files: 5 (incl. scripts)
Skills in repo: 29
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Build documentation packages from configs. An agent skill from olorehq/olore.

Works in 5 steps: Parse Arguments → Discover Work → Report Plan and Confirm → …
Updating local documentation
SKILL.md covers Usage, Workflow, Config Structure and Package Structure (after build), plus 4 more sections
Runs Shell scripts from its folder; calls jq

What it does

Build Docs is an agent skill from olorehq/olore. Build documentation packages from configs. Downloads docs, filters with AI, generates SKILL.md. Use when setting up or updating local documentation.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts (for example `adding-docs.md`, `conventions.md` and `scripts/github.sh`).

It sits in Databases. It works with Prisma. The repository describes itself as: Turn library docs into local Agent Skills. The licence is MIT.

When your agent uses it

Updating local documentation

Example prompts

“/build-docs”

Requirements

A Bash shell

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Parse Arguments
Discover Work
Report Plan and Confirm
Spawn Subagents (PARALLEL)
Summary

What it can do on your machine

Read from SKILL.md and the folder at commit 430d86c. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 2 files in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
- jq
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Build Docs loads about 1k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 263 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~40
When it runs · the whole SKILL.md, loaded when a task matches: ~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from olorehq/olore at commit 430d86c, republished under its MIT licence (© olorehq). 263 words, ~1,041 tokens.

Download SKILL.mdSave it as .claude/skills/build-docs/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.

name: build-docs
description: Build documentation packages from configs. Downloads docs, filters with AI, generates SKILL.md. Use when setting up or updating local documentation.

Build Docs

Build documentation packages from configs in vault/configs/.

Usage

/build-docs                      # All configs, all versions
/build-docs prisma               # All versions for prisma config
/build-docs prisma@latest        # Specific version only
/build-docs prisma zod           # Multiple configs
/build-docs prisma --force       # Re-download even if exists

Workflow

Phase 1: Parse Arguments

Parse $ARGUMENTS:

No args → Process all configs in vault/configs/*.json
name without @ → All versions for that config
name@version → Specific version only
--force flag → Re-download even if exists

Phase 2: Discover Work

For each config, list versions and check what needs building:

bash

# List configs
ls vault/configs/*.json

# Get versions from a config
jq -r '.versions | keys[]' vault/configs/{name}.json

# Check if version is built (olore-lock.json exists)
test -f vault/packages/{name}/{version}/olore-lock.json

Built = vault/packages/{name}/{version}/olore-lock.json exists Work = versions without olore-lock.json (unless --force)

Phase 3: Report Plan and Confirm

Show what will be built and ask for confirmation:

Build plan:
  prisma@latest - not built
  zod@latest - exists (skip)
  nextjs@16.1.3 - not built

Will build 2 packages. Proceed?

Phase 4: Spawn Subagents (PARALLEL)

CRITICAL: Spawn ALL subagents in a SINGLE message for parallel execution.

For each package that needs building, spawn a package-builder subagent:

Use package-builder agent: prisma@latest
Use package-builder agent: nextjs@16.1.3

If --force flag was set, pass it to subagents:

Use package-builder agent: prisma@latest --force

Example with 3 packages: In ONE message, spawn THREE subagents:

package-builder: prisma@latest
package-builder: zod@latest
package-builder: nextjs@16.1.3

All subagents run in parallel. Each handles:

Download docs from source
Filter files (if needed)
Generate TOC.md
Generate SKILL.md

Phase 5: Summary

Collect results from all subagents and report:

Build complete:
  ✅ prisma@latest - 312 files (126 filtered), tier 3
  ✅ zod@latest - 17 files, tier 1
  ⏭️  nextjs@16.1.3 - skipped (exists)

Install with: olore install ./vault/packages/prisma/latest

Config Structure

Config file: vault/configs/prisma.json

json

{
  "name": "prisma",
  "_source": { "type": "github", "repo": "prisma/docs", "path": "content" },
  "versions": {
    "latest": { "ref": "main" }
  }
}

Package Structure (after build)

vault/packages/{name}/{version}/
├── olore-lock.json    # Build metadata
├── SKILL.md           # Skill definition (generated)
├── TOC.md             # Table of contents (generated)
└── contents/
    └── *.md           # Documentation files

After Build

For development (changes immediately visible):

olore link ./vault/packages/prisma/latest

For testing final package (copies to ~/.olore):

olore install ./vault/packages/prisma/latest

After install/link, skills are available as /olore-<name>-<version> (e.g., /olore-prisma-latest).

Standalone Skills

Individual phases can be run independently without the full pipeline:

/download-docs prisma@latest         # Download + filter only
/build-artifacts prisma@latest       # Regenerate SKILL.md + TOC.md only

Use --force on any standalone skill to regenerate even if output exists.

Dependencies:

/download-docs has no dependencies (runs first)
/build-artifacts requires contents/ from /download-docs

Reference

Adding new documentation - Config file format, GitHub/URL sources
Conventions - Config vs lock files, naming rules
Templates: vault/packages/docs-packager/1.0.0/templates/ (single source of truth)

Requirements

jq - JSON parsing
git - GitHub cloning
curl - URL downloads

Files

SKILL.md and 4 other files (scripts) in .claude/skills/build-docs of olorehq/olore.

SKILL.md
adding-docs.md
conventions.md
scripts/github.sh
scripts/url.sh

Open the folder on GitHubat commit 430d86c

Compare with similar skills

Build Docs next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Build Docs compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Build Docs this skillolorehq/olore	104	—	~1k	Automated safety check: Pass	MIT	today
Content Create Hero Imageprisma/web	1.1k	—	~6.9k	Automated safety check: Pass	None	today
Datamodellmnimbalyst/nimbalyst	1.9k	—	~713	Automated safety check: Pass	MIT	today
Prisma Client APIcurvenote/curvenote	169	2 repos	~1.6k	Automated safety check: Pass	MIT	10 days ago
Docs Writerprisma/web	1.1k	—	~5.2k	Automated safety check: Notes	None	today
Prismablencorp/claude-code-kit	106	—	~2.7k	Automated safety check: Pass	MIT	10 mo ago

Similar skills

Content Create Hero Image
prisma/web
Official
A skill your agent uses when the operator wants a hero or meta image for a Prisma blog post; asks to create or generate a blog hero, cover, social card, Open Graph, or YouTube image; mentions cover…
1.1k GitHub stars~6.9k tokensUpdated today
DatabasesAuto-check passed
Datamodellm
nimbalyst/nimbalyst
Create visual data models for database schemas using Nimbalyst's DataModelLM editor.
1.9k GitHub stars~713 tokensUpdated today
DatabasesAuto-check passed
Prisma Client API
curvenote/curvenote
Prisma Client API reference covering model queries, filters, operators, and client methods.
169 GitHub starsUsed in 2 repos~1.6k tokens
DatabasesAuto-check passed
Docs Writer
prisma/web
Official
A skill your agent uses when writing, rewriting, or improving technical docs (quickstarts, how-tos, tutorials, concept pages, or API references).
1.1k GitHub stars~5.2k tokensUpdated today
DatabasesAuto-check: notes
Prisma
blencorp/claude-code-kit
Prisma ORM patterns including Prisma Client usage, queries, mutations, relations, transactions, and schema management.
106 GitHub stars~2.7k tokensUpdated 10 mo ago
DatabasesAuto-check passed
Prisma Expert
davila7/claude-code-templates
Prisma ORM expert for schema design, migrations, query optimization, relations modeling, and database operations.
32k GitHub starsUsed in 7 repos~2.6k tokens
DatabasesAuto-check passed

Questions about Build Docs

What does Build Docs do?

Build documentation packages from configs. An agent skill from olorehq/olore. Build Docs is an agent skill from olorehq/olore. Build documentation packages from configs.

When should I use Build Docs?

Build Docs fits situations like: updating local documentation.

How do I install Build Docs in Claude Code?

Run `npx skills add olorehq/olore --skill build-docs -a claude-code`. Or copy the skill folder (.claude/skills/build-docs in olorehq/olore) into .claude/skills/build-docs in your project. Claude Code loads it when a task matches its description.

How do I install Build Docs in Codex?

Run `npx skills add olorehq/olore --skill build-docs -a codex`. Or copy the skill folder (.claude/skills/build-docs in olorehq/olore) into .agents/skills/build-docs in your project. Codex loads it when a task matches its description.

Can I use Build Docs in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add olorehq/olore --skill build-docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/build-docs, .gemini/skills/build-docs, .github/skills/build-docs and .opencode/skills/build-docs in your project.

What does Build Docs need to run?

Going by SKILL.md and its folder, Build Docs needs a shell for the scripts in its folder and the command-line tools its instructions call (jq). Our summary lists: A Bash shell.

Does Build Docs access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Build Docs safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Build Docs use?

Build Docs is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Build Docs use?

About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Build Docs?

Skills that share tags, products or a category with Build Docs: Content Create Hero Image (prisma/web, 1.1k stars), Datamodellm (nimbalyst/nimbalyst, 1.9k stars), Prisma Client API (curvenote/curvenote, 169 stars) and Docs Writer (prisma/web, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Build Docs?

olorehq (a GitHub organization) maintains it in olorehq/olore, which has 104 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 7, 2026.

Source: olorehq/olore on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Build Docs

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Build Docs

Usage

Workflow

Phase 1: Parse Arguments

Phase 2: Discover Work

Phase 3: Report Plan and Confirm

Phase 4: Spawn Subagents (PARALLEL)

Phase 5: Summary

Config Structure

Package Structure (after build)

After Build

Standalone Skills

Reference

Requirements

Files

Compare with similar skills

Similar skills

More from olorehq/olore

Related

Questions about Build Docs