Skill

relaymind-daily

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-relaymind

Tool Access

This skill is limited to using the following tools:

Bash(viberelay relaymind daily *)Bash(viberelay relaymind mem *)Bash(viberelay relaymind checkpoint latest)

Preview

Daily summaries are persisted in SQLite (`type=daily_summary`, FTS-indexed)

SKILL.md

Similar Skills

cache-components

139.3k

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.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Parent Repo Stars1

Parent Repo Forks1

Last CommitApr 30, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

relaymind-daily

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.

Generate today's summary

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.

Read past summaries

viberelay relaymind daily show # today viberelay relaymind daily show 2026-04-26 viberelay relaymind daily search "<query>"

Decision flow

Pull the latest checkpoint and any same-day memories.

Draft a terse summary — bullets, no narrative filler.

Write via viberelay relaymind daily summarize.

If new durable decisions surfaced during composition, also call the memory skill to record them as decision items.

Hard rules

Never call from a hook.

Never invent activity. If Done would be empty, say "(quiet day)".

Do not include secrets.

relaymind-daily

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.

Generate today's summary

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.

Read past summaries

viberelay relaymind daily show          # today
viberelay relaymind daily show 2026-04-26
viberelay relaymind daily search "<query>"

Decision flow

Pull the latest checkpoint and any same-day memories.
Draft a terse summary — bullets, no narrative filler.
Write via viberelay relaymind daily summarize.
If new durable decisions surfaced during composition, also call the memory skill to record them as decision items.

Hard rules

Never call from a hook.
Never invent activity. If Done would be empty, say "(quiet day)".
Do not include secrets.