Unified Event Stream Query

VerifiedSafe

Query the unified event stream for recent activity across all surfaces (CLI, iMessage, wake cycles, webhooks, etc.). Use to answer questions about recent conversations, what happened on iMessage today, or CLI sessions earlier. Supports filters by surface type and time range.

Sby Skills Guide Bot
ProductivityIntermediate
6/2/2026
Claude Code
#stream#event-query#recent-activity#cross-surface#recall

Recommended for

Automated summary

Queries the unified event stream for recent activity across all surfaces (CLI, iMessage, wake cycles, webhooks, etc.).

Strengths

  • Centralizes interaction history across multiple surfaces.
  • Easy filtering by surface (iMessage, CLI, webhooks, etc.).
  • Detailed JSON output for automated analysis.

Limitations

  • Requires the stream binary to be installed and configured.
  • Distilled events may be missed unless --include-distilled is used.
  • Limited to locally accessible data, no built-in cloud sync.
When to use it

When you need to quickly recall recent conversations or cross-surface activity.

When not to use it

For deep historical search or when the event stream is irrelevant.

Security analysis

Safe
Quality score95/100

This skill uses Bash to run a local binary with predefined, read-only queries; no destructive actions, external data exfiltration, or obfuscation.

No concerns found

How this analysis is made

Examples

Recent iMessage activity
What happened on iMessage today?
All recent activity
Show me all recent activity
CLI sessions from today
What did we talk about in CLI sessions today?

name: stream description: Query the unified event stream for recent activity across all surfaces. Use when user asks about recent conversations, what happened on iMessage/CLI/wake cycles, or wants to see cross-surface activity. Trigger words: stream, recent activity, what happened, iMessage today, CLI earlier, recent conversations, cross-surface. context: fork allowed-tools:

  • Bash
  • Read

Unified Event Stream Query

This skill provides on-demand access to the unified event stream - all interactions across all surfaces (CLI, iMessage, wake cycles, webhooks, social media, etc.).

When to Use

  • User asks "what happened on iMessage today?"
  • User asks "what did we talk about in CLI earlier?"
  • User wants to see recent cross-surface activity
  • User asks "show me the stream" or "recent activity"
  • You need detailed recall of specific surface interactions

Commands

Quick Overview (last N hours)

~/.claude-mind/bin/stream query --hours 6

Filter by Surface

# iMessage only
~/.claude-mind/bin/stream query --hours 12 --surface imessage

# CLI only
~/.claude-mind/bin/stream query --hours 12 --surface cli

# Wake cycles
~/.claude-mind/bin/stream query --hours 24 --surface wake

# Dream cycles
~/.claude-mind/bin/stream query --hours 48 --surface dream

# Webhooks/social
~/.claude-mind/bin/stream query --hours 24 --surface webhook
~/.claude-mind/bin/stream query --hours 24 --surface x
~/.claude-mind/bin/stream query --hours 24 --surface bluesky

Statistics

~/.claude-mind/bin/stream stats

Detailed JSON Output

~/.claude-mind/bin/stream query --hours 6 --format json

Include Already-Processed Events

~/.claude-mind/bin/stream query --hours 24 --include-distilled

Surface Types

| Surface | Description | |---------|-------------| | cli | Direct Claude Code sessions | | imessage | iMessage conversations via Samara | | wake | Autonomous wake cycle events | | dream | Nightly dream cycle events | | webhook | External webhook triggers | | x | X/Twitter interactions | | bluesky | Bluesky interactions | | email | Email events | | calendar | Calendar events | | location | Location changes | | sense | Generic sense events | | system | Internal system events |

Output Interpretation

Each event shows:

  • Timestamp - When it occurred
  • Surface - Where it came from
  • Summary - Brief description
  • [distilled] - Already processed by dream cycle

Example Queries

"What did we talk about in iMessage today?"

~/.claude-mind/bin/stream query --hours 12 --surface imessage

"Show me all recent activity"

~/.claude-mind/bin/stream query --hours 6

"What happened in CLI sessions today?"

~/.claude-mind/bin/stream query --hours 24 --surface cli

"Show me the raw event data"

~/.claude-mind/bin/stream query --hours 3 --format json | head -100

Presenting Results

When presenting stream results to the user:

  1. Summarize the activity by surface
  2. Highlight key conversations or events
  3. Note the timeline
  4. Connect to current context if relevant

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/unified-event-stream-query-mma3jrkx/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/unified-event-stream-query-mma3jrkx' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/unified-event-stream-query-mma3jrkx/download' --output '.skill-downloads/unified-event-stream-query-mma3jrkx/SKILL.md.part' && mv '.skill-downloads/unified-event-stream-query-mma3jrkx/SKILL.md.part' '.skill-downloads/unified-event-stream-query-mma3jrkx/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/unified-event-stream-query-mma3jrkx/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills