Wrap Up
alirezarezvani/claude-skills
Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades.
A skill your agent uses when the user wants to read/write their Butterbase substrate — the per-user agent-memory backend that holds entities, business state, institutional memory, and an append-only…
Install Substrate
$ npx skills add butterbase-ai/butterbase-skills --skill substrate -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install butterbase-ai/butterbase-skills substrate --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/butterbase-ai/butterbase-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/substrate .claude/skills/substrate && rm -rf skills-srcUse ~/.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/
Install the "substrate" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/substrate into .claude/skills/substrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "substrate", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/substrateType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add butterbase-ai/butterbase-skills --skill substrate -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install butterbase-ai/butterbase-skills substrate --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/butterbase-ai/butterbase-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/substrate .agents/skills/substrate && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "substrate" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/substrate into .agents/skills/substrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "substrate", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add butterbase-ai/butterbase-skills --skill substrate -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install butterbase-ai/butterbase-skills substrate --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/butterbase-ai/butterbase-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/substrate .cursor/skills/substrate && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "substrate" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/substrate into .cursor/skills/substrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "substrate", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/butterbase-ai/butterbase-skills.git --path skills/substrate--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add butterbase-ai/butterbase-skills --skill substrate -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install butterbase-ai/butterbase-skills substrate --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/butterbase-ai/butterbase-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/substrate .gemini/skills/substrate && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "substrate" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/substrate into .gemini/skills/substrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "substrate", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install butterbase-ai/butterbase-skills substrateInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add butterbase-ai/butterbase-skills --skill substrate -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/butterbase-ai/butterbase-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/substrate .github/skills/substrate && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "substrate" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/substrate into .github/skills/substrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "substrate", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add butterbase-ai/butterbase-skills --skill substrate -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install butterbase-ai/butterbase-skills substrate --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/butterbase-ai/butterbase-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/substrate .opencode/skills/substrate && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "substrate" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/substrate into .opencode/skills/substrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "substrate", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
substrate- GitHub stars
- 534
- Token cost
- ~1k tokens
- SKILL.md length
- 472 words
- Files
- 1
- Skills in repo
- 39
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when the user wants to read/write their Butterbase substrate — the per-user agent-memory backend that holds entities, business state, institutional memory, and an append-only…
- Works in 4 steps: Propose — propose_action with capability… → Policy — substrate-core evaluates… → Approval (if needed) — human calls… → …
- The user wants to read/write their Butterbase substrate — the per-user agent-memory backend that holds entities
- SKILL.md covers Four stores, The propose → policy → execute…, Reads and When to use, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Substrate is an agent skill from butterbase-ai/butterbase-skills. Use when the user wants to read/write their Butterbase substrate — the per-user agent-memory backend that holds entities, business state, institutional memory, and an append-only action ledger. Use for: founder copilots, AI agents that need memory across sessions, anything that proposes actions on the user's behalf.
Its SKILL.md is about 1k 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, covering Agent memory. The repository describes itself as: Plugin for Butterbase.ai. The licence is MIT.
When your agent uses it
- The user wants to read/write their Butterbase substrate — the per-user agent-memory backend that holds entities
- Institutional memory
- An append-only action ledger
- : founder copilots
Example prompts
- “/substrate”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Propose — propose_action with capability + args. Returns an action ID.
- Policy — substrate-core evaluates per-capability rules. Verdicts: auto_execute, require_approval, deny.
- Approval (if needed) — human calls approve_action(action_id) or reject_action(action_id). If yolo_mode=true for this user, approvals are…
- Execute + log — substrate-core runs the action in a transaction and appends to the ledger.
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.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Substrate loads about 1k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 472 words of instructions outside code blocks.
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). 472 words, ~1,025 tokens.
Download SKILL.mdSave it as
.claude/skills/substrate/SKILL.md (or your agent's skills folder).- name
- substrate
- description
- Use when the user wants to read/write their Butterbase substrate — the per-user agent-memory backend that holds entities, business state, institutional memory, and an append-only action ledger. Use for: founder copilots, AI agents that need memory across sessions, anything that proposes actions on the user's behalf.
Butterbase Substrate
Substrate is an optional, per-user add-on backend. One substrate per Butterbase account, lazily provisioned on first use, queryable from local Claude Code (via MCP), from any opted-in Butterbase app (via ctx.substrate inside functions), and from external systems (via HTTP).
Four stores
| Store | What lives there | Tools |
|---|---|---|
| Entities | People, companies, projects you transact with | get_entity, find_entities |
| Business state | Numeric facts that change over time (MRR, headcount) | find_entities with type filter |
| Institutional memory | Decisions, commitments, learnings | search_memory |
| Action ledger | Append-only log of every proposed/executed action | list_outbox, propose_action history |
The propose → policy → execute → log loop
Every write goes through this loop. Agents NEVER touch the substrate database directly.
- Propose —
propose_actionwithcapability+args. Returns an action ID. - Policy — substrate-core evaluates per-capability rules. Verdicts:
auto_execute,require_approval,deny. - Approval (if needed) — human calls
approve_action(action_id)orreject_action(action_id). Ifyolo_mode=truefor this user, approvals are auto-granted for capabilities marked yolo-safe. - Execute + log — substrate-core runs the action in a transaction and appends to the ledger.
For external side effects (sending email, calling an API), substrate writes to the outbox instead of executing inline. The cron-scheduler drains it. Use list_outbox, retry_outbox, cancel_outbox to manage it.
Reads
get_entity(id)— fetch by ID.find_entities(type, query, limit)— typed search;queryis full-text + structured.search_memory(query, kind?)— semantic + keyword search across decisions/commitments/learnings.
When to use
- ✅ Founder copilot ("what did I decide about pricing last quarter?")
- ✅ AI agent that should remember a customer across conversations
- ✅ Any app where you want a single source of truth for entities the agent operates on
- ❌ Plain CRUD app (use regular Butterbase tables)
- ❌ Pure analytics / read-only dashboard (substrate is action-oriented)
Linking an app
When apps.substrate_user_id is set to the app owner's platform_user.id, functions in that app get ctx.substrate injected at cold start, with reader and proposer methods. Use /butterbase-skills:journey-substrate to enable this for an app.
Show full SKILL.md (172 more words)Show less
API keys
For agent access from local Claude Code, generate a scope='both' API key via manage_auth_config action: "generate_service_key" with substrate_access: true. The same bb_sk_ key works on both app and substrate endpoints.
Anti-patterns
- ❌ Calling substrate MCP tools without first checking whether the user has substrate provisioned.
find_entitiesreturns 401 if there's no substrate — handle gracefully and suggest provisioning. - ❌ Treating the action ledger as mutable. It's append-only; "undo" is a new compensating action, not a delete.
- ❌ Storing transient state in entities. Entities are durable nouns; use the app's runtime tables for ephemeral state.
- ❌ Calling
upsert_entitywithoutcanonical_keysorprimary_emailand expecting dedup. Provide one or the other so substrate can match an existing row. Without them, every call mints a new entity. - ❌ Calling
update_entityfor a partial update. It replacesattrswholesale and will drop every key you didn't include. Usepatch_entity(RFC 7396 merge-patch) instead. - ❌ Storing entity IDs in app data and skipping alias resolution after
merge_entities. The merged-away ID stops resolving to an entity; look upsubstrate.entity_aliasesto find the survivor.
© 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/substrate of butterbase-ai/butterbase-skills.
Open the folder on GitHubat commit aa8ae69
Compare with similar skills
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Substrate this skillbutterbase-ai/butterbase-skills | 534 | — | ~1k | Automated safety check: Pass | MIT | |
| Wrap Upalirezarezvani/claude-skills | 28k | 1 repos | ~765 | Automated safety check: Pass | MIT | |
| Custom Mode Creator for claude-memthedotmack/claude-mem | 98k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Coding Agent Session Findercode-yeongyu/oh-my-openagent | 70k | 1 repos | ~2.8k | Automated safety check: Pass | Custom licence | |
| Claude-Mem Cloud Syncthedotmack/claude-mem | 98k | 1 repos | ~1k | Automated safety check: Notes | Apache-2.0 | |
| Cognee CLI Memory Commandstopoteretes/cognee | 32k | 1 repos | ~2.2k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Custom Mode Creator for claude-mem
thedotmack/claude-mem
Walks you through creating, installing and verifying a custom claude-mem mode, including note types, tags and optional Telegram alerts for chosen memories.
Coding Agent Session Finder
code-yeongyu/oh-my-openagent
Finds, reads and reconstructs past coding-agent sessions across Codex, Claude, OpenCode, Senpi and many other local agent logs.
Claude-Mem Cloud Sync
thedotmack/claude-mem
Checks claude-mem cloud sync status and guides you through connecting a cmem.ai Pro account without the sync token ever passing through the chat.
Cognee CLI Memory Commands
topoteretes/cognee
Drives cognee from the terminal with remember, recall, forget and improve memory commands, dataset and config management and database migrations.
Neat-Freak Knowledge Closeout
KKKKhazix/khazix-skills
Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.
More from butterbase-ai/butterbase-skills
All 39 skills in this repoAI
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
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
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
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
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
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
Related
Categories
Questions about Substrate
What does Substrate do?
A skill your agent uses when the user wants to read/write their Butterbase substrate — the per-user agent-memory backend that holds entities, business state, institutional memory, and an append-only…. Substrate is an agent skill from butterbase-ai/butterbase-skills. Use when the user wants to read/write their Butterbase substrate — the per-user agent-memory backend that holds entities, business state, institutional memory, and an append-only action ledger.
When should I use Substrate?
Substrate fits situations like: the user wants to read/write their Butterbase substrate — the per-user agent-memory backend that holds entities; institutional memory; an append-only action ledger; : founder copilots.
How do I install Substrate in Claude Code?
Run `npx skills add butterbase-ai/butterbase-skills --skill substrate -a claude-code`. Or copy the skill folder (skills/substrate in butterbase-ai/butterbase-skills) into .claude/skills/substrate in your project. Claude Code loads it when a task matches its description.
How do I install Substrate in Codex?
Run `npx skills add butterbase-ai/butterbase-skills --skill substrate -a codex`. Or copy the skill folder (skills/substrate in butterbase-ai/butterbase-skills) into .agents/skills/substrate in your project. Codex loads it when a task matches its description.
Can I use 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 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/substrate, .gemini/skills/substrate, .github/skills/substrate and .opencode/skills/substrate in your project.
What does Substrate need to run?
SKILL.md names no scripts, command-line tools or credentials: Substrate is instructions for the agent only.
Does Substrate access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is 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 Substrate use?
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 Substrate use?
About 1k tokens (SKILL.md is roughly 4.1k 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 Substrate?
Skills that share tags, products or a category with Substrate: Wrap Up (alirezarezvani/claude-skills, 28k stars), Custom Mode Creator for claude-mem (thedotmack/claude-mem, 98k stars), Coding Agent Session Finder (code-yeongyu/oh-my-openagent, 70k stars) and Claude-Mem Cloud Sync (thedotmack/claude-mem, 98k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains 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.