Journey Docs

Organization

butterbase-ai

journey-docs

Use as the docs-priming stage of the Butterbase journey, immediately after journey-preflight and before the first build stage. Reads the plan to discover which capabilities the app uses, calls butterbase_docs once per relevant topic, and caches a summary the build stages can re-read.

Overview

Publisher	butterbase-ai
Repository	`butterbase-skills`
Skill name	`journey-docs`
Stars	535
Forks	42
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

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.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by butterbase-ai on GitHub. Read the source before you install it.

Installation

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

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/journey-docs
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.

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/butterbase-ai/butterbase-skills.git /tmp/butterbase-skills
mkdir -p .claude/skills
cp -r /tmp/butterbase-skills/skills/journey-docs .claude/skills/journey-docs

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Journey Docs 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 Journey Docs 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 Journey Docs 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.

Journey Docs Gate

A short, mechanical priming step. The goal is that every downstream stage starts with the relevant docs already in the conversation, so the model doesn't invent API shapes.

When to use

Invoke automatically after journey-preflight returns. Also invoke standalone (/butterbase-skills:journey-docs) any time the user changes the plan or you realize a stage is using a capability you haven't refreshed this session.

Procedure

Read the plan. Open docs/butterbase/02-plan.md. Identify every Butterbase capability in use (Tables → schema; RLS → auth; Auth → auth; Storage → storage; Functions → functions; AI → ai; RAG → rag; Realtime → realtime; Durable → functions; Frontend → frontend; Integrations → integrations; Substrate → substrate; Payments → billing).
Call butterbase_docs per topic. For each unique topic from step 1, call butterbase_docs with that topic argument. Skip duplicates.

Write the cache file. Create docs/butterbase/03b-docs-cache.md with this structure:

markdown
---
primed_at: <ISO timestamp>
topics: [<comma-separated list>]
---

# Docs Cache

## <topic-1>
<one-paragraph summary of what the MCP doc says — key endpoints, common patterns, gotchas>
URL: https://docs.butterbase.ai/<area>

## <topic-2>
...

Update 00-state.md. Tick the docs row.
Return. One-line summary: "Primed docs for: schema, auth, storage, functions. Cache at docs/butterbase/03b-docs-cache.md."

Anti-patterns

❌ Calling butterbase_docs with topic: "all". Burns context. Call once per relevant topic instead.
❌ Skipping the cache file. Other stages re-read it; in-memory only doesn't survive context compression.
❌ Calling for topics not in the plan. We're priming, not exhaustive.

Frequently asked questions

What does the Journey Docs AI skill do?

Why use Journey Docs on TypingMind?

Because you install it once and use it with any model. Journey Docs 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 Journey Docs in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/journey-docs. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Journey Docs?

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 Journey Docs?

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

Is the Journey Docs AI skill free?

Yes. It is published on GitHub by butterbase-ai 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

Solid

openclaw

OrganizationPopular

Write, port, review, or test Solid 2 UI in OpenClaw (Control UI, plugin views, Canvas hosts), including state ownership, Lit interop during the migration, native overlays, testing, performance, and…

Agent Transcript

Requested GitHub PR/issue agent transcripts: redact, trim, preview, and insert safely.

Auto Qa

Run OpenClaw-wide autonomous QA and live/stress campaigns across independent subsystem lanes, with verified fixes and a resumable evidence report.

Autoreview

Structured code review when explicitly requested, preferring OpenAI/Codex before Claude.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Journey Docs Gate

When to use

Procedure

Anti-patterns

Frequently asked questions

Related AI Skills

Set up your own AI workspace now