Agent skill

Journey Substrate

by butterbase-ai in butterbase-ai/butterbase-skills

Use as the optional substrate-linking stage of the Butterbase journey, after deploy and before submit.

MITAuto-check passedAgent Workflows

Install Journey Substrate

skills CLI
$ npx skills add butterbase-ai/butterbase-skills --skill journey-substrate -a claude-code

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

GitHub CLI
$ gh skill install butterbase-ai/butterbase-skills journey-substrate --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/butterbase-ai/butterbase-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/journey-substrate .claude/skills/journey-substrate && 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/

Facts

Skill name
journey-substrate
GitHub stars
534
Token cost
~741 tokens
SKILL.md length
305 words
Files
1
Skills in repo
39
Repo updated
First seen
Licence
MIT

At a glance

Use as the optional substrate-linking stage of the Butterbase journey, after deploy and before submit.

  • Works in 6 steps: Refresh docs. Call butterbase_docs with… → Confirm. Ask the user → On skip: mark the row - [x] substrate… → …
  • Agent Workflows work in your project
  • SKILL.md covers When to use, Procedure and Anti-patterns
  • Reaches docs.butterbase.ai

What it does

Journey Substrate is an agent skill from butterbase-ai/butterbase-skills. Use as the optional substrate-linking stage of the Butterbase journey, after deploy and before submit. Asks whether to connect the deployed app to the owner's substrate (so functions get ctx.substrate). Skipped by default in hackathon mode.

Its SKILL.md is about 740 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. The repository describes itself as: Plugin for Butterbase.ai. The licence is MIT.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/journey-substrate”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Refresh docs. Call butterbase_docs with topic: "substrate". If the plan mentions AI memory / agent state / cross-session knowledge, also…
  2. Confirm. Ask the user
  3. On skip: mark the row - [x] substrate (skipped — no agent memory needed) in docs/butterbase/00-state.md. Write…
  4. On yes
  5. Write artifact. docs/butterbase/04b-substrate.md
  6. Update state. Tick the substrate row in 00-state.md.

What it can do on your machine

Read from SKILL.md and the folder at commit aa8ae69. 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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • docs.butterbase.ai

    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

Journey Substrate loads about 741 tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 305 words of instructions outside code blocks.

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

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from butterbase-ai/butterbase-skills at commit aa8ae69, republished under its MIT licence (© butterbase-ai). 305 words, ~741 tokens.

Download SKILL.mdSave it as .claude/skills/journey-substrate/SKILL.md (or your agent's skills folder).
name
journey-substrate
description
Use as the optional substrate-linking stage of the Butterbase journey, after deploy and before submit. Asks whether to connect the deployed app to the owner's substrate (so functions get ctx.substrate). Skipped by default in hackathon mode.

Journey Substrate Stage (optional)

Connect the deployed app to the owner's substrate so functions get ctx.substrate injected at cold start. Skip if the user has no AI-agent / memory use case.

When to use

Invoke automatically when the journey orchestrator's cursor reaches substrate. The row is optional in the checklist; skip silently if the user declines.

Procedure

  1. Refresh docs. Call butterbase_docs with topic: "substrate". If the plan mentions AI memory / agent state / cross-session knowledge, also WebFetch https://docs.butterbase.ai/substrate. Skip if docs/butterbase/03b-docs-cache.md already covers substrate.

  2. Confirm. Ask the user:

    "Connect <app_id> to your substrate? This lets the app's functions read/write your agent memory via ctx.substrate. You can disable later. (yes / skip)"

    Default: skip.

  3. On skip: mark the row - [x] substrate (skipped — no agent memory needed) in docs/butterbase/00-state.md. Write docs/butterbase/04b-substrate.md with one line: Skipped on <date>. Return.

  4. On yes: a. If platform_users.substrate_provisioned_at is NULL for the caller, call POST /v1/me/substrate/provision first (or invoke whatever MCP wrapper exists — check butterbase_docs topic substrate). b. Link the app. Use whichever surface you have:

    • MCP: manage_app with { action: "link_substrate", app_id: "<app_id>" }.
    • CLI: butterbase apps link-substrate <app_id>.
    • REST (curl): POST /v1/me/apps/<app_id>/substrate-link with empty body and Authorization: Bearer <bb_sk_*> for the app owner. The route enforces caller == app owner and sets apps.substrate_user_id to the caller's id. c. Verify: manage_app with { action: "get_config", app_id: "<app_id>" } and assert substrate_user_id is non-null. d. Smoke: invoke any HTTP function the app already has and check ctx.substrate is defined (if the function logs it). If no function exists yet, skip the smoke and note in the artifact.
  5. Write artifact. docs/butterbase/04b-substrate.md:

    markdown
    ---
    linked_at: <ISO>
    app_id: <id>
    substrate_user_id: <id>
    ---
    
    # Substrate Linkage
    
    - App linked at <ISO>
    - Substrate user ID: <id>
    - Smoke: <pass / skipped — no function yet>
  6. Update state. Tick the substrate row in 00-state.md.

Anti-patterns

  • ❌ Auto-linking without asking. Substrate is a privacy-sensitive surface.
  • ❌ Linking before the app has any function deployed. Wait until journey-functions has run.
  • ❌ Forgetting to handle the "substrate not yet provisioned" case. Lazy provisioning is by design.

© butterbase-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/journey-substrate of butterbase-ai/butterbase-skills.

Open the folder on GitHubat commit aa8ae69

Compare with similar skills

Journey Substrate 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.

Journey Substrate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Journey Substrate this skillbutterbase-ai/butterbase-skills534—~741Automated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79689 repos~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    796 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

More from butterbase-ai/butterbase-skills

All 39 skills in this repo
  • AI

    butterbase-ai/butterbase-skills

    A skill your agent uses when calling the app's AI gateway from agent tools — chat completions, embeddings, listing models, configuring defaults or BYOK, reading token/cost usage

    534 GitHub stars~1.1k tokensUpdated 5 days ago
    Auto-check passed
  • Auth Setup

    butterbase-ai/butterbase-skills

    A skill your agent uses when configuring OAuth providers (Google/GitHub/Apple/X/etc.), setting up post-login auth hooks, tuning JWT lifetimes, or generating service API keys

    534 GitHub stars~2.2k tokensUpdated 5 days ago
    Auto-check passed
  • Build App

    butterbase-ai/butterbase-skills

    A skill your agent uses when building a new Butterbase app from scratch, creating a full-stack application, or when the user asks to set up a complete backend with database, auth, and deployment

    534 GitHub stars~4.9k tokensUpdated 5 days ago
    Auto-check passed
  • Contributing

    butterbase-ai/butterbase-skills

    A skill your agent uses when contributing to the Butterbase codebase, adding new MCP tools, creating API routes, writing migrations, or understanding the monorepo architecture

    534 GitHub stars~1.5k tokensUpdated 5 days ago
    Auto-check passed
  • Debug Rls

    butterbase-ai/butterbase-skills

    A skill your agent uses when users report access denied errors, see wrong data, RLS policies are not working, or when troubleshooting Row-Level Security issues in Butterbase

    534 GitHub stars~3.5k tokensUpdated 5 days ago
    Auto-check passed
  • Deploy Frontend

    butterbase-ai/butterbase-skills

    A skill your agent uses when deploying a frontend (React, Next.js, or static HTML) to a live URL on Butterbase, or when troubleshooting deployment issues like MIME type errors or blank pages

    534 GitHub stars~2.8k tokensUpdated 5 days ago
    Auto-check passed

Categories

Questions about Journey Substrate

What does Journey Substrate do?

Use as the optional substrate-linking stage of the Butterbase journey, after deploy and before submit. Journey Substrate is an agent skill from butterbase-ai/butterbase-skills. Use as the optional substrate-linking stage of the Butterbase journey, after deploy and before submit.

When should I use Journey Substrate?

Journey Substrate fits situations like: agent Workflows work in your project.

How do I install Journey Substrate in Claude Code?

Run `npx skills add butterbase-ai/butterbase-skills --skill journey-substrate -a claude-code`. Or copy the skill folder (skills/journey-substrate in butterbase-ai/butterbase-skills) into .claude/skills/journey-substrate in your project. Claude Code loads it when a task matches its description.

How do I install Journey Substrate in Codex?

Run `npx skills add butterbase-ai/butterbase-skills --skill journey-substrate -a codex`. Or copy the skill folder (skills/journey-substrate in butterbase-ai/butterbase-skills) into .agents/skills/journey-substrate in your project. Codex loads it when a task matches its description.

Can I use Journey Substrate 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 butterbase-ai/butterbase-skills --skill journey-substrate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/journey-substrate, .gemini/skills/journey-substrate, .github/skills/journey-substrate and .opencode/skills/journey-substrate in your project.

What does Journey Substrate need to run?

SKILL.md names no scripts, command-line tools or credentials: Journey Substrate is instructions for the agent only.

Does Journey Substrate access the network?

SKILL.md names 1 domain. In commands or code: docs.butterbase.ai; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Journey Substrate 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. Review the folder before installing.

What licence does Journey Substrate use?

Journey Substrate 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 Journey Substrate use?

About 741 tokens (SKILL.md is roughly 3k 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 Journey Substrate?

Skills that share tags, products or a category with Journey Substrate: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Journey Substrate?

butterbase-ai (a GitHub organization) maintains it in butterbase-ai/butterbase-skills, which has 534 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 5, 2026.

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