async-standup-compiler
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.
npx skills add mohitagw15856/pm-claude-skills --skill async-standup-compiler --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 1. **By person, by status** — shipped / in-progress / blocked; one line each, no essays. 2. **Blockers first-class** — every blocker names who can unblock it. 3. **Silence is data** — expected people who
- What This Skill Produces
- Required Inputs
- Framework: A Standup That Earns Its Place
- Execution (Cowork)
- Output Format
- 🚑 Blockers (needs attention)
- Updates by person
- No update
- Reality check (if tracker available)
- Quality Checks
- Anti-Patterns
- Example Trigger Phrases
What does the async-standup-compiler skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill async-standup-compiler --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.