standup-formatter
Use when generating standup reports, daily updates, or team status summaries. Formats work activity into concise standup format.
Best use case
standup-formatter is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Use when generating standup reports, daily updates, or team status summaries. Formats work activity into concise standup format.
Use when generating standup reports, daily updates, or team status summaries. Formats work activity into concise standup format.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "standup-formatter" skill to help with this workflow task. Context: Use when generating standup reports, daily updates, or team status summaries. Formats work activity into concise standup format.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/standup-formatter/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How standup-formatter Compares
| Feature / Agent | standup-formatter | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when generating standup reports, daily updates, or team status summaries. Formats work activity into concise standup format.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
<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
```markdown
## Standup - [Date]
### Done
- [Completed item 1]
- [Completed item 2]
### Today
- [Focus item 1]
- [Focus item 2]
### Blockers
- [Blocker with specific need] / None
```
## Team Standup
```markdown
## Team Standup - [Date]
### [Person 1]
- Done: [summary]
- Today: [focus]
- Blockers: [if any]
### [Person 2]
...
```
</templates>Related Skills
standup-meeting
Conduct effective daily standup meetings for agile teams. Use when facilitating standups, tracking blockers, or improving team synchronization. Handles standup format, time management, and blocker resolution.
team-collaboration-standup-notes
You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns.
lark-workflow-standup-report
日程待办摘要：编排 calendar +agenda 和 task +get-my-tasks，生成指定日期的日程与未完成任务摘要。适用于了解今天/明天/本周的安排。
enact-json-formatter
Formats and prettifies JSON with configurable indentation
enact-formatter
Formats and prettifies JSON with configurable indentation
code-formatter
Automatically format code across multiple languages with opinionated configurations.
azure-quotas
Check/manage Azure quotas and usage across providers. For deployment planning, capacity validation, region selection. WHEN: "check quotas", "service limits", "current usage", "request quota increase", "quota exceeded", "validate capacity", "regional availability", "provisioning limits", "vCPU limit", "how many vCPUs available in my subscription".
raindrop-io
Manage Raindrop.io bookmarks with AI assistance. Save and organize bookmarks, search your collection, manage reading lists, and organize research materials. Use when working with bookmarks, web research, reading lists, or when user mentions Raindrop.io.
zlibrary-to-notebooklm
自动从 Z-Library 下载书籍并上传到 Google NotebookLM。支持 PDF/EPUB 格式，自动转换，一键创建知识库。
discover-skills
当你发现当前可用的技能都不够合适（或用户明确要求你寻找技能）时使用。本技能会基于任务目标和约束，给出一份精简的候选技能清单，帮助你选出最适配当前任务的技能。
web-performance-seo
Fix PageSpeed Insights/Lighthouse accessibility "!" errors caused by contrast audit failures (CSS filters, OKLCH/OKLAB, low opacity, gradient text, image backgrounds). Use for accessibility-driven SEO/performance debugging and remediation.
project-to-obsidian
将代码项目转换为 Obsidian 知识库。当用户提到 obsidian、项目文档、知识库、分析项目、转换项目 时激活。 【激活后必须执行】： 1. 先完整阅读本 SKILL.md 文件 2. 理解 AI 写入规则（默认到 00_Inbox/AI/、追加式、统一 Schema） 3. 执行 STEP 0: 使用 AskUserQuestion 询问用户确认 4. 用户确认后才开始 STEP 1 项目扫描 5. 严格按 STEP 0 → 1 → 2 → 3 → 4 顺序执行 【禁止行为】： - 禁止不读 SKILL.md 就开始分析项目 - 禁止跳过 STEP 0 用户确认 - 禁止直接在 30_Resources 创建（先到 00_Inbox/AI/） - 禁止自作主张决定输出位置