From vibemind-relaymind
Produce or recall RelayMind daily summaries via viberelay relaymind daily. Use when the supervisor signals a daily summary is due (default 22:00 local), when the user asks "what did we do today", "/daily", or wants to inspect a past day. Daily summaries are written by the persistent Claude session, never by hooks.
npx claudepluginhub yusuflisawi/viberelay --plugin vibemind-relaymindThis skill is limited to using the following tools:
Daily summaries are persisted in SQLite (`type=daily_summary`, FTS-indexed)
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.
Daily summaries are persisted in SQLite (type=daily_summary, FTS-indexed)
and rendered to .relaymind/daily/YYYY-MM-DD.md. SQLite is the source of
truth; the markdown is a human-friendly artifact.
viberelay relaymind daily summarize
Before you call it, gather material:
viberelay relaymind checkpoint latest
viberelay relaymind mem search "$(date +%Y-%m-%d)" --limit 20
viberelay relaymind mem search "<topic of the day>" --limit 10
Compose the summary in the documented shape:
# Daily Summary — YYYY-MM-DD
## Done
- ...
## Decisions
- ...
## Open Loops
- ...
## Next
- ...
viberelay relaymind daily summarize accepts the body via the CLI's prompt
and stores it through the memory layer.
viberelay relaymind daily show # today
viberelay relaymind daily show 2026-04-26
viberelay relaymind daily search "<query>"
viberelay relaymind daily summarize.decision items.Done would be empty, say "(quiet day)".