Skills anthropics knowledge-work-plugins

standup

Use it when:: You're preparing for daily standup and want your recent work turned into a shareable update.
You get:: A dated Markdown update with Yesterday, Today and Blockers, ticket references where available, and who can help with each blocker.
From:: Rough notes you give it, or, with connectors, your recent commits and PRs, ticket moves, sprint items and chat discussions.
Also:: Flags chat threads that need your response, and formats the update for Slack, email or your team's standup tool on request.
Runs:: As /standup, optionally for yesterday, today or blockers.
Part of:: The engineering plugin of Anthropic's knowledge-work plugins.

TL;DR

A standup command from the engineering plugin of Anthropic's knowledge-work plugins. It works two ways. Without connectors, you tell it what you did, such as "worked on the auth migration, reviewed 3 PRs, got blocked on the API rate limiting issue", and it structures that into a concise, action-oriented update. With connectors, /standup alone gathers the material: commits and PRs you opened, reviewed or merged, summarized at a high level, from source control; tickets moved to in progress or done, and upcoming sprint items, from a project tracker; relevant discussions and decisions from chat, with threads that need your reply flagged. The update has three sections, Yesterday, Today and Blockers, with ticket references where available and, for each blocker, its context and who can help. You can add nuance afterwards, or ask for it formatted for Slack, email or your team's standup tool.

Summarizes the skill at ab4cb1c.

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill standup

skills.sh page Source on GitHub All skills from anthropics/knowledge-work-plugins

Total Downloads: 5,300 on skills.sh, Nov 9, 2026
Repo stars: 35,234 anthropics/knowledge-work-plugins
First seen: Mar 13, 2026 on skills.sh

Weekly Downloads

-35% over the 8 weeks to Nov 9

Weekly values

Week to	Installs
Sep 21	77
Sep 28	45
Oct 5	35
Oct 12	54
Oct 19	52
Oct 26	55
Nov 2	45
Nov 9	50

Category	category:writing Articles, docs, internal comms, research write-ups and prose that doesn't read as generated.
Type	type:command A one-shot action you invoke by name, such as turning the conversation into a PRD.
Effect	effect:none Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code.
Needs	needs:none Instructions only. Works in any agent that supports skills.
Publisher	by:official A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates.
Topics	writing git issue-tracking

SKILL.md

From anthropics/knowledge-work-plugins at ab4cb1c. Checked daily, last changed Nov 6, 2026.

Frontmatter

name: standup
description: Generate a standup update from recent activity. Use when preparing for daily standup, summarizing yesterday's commits and PRs and ticket moves, formatting work into yesterday/today/blockers, or structuring a few rough notes into a shareable update.
argument-hint: "[yesterday | today | blockers]"

/standup

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Generate a standup update by pulling together recent activity across your tools.

How It Works

┌─────────────────────────────────────────────────────────────────┐
│                        STANDUP                                    │
├─────────────────────────────────────────────────────────────────┤
│  STANDALONE (always works)                                       │
│  ✓ Tell me what you worked on and I'll structure it             │
│  ✓ Format for daily standup (yesterday / today / blockers)      │
│  ✓ Keep it concise and action-oriented                          │
├─────────────────────────────────────────────────────────────────┤
│  SUPERCHARGED (when you connect your tools)                      │
│  + Source control: Recent commits and PRs                        │
│  + Project tracker: Ticket status changes                        │
│  + Chat: Relevant discussions and decisions                      │
│  + CI/CD: Build and deploy status                                │
└─────────────────────────────────────────────────────────────────┘

What I Need From You

Option A: Let me pull it If your tools are connected, just say /standup and I'll gather everything automatically.

Option B: Tell me what you did "Worked on the auth migration, reviewed 3 PRs, got blocked on the API rate limiting issue."

Output

## Standup — [Date]

### Yesterday
- [Completed item with ticket reference if available]
- [Completed item]

### Today
- [Planned item with ticket reference]
- [Planned item]

### Blockers
- [Blocker with context and who can help]

If Connectors Available

If ~~source control is connected:

Pull recent commits and PRs (opened, reviewed, merged)
Summarize code changes at a high level

If ~~project tracker is connected:

Pull tickets moved to "in progress" or "done"
Show upcoming sprint items

If ~~chat is connected:

Scan for relevant discussions and decisions
Flag threads needing your response

Tips

Run it every morning — Build a habit and never scramble for standup notes.
Add context — After I generate, add any nuance about blockers or priorities.
Share format — Ask me to format for Slack, email, or your team's standup tool.