Configures per-project memory storage mode and writes the memory plugin config.
npx skills add https://github.com/reddb-io/red-skills --skill init-reddb-io
Please help me install this Agent Skill. Skill: init Source: https://github.com/reddb-io/red-skills/tree/main/plugins/memory/skills/core/init Command: npx skills add https://github.com/reddb-io/red-skills --skill init-reddb-io
.red/memory/notes/, no engine) and graph mode (governed operational memory over a per-project RedDB store at .red/memory/graph.rdb). - Automatic runtime bootstrap: The bundled bootstrap.mjs script downloads the memory CLI and native red engine on first use with checksum verification — no build step required. - Optional auto-firing hooks: In graph mode, optionally enable SessionStart recall, PostToolUse re-index, Stop extract, and PreCompact flush hooks, which stay dormant until the config flag is on. - Use Case: After installing the memory plugin, run the wizard to pick graph mode with hooks, then immediately use /memory:store and /memory:recall against the configured store. ## Quick Start Ask the assistant to initialize memory for this repository and walk you through choosing a storage mode.High-intent search queries and answers about installing and using this skill.
Run the init wizard from the repository root, which asks which storage mode to use and writes the `plugins.memory` block to `.red/config.yaml`. Pass `--mode markdown-only` or `--mode graph` to the bootstrap script, and add `--hooks` only in graph mode if you want auto-firing hooks.
Markdown-only stores plain searchable notes under `.red/memory/notes/` with no engine, hooks, or MCP server. Graph mode stores governed operational memory as nodes and edges in a per-project RedDB store at `.red/memory/graph.rdb`, with dedupe, provenance, and optional hooks.
No separate installation is needed. The bundled bootstrap script downloads the memory CLI and native `red` engine into a cache directory on first use and verifies checksums. Markdown-only mode does not require RedDB at all.
Pass `--hooks` during init in graph mode only after the user confirms. Hooks are wired in the plugin manifest but stay dormant until the per-project config flag is on. On Codex, also set `[features].plugin_hooks = true` since hooks are off by default there.
No. The `.red/memory/graph.rdb` store is per-project local state and should not be committed, similar to `node_modules/`. The config in `.red/config.yaml` is written through the CLI to keep the schema valid.
xlelibertyProvision software stacks and initialize local development environments with the Stripe Projects CLI.
dmae97Classify coding agent memories and generate evidence bundles for audit replay.
wormholecowboyConfigure Claude Code hooks for lifecycle events with templates and scripts.
tiankong0101-byteBuild and query graph-based knowledge structures from unstructured information.