How do I install the Standup skill?

Run npx skillmds@latest add charlieviettq/standup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Standup safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Standup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Standup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Standup?

charlieviettq (@charlieviettq) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Standup by charlieviettq — Agent Skill

Name: Standup
Author: charlieviettq

Standup

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.

charlieviettq Updated Sep 17, 2026

File contents

/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.

---name: standupdescription: 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.---# /standup> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../CONNECTORS-engineering.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```markdown## 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 AvailableIf **~~source control** is connected:- Pull recent commits and PRs (opened, reviewed, merged)- Summarize code changes at a high levelIf **~~project tracker** is connected:- Pull tickets moved to "in progress" or "done"- Show upcoming sprint itemsIf **~~chat** is connected:- Scan for relevant discussions and decisions- Flag threads needing your response## Tips1. **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.

Frequently asked questions