olore-docs-packager-1.0.0

Package local documentation into an installable olore skill with TOC.md, SKILL.md, and INDEX.md.

67|4|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/olorehq/olore --skill olore-docs-packager-1-0-0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: olore-docs-packager-1.0.0
Source: https://github.com/olorehq/olore/tree/main/vault/packages/docs-packager/1.0.0
Command: npx skills add https://github.com/olorehq/olore --skill olore-docs-packager-1-0-0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Packaging local documentation into a reusable, offline-accessible olore skill that any agent can load.

Core Features & Use Cases

  • Package a project's docs into a ready-to-use skill with TOC.md, SKILL.md, and INDEX.md for consistent agent access.
  • Generate a structured Table of Contents and searchable index to speed up lookups.
  • Build an installable skill package that works offline and is versioned for reproducibility.

Quick Start

Run the packaging workflow to generate an olore skill from your local docs.

Frequently Asked Questions about olore-docs-packager-1.0.0

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

FAQPage Schema
How do I package local documentation for offline agent access?

You package local documentation by running the workflow to generate an installable skill containing TOC.md, SKILL.md, and INDEX.md, ensuring consistent offline access for agents.

What is the best way to create a searchable index from existing project docs?

Creating a searchable index from project docs is done by packaging them into an olore skill, which automatically generates a structured Table of Contents and INDEX.md for quick lookups.

Can I create a reusable docs package that works consistently across different agents?

Yes, you can build an installable docs package that provides a deterministic structure, ensuring any agent loads and queries your documentation consistently across environments.

How do I generate a Table of Contents for local markdown documentation?

Generating a Table of Contents for local documentation happens during the packaging process, which automatically creates a TOC.md file to speed up navigation and lookups.

Does packaging documentation into a skill require any external dependencies?

Packaging documentation into a skill requires no external dependencies, allowing you to build an offline, versioned package directly from your local project files.