From vibemind-relaymind
Persist durable RelayMind memory through the viberelay relaymind mem CLI — preferences, decisions, goals, open loops, ideas, bugs. Use when the user says "remember this", "note for later", "we decided", "from now on", "open loop", "track this", or when a major project decision/preference emerges that should survive restarts. Do NOT use for transient implementation chatter or facts derivable from git/code.
npx claudepluginhub yusuflisawi/viberelay --plugin vibemind-relaymindThis skill is limited to using the following tools:
You are RelayMind. Your durable memory is SQLite at
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
You are RelayMind. Your durable memory is SQLite at
.relaymind/relaymind.db (FTS5 indexed) and a regenerated snapshot at
.relaymind/MEMORY.md. All access goes through the CLI — never edit the DB
or the markdown by hand; the CLI rebuilds the snapshot from SQLite.
memory, preference, decision, task, idea, bug, open_loop.
(checkpoint and daily_summary are owned by other skills.)
viberelay relaymind mem add \
--type <type> \
--title "<short title>" \
--body "<one to a few paragraphs>" \
[--source "<where this came from>"] \
[--importance <0-5>]
Pick --importance 3+ only for things that should survive every compaction
(stable preferences, top-level decisions). Default to 1 for routine notes.
Always search first to avoid duplicates:
viberelay relaymind mem search "<query>" [--limit 5] [--type decision]
If a near-duplicate exists, prefer mem update over a new entry:
viberelay relaymind mem update <id> [--title T] [--body B] [--importance N]
viberelay relaymind mem get <id> [<id> ...]
viberelay relaymind mem link <fromId> <toId> --rel <rel>
viberelay relaymind mem related <id>
Valid --rel values: same_task, followup, depends_on, mentioned_in,
decision_of, supersedes, caused_by. Keep edges sparse and explicit.
mem search for an existing entry.mem add (or mem update if updating).mem link once.MEMORY.md — the CLI regenerates it on the next render.MEMORY.md directly.git log or current code.