agentsclimarketplace

Standup update

Skill openagentskills/betterskills/skills/productivity/standup-update

Portable, open catalogue of agent skills for Cursor, Claude Code, Windsurf, Copilot, and other AI coding assistants.

Install
npx -y skills add openagentskills/betterskills --skill standup-update

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

One thing to look at

  • 0 stars0 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

Turns raw notes or bullet dumps into a concise standup update with yesterday, today, and blockers sections. Use when the user asks for a daily update, standup summary, or to summarize what they did yesterday for Slack or Teams.

SKILL.md

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

Standup / Daily Update Writer

Quick start

  1. Collect raw notes: commits, tickets, bullets, or voice-to-text dumps.
  2. Sort items into yesterday (done), today (planned), and blockers.
  3. Keep each section to 2–5 bullets; lead with outcomes, not activity.
  4. Output in the template below unless the user requests a different format.

Output template

**Yesterday**
- [Completed outcome or deliverable]
- [Another completed item]

**Today**
- [Planned focus or next step]
- [Another planned item]

**Blockers**
- [Blocker with who/what is needed] — or "None"

Writing rules

  • Yesterday — Past tense; emphasize results ("shipped login fix") not process ("worked on login").
  • Today — Present or future tense; one primary focus per bullet.
  • Blockers — Be specific: dependency, decision, access, or person needed. Omit fluff.
  • Length — Default to three sections only; skip optional sections unless asked.
  • Tone — Direct and scannable for async channels (Slack, Teams, email).

Optional variants

If the user asks for a shorter format:

Done: [item 1]; [item 2]
Next: [item 1]; [item 2]
Blocked: [blocker] or None

If the user asks for a team-wide roll-up, group by person or squad using the same three sections.

Example

Input

- fixed the jwt bug in staging
- pr waiting on review from alex
- need db migration approved before prod deploy
- today want to finish rate limiting middleware
- also need to prep demo for friday

Output

**Yesterday**
- Fixed JWT validation bug in staging

**Today**
- Finish rate limiting middleware
- Prep demo for Friday

**Blockers**
- PR waiting on review from Alex
- DB migration needs approval before production deploy

Gives 0 of the 12 instructions most note taking skills give in 433 tokens

Counted across 686 of the 876 authors here whose files we hold, read 2026-08-07

  • include a visual element on every slidein 44 of 686, across 13 files
  • use wikilinks for internal vault linksin 36 of 686, across 12 files
  • commit to a single visual motif across every slidein 34 of 686, across 9 files
  • use subagents to visually inspect rendered slidesin 31 of 686, across 7 files
  • read pptxgenjs guide before creating presentations from scratchin 30 of 686, across 6 files
  • keep 0.5 inch minimum marginsin 30 of 686, across 7 files
  • re-verify affected slides after every fixin 27 of 686, across 5 files
  • run content QA checks before declaring successin 26 of 686, across 3 files
  • Use Markdown links for external URLs onlyin 26 of 686, across 11 files
  • pick a bold topic specific color palettein 24 of 686, across 2 files
  • read editing guide before editing existing presentationsin 23 of 686, across 1 file
  • use one dominant color across all slidesin 23 of 686, across 1 file

Said here and by no other author read

  • collect raw notes from any source
  • sort items into yesterday, today, and blockers
  • limit each section to 2-5 bullets
  • lead bullets with outcomes, not process activity
  • write yesterday items in past tense
  • specify the dependency or person needed for blockers

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. 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.