---
name: hourly-digest
description: |
  This skill should be used when the user asks to "check hourly updates",
  "hourly digest", "slack hourly summary", "gmail daily summary",
  "what happened in the last hour", "hourly monitoring", or needs a periodic
  digest from Slack or Gmail. Runs as two independent loops on different
  cadences: Slack hourly, Gmail daily. Also triggers for automated invocation
  via /loop 1h /hourly-digest:hourly-digest slack and
  /loop 1d /hourly-digest:hourly-digest gmail.
  Distinct from per-channel Slack digest or single-source summaries.
  For GitHub/Linear activity sync, use /loop 1h /github-activity separately.
argument-hint: "[slack|gmail]"
---

# Hourly Digest

Two independent digest loops on different cadences: Slack messages from the past hour, Gmail from the past day. Respond in the user's language.

The cadences differ by source constraint: Gmail's `newer_than:` search operator only supports day/month/year units (no hour granularity), so the Gmail loop runs daily while the Slack loop runs hourly.

## Argument Parsing

Parse `ARGUMENTS` for an optional subcommand:

| Input | Behavior |
|-------|----------|
| (empty) | Run both sections: Slack (past hour), Gmail (past day) |
| `slack` | Slack hourly digest only |
| `gmail` | Gmail daily digest only |

## Execution

Run each requested section independently. On failure, report `[ERROR] Source: {message}` and continue to the next section.

Load all needed MCP tools upfront in a single call before starting any section:

```
ToolSearch("select:mcp__claude_ai_Slack__slack_search_public_and_private,mcp__claude_ai_Gmail__gmail_search_messages,mcp__claude_ai_Gmail__gmail_read_message")
```

### 1. Slack Hourly Digest (past hour)

1. Compute today's date via Bash: `date '+%Y-%m-%d'` (Slack `after:` excludes the given date; use `on:` to include it)
2. Use `slack_search_public_and_private` with query `on:{date}` to find today's messages. During the first hour of the day (00:00-00:59), also run a second query with `on:{yesterday}` so the window spanning midnight is covered. Filter combined results to the past hour by message timestamp
3. Group results by topic — cluster messages about the same subject together, even when they span multiple channels
4. Per topic: `**Topic** (N): key points — [#channel-name](https://{workspace}.slack.com/archives/{channel_id})`
5. For notable messages with threads, link to the thread: `[thread](https://{workspace}.slack.com/archives/{channel_id}/p{timestamp_no_dot})`
6. If no messages found, state that there are none

Construct Slack links from search result metadata: channel ID for channel links, channel ID + message timestamp (remove the dot) for thread permalinks.

### 2. Gmail Daily Digest (past day)

1. Use `gmail_search_messages` with query `newer_than:1d`
2. If search results already include sender and subject, use them directly. Only call `gmail_read_message` for items missing these details (avoid N+1 reads)
3. Group by topic — cluster related subjects and threads together
4. Per topic: `**Topic** (N): key points — ["Subject"](https://mail.google.com/mail/u/0/#inbox/{messageId}) from sender`, listing a link for every message in the topic (do not collapse to a single link when N > 1)
5. If no emails found, state that there are none

Construct Gmail links from the messageId returned by search results.

## Output Format

Each section gets its own header carrying its own time window:

- Slack: `## Slack Hourly Digest (HH:MM-HH:MM KST)`
- Gmail: `## Gmail Daily Digest (YYYY-MM-DD)`

Example structure:

```
## Slack Hourly Digest (14:00-15:00 KST)
- **Auth service hotfix** (3): deployment discussion and rollout decision — [#channel-a](https://workspace.slack.com/archives/C0123), [hotfix thread](https://workspace.slack.com/archives/C0123/p1234567890)
- **Standup** (1): reminder — [#channel-b](https://workspace.slack.com/archives/C0456)

## Gmail Daily Digest (2026-06-12)
- **Billing renewal** (1): ["Subject line"](https://mail.google.com/mail/u/0/#inbox/msg123) from sender@example.com
- **Project kickoff** (2): ["Thread topic"](https://mail.google.com/mail/u/0/#inbox/msg456) from another@example.com, ["Re: Thread topic"](https://mail.google.com/mail/u/0/#inbox/msg789) from third@example.com
```

When a section has no results, use a single line indicating nothing new.
When running a single section via subcommand, omit the other section entirely.

## Cron Usage

```
/loop 1h /hourly-digest:hourly-digest slack
/loop 1d /hourly-digest:hourly-digest gmail
```

Plugin skills are namespaced as `{plugin-name}:{skill-name}`; the bare `/hourly-digest` form only resolves for a user-level skill installation.