Skill Tracer
Skills › Knowledge Work Plugins › standup

standup

skill · 75 lines · Apache-2.0 · engineering/skills/standup/SKILL.md

The facts

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

The description the agent reads to decide when to use it.

From its settingsline 3

When it starts

This skill is used to generate a daily standup update by summarizing recent activity across various tools. A user would pick this skill when preparing for a daily standup meeting or when they need to structure rough notes into a shareable update.

Things a person might say (the model's guesses)

  • “Generate a standup update.”
  • “Worked on the auth migration, reviewed 3 PRs, got blocked on the API rate limiting issue.”
  • “Format my work into yesterday, today, and blockers.”

A model's summary of when it is used.

A model's reading

What it takes when started

[yesterday | today | blockers]

What to type after its name when you start it.

From its settingsline 4

Licence

Apache-2.0, from LICENSE

The terms its author shares it under, which let it be shown here.

From the repositorylicence text

The text

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1---
2name: standup
3description: 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.
4argument-hint: "[yesterday | today | blockers]"
5---
6
7# /standup
8
9> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
11Generate a standup update by pulling together recent activity across your tools.

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

Raw lines 1 to 12
Names a skill status-report :3
13## How It Works
15```
16┌─────────────────────────────────────────────────────────────────┐
17│ STANDUP │
18├─────────────────────────────────────────────────────────────────┤
19│ STANDALONE (always works) │
20│ ✓ Tell me what you worked on and I'll structure it │
21│ ✓ Format for daily standup (yesterday / today / blockers) │
22│ ✓ Keep it concise and action-oriented │
23├─────────────────────────────────────────────────────────────────┤
24│ SUPERCHARGED (when you connect your tools) │
25│ + Source control: Recent commits and PRs │
26│ + Project tracker: Ticket status changes │
27│ + Chat: Relevant discussions and decisions │
28│ + CI/CD: Build and deploy status │
29└─────────────────────────────────────────────────────────────────┘
30```

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                                │
└─────────────────────────────────────────────────────────────────┘
Raw lines 13 to 31
32## What I Need From You
34**Option A: Let me pull it**
35If your tools are connected, just say `/standup` and I'll gather everything automatically.
37**Option B: Tell me what you did**
38"Worked on the auth migration, reviewed 3 PRs, got blocked on the API rate limiting issue."

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

Raw lines 32 to 39
40## Output
42```markdown
43## Standup — [Date]
45### Yesterday
46- [Completed item with ticket reference if available]
47- [Completed item]
49### Today
50- [Planned item with ticket reference]
51- [Planned item]
53### Blockers
54- [Blocker with context and who can help]
55```

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]
Raw lines 40 to 56
57## If Connectors Available
59If **~~source control** is connected:
60- Pull recent commits and PRs (opened, reviewed, merged)
61- Summarize code changes at a high level
63If **~~project tracker** is connected:
64- Pull tickets moved to "in progress" or "done"
65- Show upcoming sprint items
67If **~~chat** is connected:
68- Scan for relevant discussions and decisions
69- Flag threads needing your response

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
Raw lines 57 to 70
Uses an outside tool ~~source :59
Uses an outside tool ~~project :63
Uses an outside tool ~~chat :67
71## Tips
731. **Run it every morning** — Build a habit and never scramble for standup notes.
742. **Add context** — After I generate, add any nuance about blockers or priorities.
753. **Share format** — Ask me to format for Slack, email, or your team's standup tool.

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.
Raw lines 71 to 75

From anthropics/knowledge-work-plugins at 2574e29, 2026-10-27. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.