build-artifacts

Generate SKILL.md and TOC.md from existing documentation packages.

67|4|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/olorehq/olore --skill build-artifacts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-artifacts
Source: https://github.com/olorehq/olore/tree/main/.claude/skills/build-artifacts
Command: npx skills add https://github.com/olorehq/olore --skill build-artifacts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the generation of essential documentation artifacts for a documentation package, specifically SKILL.md and TOC.md, reducing manual steps and ensuring consistency across deployments.

Core Features & Use Cases

  • Generate SKILL.md and TOC.md from an existing documentation package to standardize skill discovery and navigation.
  • Ensure metadata alignment between package contents and the generated artifacts for reliable agent loading.
  • Use Case: When you have a vault/packages/{config_name}/{version} package ready, run the tool to produce the required SKILL.md and TOC.md files for agent ingestion.

Quick Start

Run /build-artifacts prisma@latest to generate artifacts.

Frequently Asked Questions about build-artifacts

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

FAQPage Schema
How do I generate SKILL.md and TOC.md files for a documentation package?▼

To generate SKILL.md and TOC.md artifacts, run the build-artifacts command targeting an existing documentation package located in vault/packages/{config_name}/{version}/ to automatically render and create the required files.

What is the best way to automate documentation artifact generation for agent ingestion?▼

Automating documentation artifact generation ensures metadata alignment between package contents and the generated SKILL.md and TOC.md files, reducing manual steps and standardizing skill discovery for reliable agent loading.

Do I need an existing documentation package structure to generate TOC.md files?▼

Yes, you need an existing documentation package located in vault/packages/{config_name}/{version}/contents, because the generation process reads from this directory and applies templates from vault/packages/docs-packager to render the artifacts.

Can I use build-artifacts to create a table of contents for any vault package?▼

You can use build-artifacts to create a TOC.md and SKILL.md for any documentation package structured under vault/packages/{config_name}/{version}/, provided the contents directory exists and you have read access to it.

How does the template rendering process work for generating SKILL.md files?▼

The template rendering process uses templates from vault/packages/docs-packager, reads the contents of a specific documentation package, and outputs standardized SKILL.md and TOC.md files directly into the package version directory.