| name | activity-summary |
| description | Use when an agent is asked "what did I (or my team) work on yesterday / this week / today" across provider data in a relayfile mount (Linear, GitHub, Notion, Slack, Confluence, Jira, etc.). Tells the agent to consult the pre-computed `digests/yesterday.md` (and sibling digest files) at the workspace root BEFORE doing manual exploration with `ls`/`grep`/`find`. The digest is deterministic, exhaustive over the window, and costs one file read instead of dozens of provider queries. |
Activity Summary — Read the Digest First
Overview
A relayfile workspace pre-computes deterministic daily activity digests at <mount>/digests/. These are produced by relayfile itself from the raw provider data, so they are complete over the time window (no API pagination gaps) and free for the agent to consume (one file read, no LLM generation step).
If you've been asked an activity-summary question, read the digest before doing anything else. Reaching for ls, grep, or per-provider exploration first is the most common reason these answers cost 20+ tool calls when they could cost 1.
When to use this skill
Trigger phrases from the user — read the digest first:
- "what did I work on yesterday / today / this week"
- "what changed across {GitHub, Linear, Notion, Slack, ...} {yesterday, since Friday, etc.}"
- "summarize my activity"
- "give me a standup update"
- "what did $team_member ship recently"
If the user's question is not windowed by time (e.g. "find the Notion page about onboarding"), the digest is not the right entry point — use by-title/ or by-id/ indexes instead. See the workspace-layout skill.
What digests look like
$ ls /digests/
yesterday.md
today.md
2026-05-12.md
2026-05-11.md
...
this-week.md
last-week.md
