Compile the team's REAL updates into one async standup — pull what people posted in Slack (and moved in Notion/Linear), not a template for running standups. Use when asked to compile today's standup, pull the team's updates into one post, what did the team ship, or run async standup in Cowork. Reads a Slack channel and (optionally) the tracker via connectors, groups updates by person into shipped / in-progress / blocked, surfaces the blockers needing attention, and produces a standup-digest artifact ready to post back.
Start a fresh conversation. Replace the highlighted placeholders.
Use async-standup-compiler to compile [Slack channel] updates for [time window] against the expected [roster] into a concise, post-ready digest and blocker board; do not post it.
Required inputs
[Slack channel]
[time window]
[roster]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: async-standup-compilerdescription: "Compile the team's REAL updates into one async standup — pull what people posted in Slack (and moved in Notion/Linear), not a template for running standups. Use when asked to compile today's standup, pull the team's updates into one post, what did the team ship, or run async standup in Cowork. Reads a Slack channel and (optionally) the tracker via connectors, groups updates by person into shipped / in-progress / blocked, surfaces the blockers needing attention, and produces a standup-digest artifact ready to post back."
Async Standup Compiler (Live)
Async standups scatter across a channel — twelve messages, three threads, and the blockers get lost. In Claude Cowork this skill reads the real channel (and the tracker), compiles one clean digest grouped by person and status, and surfaces the blockers that actually need someone — so the team gets signal, not scroll.
What This Skill Produces
The standup digest — each person's shipped / in-progress / blocked, deduped and tightened
The blocker board — blockers pulled to the top with who's waiting on whom
A post-ready artifact — the digest formatted to drop back into Slack/Notion (posted only on request)
Required Inputs
Ask for these if not provided:
The channel & window — which Slack channel and time range (e.g. "#eng-standup, today")
The roster — who's expected, so silence is visible
Tracker (optional) — a Notion/Linear board to cross-reference what actually moved
Framework: A Standup That Earns Its Place
By person, by status — shipped / in-progress / blocked; one line each, no essays.
Blockers first-class — every blocker names who can unblock it.
Silence is data — expected people who didn't post are listed, not hidden.
Cross-check reality — if a tracker is available, note "said done" vs "still open".
Signal over ceremony — the digest is shorter than the raw channel.
Execution (Cowork)
Read the channel — via the Slack connector, pull messages in the window; follow threads. Map each update to its author.
Cross-reference (optional) — via the Notion/Linear connector, check what moved; flag mismatches between claims and the board.
Compile — group by person into shipped/in-progress/blocked; dedupe repeats; keep each item to a line. List rostered people who didn't post.
Surface blockers — pull them to a board with the owner and who's waiting.
Emit the artifact — the digest, formatted for the target. Post it back only if asked; default is produce-and-show.
Guardrails: attribute every item to the person who actually posted it; don't invent updates for silent members — list them as "no update"; flag claim-vs-tracker mismatches rather than resolving them silently; post only on explicit request; if a connector is unauthorised, compile from what's available and say what's missing.