Olore Docs Packager 1.0.0 logo

Olore Docs Packager 1.0.0

Organization
olorehq
olore-docs-packager-1.0.0

Package local documentation into an olore skill. Use when the user wants to create a documentation package from their local files, or asks about olore init or building docs.

Overview

Publisherolorehq
Repositoryolore
Skill nameolore-docs-packager-1.0.0
Stars
103
Forks
6
Bundled files
13
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 13 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by olorehq on GitHub. Read the source before you install it.

Installation

Install the Olore Docs Packager 1.0.0 AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/olorehq/olore.git /tmp/olore
mkdir -p .claude/skills
cp -r /tmp/olore/vault/packages/docs-packager/1.0.0 .claude/skills/olore-docs-packager-1.0.0
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Olore Docs Packager 1.0.0 in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Olore Docs Packager 1.0.0 on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Olore Docs Packager 1.0.0 is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Package Local Documentation

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

Quick Start

If you don't have olore.config.json yet, run:

bash
olore init

This creates olore.config.json and a docs/ folder with a sample file.

Usage

/olore-docs-packager-1.0.0                        # Use olore.config.json in cwd
/olore-docs-packager-1.0.0 ./custom-config.json   # Use specific config

Workflow

Step 1: Load and Validate Config

Parse $ARGUMENTS to find config file (default: olore.config.json in cwd).

bash
cat {config_path}

Required fields: name, version, description, contentPath

See contents/getting-started.md for config format.

Step 2: Copy Documentation Files

Run the copy script:

bash
uv run scripts/copy-docs.py {config_path}

This copies files matching extensions, applies excludes, and outputs JSON with file count and size.

Step 3: Determine Tier

Run the tier script:

bash
uv run scripts/determine-tier.py {output_path}/contents
TierCriteria
1< 30 files AND < 500KB
230-100 files OR 500KB-2MB
3> 100 files OR > 2MB

Step 4: Generate TOC.md

Read the appropriate template and generate TOC.md:

Write to {output_path}/TOC.md

Step 5: Generate SKILL.md

Read the appropriate template and generate SKILL.md:

IMPORTANT: The name field MUST be olore-{name}-{version} to match the installed folder.

Write to {output_path}/SKILL.md

Step 5.5: Generate INDEX.md

Read the appropriate index template based on tier:

Write to {output_path}/INDEX.md

Format: Each content line is keyword1,keyword2|contents/path/to/file.ext

Keywords should be actual API names, method names, config keys extracted from the file contents.

Step 6: Generate olore-lock.json

Create {output_path}/olore-lock.json:

json
{
  "name": "{name}",
  "version": "{version}",
  "source": {
    "type": "local",
    "contentPath": "{original contentPath}"
  },
  "builtAt": "{ISO timestamp}",
  "files": {file_count}
}

Step 7: Report Summary

Package built successfully:

  Name: olore-{name}-{version}
  Files: {file_count}
  Tier: {tier}
  Output: {output_path}

Install with:
  olore install {output_path}

Config Reference

FieldRequiredDefaultDescription
nameYes-Package name (prefixed with olore-)
versionYes-Version string
descriptionYes-One-line description
contentPathYes-Path to docs (relative to config)
outputPathNo./olore-packageOutput directory
extensionsNo[".md", ".mdx"]File extensions
excludeNo[]Glob patterns to exclude

Requirements

  • uv - Python package manager (handles Python version automatically)

Install uv: curl -LsSf https://astral.sh/uv/install.sh | sh

Example

See contents/getting-started.md for a complete walkthrough.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Olore Docs Packager 1.0.0 AI skill do?

Package local documentation into an olore skill. Use when the user wants to create a documentation package from their local files, or asks about olore init or building docs.

Why use Olore Docs Packager 1.0.0 on TypingMind?

Because you install it once and use it with any model. Olore Docs Packager 1.0.0 is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Olore Docs Packager 1.0.0 in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/olorehq/olore/tree/main/vault/packages/docs-packager/1.0.0. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Olore Docs Packager 1.0.0?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Olore Docs Packager 1.0.0?

As many as you like. As long as a model supports skills, you can use Olore Docs Packager 1.0.0 with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Olore Docs Packager 1.0.0 AI skill free?

Yes. It is published on GitHub by olorehq under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇