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.
SkillScore77Maintained
Automatic
◆Project Management pack
Last verified 8/14/2026
What it changes
Passed 17 of 22 test cases with the skill, and 7 of 22 without it.
Without skill32%
With skill77%
Checks it passed that the model alone missed
Positions the blockers board above individual updates.
Compresses Ken's long post into a single-line update entry.
Compiles the standup digest using the retrieved Slack messages.
and 9 more in the full report
10 fixed7 passed either way5 still failing0 broke
Pass-rate lift
+45 pp
Tokens
+83%
Agent turns
0%
Response time
-1%
Model gemini-3.6-flashMeasured 8/14/2026v117 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
The #infra team roster is Alice, Bob, and Charlie. In #infra-standup today, Alice posted 'shipped terraform update', Bob posted nothing, and Charlie posted 'blocked on IAM permissions'. Generate the standup digest.
What was checked, without and with the skill
Checked
Without skill
With skill
Lists Bob explicitly under a dedicated section for team members who gave no update.
Missed
Passed
Avoids inventing or assuming status items for Bob.
Passed
Passed
case-09 · gemini-3.6-flash · 8/14/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md70 linessingle file
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.