Standup
- 4.2k installs
- 23.1k repo stars
- Updated July 28, 2026
- anthropics/knowledge-work-plugins
How do I quickly prepare a structured daily standup update from my work activity?
About
Standup generates structured daily standup updates by aggregating recent work activity across source control, project trackers, chat, and CI/CD systems. Developers use it to prepare for team standups without manual note-taking, pulling commits and PRs from git, ticket status changes from project management tools, relevant discussions from chat, and build status from CI/CD pipelines. The tool formats output into yesterday/today/blockers sections. It works standalone when developers provide a brief summary of their work, or supercharged when tools are connected via Skillselion connectors. Key workflow: run each morning to automatically gather activity, add context about blockers, and optionally reformat for Slack or email before sharing with the team. Pulls recent commits, PRs, and code reviews from source control automatically. Aggregates ticket moves and status changes from connected project trackers. Scans chat systems for relevant discussions and decisions affecting work.
- Pulls recent commits, PRs, and code reviews from source control automatically
- Aggregates ticket moves and status changes from connected project trackers
- Scans chat systems for relevant discussions and decisions affecting work
- Formats output into standard yesterday/today/blockers structure for team standups
- Works standalone via manual input or supercharged with connected integrations
Standup by the numbers
- 4,156 all-time installs (skills.sh)
- +202 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #125 of 3,301 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
standup capabilities & compatibility
- Capabilities
- aggregates commits and prs from source control · pulls ticket status changes from project tracker · scans chat for relevant discussions · retrieves ci/cd build and deploy status · structures activity into standup format · reformats output for slack or email
- Works with
- github · gitlab · bitbucket · jira · slack · teams
- Use cases
- project management · documentation
- Runs
- Hosted SaaS
- Pricing
- Freemium
What standup says it does
Generate a standup update by pulling together recent activity across your tools.
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill standupAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 4.2k |
|---|---|
| repo stars | ★ 23.1k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 28, 2026 |
| Repository | anthropics/knowledge-work-plugins ↗ |
What it does
Automatically generate daily standup summaries from recent commits, PRs, tickets, and chat activity across connected tools.
Who is it for?
Teams with daily standups; developers using multiple connected tools (git, project trackers, chat, CI/CD); morning routine optimization.
Skip if: Teams without standup requirements; standalone developers without connected integrations; async-only communication workflows.
When should I use this skill?
Preparing for daily standup meeting; need to summarize work from previous day; have rough notes to structure; want to gather cross-tool activity automatically.
What you get
Standup automatically gathers recent activity and formats it into a ready-to-share yesterday/today/blockers structure.
- Formatted standup message
- Yesterday/today/blockers sections
By the numbers
- Supports four tool integrations: source control, project tracker, chat, CI/CD
- Three output sections: Yesterday, Today, Blockers
Files
/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
1. Run it every morning — Build a habit and never scramble for standup notes. 2. Add context — After I generate, add any nuance about blockers or priorities. 3. Share format — Ask me to format for Slack, email, or your team's standup tool.
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.645k185kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.547k185k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.466kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).466kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.466kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.465kHow it compares
Pick standup over generic summarization skills when the deliverable must follow the standard three-part daily standup structure from live dev-tool activity.
FAQ
Does standup require connected tools?
No - it works standalone when you describe your work verbally. Connectors enable automatic activity gathering from git, project trackers, chat, and CI/CD.
What format does standup output?
Standard format with three sections: Yesterday (completed items), Today (planned items), Blockers (issues and who can help). Can be reformatted for Slack or email.
How often should I run standup?
Documentation recommends running each morning as a habit to gather activity overnight and prepare before standup meetings.
Is Standup safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.