agentsclimarketplace

Standup formatter

Skill bg-szy/TOP-SKILLS/skills/marketplace/standup-formatter

全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能,提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard

Install
npx -y skills add bg-szy/TOP-SKILLS --skill standup-formatter

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when generating standup reports, daily updates, or team status summaries. Formats work activity into concise standup format.

SKILL.md

2.0 KB, 506 tokens by cl100k_base, as published. Nobody here has run it

<essential_principles>

Standup Philosophy

Purpose

Standups exist to:

  1. Share blockers that need help
  2. Coordinate on dependencies
  3. Keep work visible

Standups do NOT exist to:

  • Report hours worked
  • Justify existence
  • Detail every task

The Ideal Standup

Done: What you completed (outcomes, not activities) Today: What you're working on (1-2 focus items) Blockers: What's preventing progress (specific, actionable)

Time Budgets

  • Speaking: 60 seconds max per person
  • Written: 3-5 bullet points total
  • Detail level: Enough to understand, not to replicate

Format Guidelines

Good Examples

Done: Merged PR for user auth (#234)
Today: Starting payment integration
Blockers: Waiting on API spec from backend team

Bad Examples

Done: Worked on stuff, had meetings, reviewed some code,
      wrote tests, fixed bugs, updated docs, etc.
Today: More of the same
Blockers: Nothing

Async vs Sync

Async (written):

  • More detail acceptable
  • Include links to PRs/tickets
  • Post by 9am team time

Sync (spoken):

  • Extremely concise
  • No reading from notes
  • Save details for follow-ups </essential_principles>
<intake> What standup format do you need?
  1. Individual - Your personal standup
  2. Team - Aggregate team status
  3. Project - Status for specific project

For what timeframe?

  • Yesterday/today (daily)
  • This week (weekly)
  • Custom dates

Source data?

  • Git activity
  • Calendar events
  • Manual input </intake>
<templates> ## Individual Standup
## Standup - [Date]

### Done
- [Completed item 1]
- [Completed item 2]

### Today
- [Focus item 1]
- [Focus item 2]

### Blockers
- [Blocker with specific need] / None

Team Standup

## Team Standup - [Date]

### [Person 1]
- Done: [summary]
- Today: [focus]
- Blockers: [if any]

### [Person 2]
...
</templates>

What ships with it: 1 file

13.0 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,984. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.