async-update-format
Write status updates people actually read — the traffic-light-plus-narrative format (state first, story second), the blockers-are-asks rule, and the skimmable structure that respects a reader with thirty seconds. Use when asked write my weekly update, format our team's status posts, nobody reads my updates, or what goes in a good async check-in. Produces the update format with a filled example, the blockers-as-asks discipline, and the reader-time contract.
npx skills add mohitagw15856/pm-claude-skills --skill async-update-format --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 Update Format Skill Status updates die of two diseases: the activity log ("attended meetings, worked on the project") that says nothing, and the essay that says everything to readers with thirty seconds. The format that survives: **state first** (on-track / at-risk / blocked, with the one-line why), then the delta (what changed since last time — not what exists), then blockers written as *asks with names* ("blocked on X — need [person] to approve Y by Friday"), then the next milestone with its date. Skimmable in thirty seconds, expandable for the reader who wants more. ## What This Skill Produces - **The format** — state → delta → asks → next, with length budgets per section - **A filled example** — realistic, showing the delta-not-inventory discipline - **The blockers-as-asks rule** — every blocker names a person and an action, or it's just weather - **The reader-time contract** — the 30-second skim layer and the optional depth layer, separated ## Required Inputs Ask for these if not provided: - **The update's audience and altitude** — the manager (risks and asks), the team (coordination detail), stakeholders (outcomes) — one update rarely serves all three; the format flex
- What This Skill Produces
- Required Inputs
- Framework: The Format Rules
- Output Format
- Quality Checks
- Anti-Patterns
What does the async-update-format skill do?
Write status updates people actually read — the traffic-light-plus-narrative format (state first, story second), the blockers-are-asks rule, and the skimmable structure that respects a reader with thirty seconds. Use when asked write my weekly update, format our team's status posts, nobody reads my updates, or what goes in a good async check-in. Produces the update format with a filled example, the blockers-as-asks discipline, and the reader-time contract.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill async-update-format --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.