substrate
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.
Profile →npx skills add butterbase-ai/butterbase-skills --skill substrate --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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. 1. **Propose** — `propose_action` with `capability` + `args`. Returns an action ID. 2. **Policy** — substrate-core evaluates per-capability rules. Verdicts: `auto_execute`, `require_approval`, `deny`. 3. **Approval (if needed)** — human calls `approve_action(action_id)` or `reject_action(action_id)`. If
- Four stores
- The propose → policy → execute → log loop
- Reads
- When to use
- Linking an app
- API keys
- Anti-patterns
What does the substrate skill do?
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.
How do I install it?
Run `npx skills add butterbase-ai/butterbase-skills --skill substrate --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From butterbase-ai/butterbase-skills, a repository with 532 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.