mcpbeat

Vouch Standup

vouchdev/vouch-standup

Narrate the vouch digest — pending reviews, decisions, stale claims, due followups

226 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
120
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/vouchdev/vouch --skill vouch-standup

The instruction itself

1 sections, as written by the author

/vouch-standup

Give the user a morning briefing from the KB, then get out of the way.

Steps:

  • Call the kb_digest MCP tool (or run vouch digest --format markdown

via Bash if MCP is unavailable). Default window is fine unless the user

names one.

  • Narrate it in four short lines, leading with counts: pending proposals

(oldest first — nudge vouch review if any), decisions since the window

start, stale claims worth a kb_confirm or supersede, and followups due

(with owners).

  • If a followup in the list is done, offer to file the close — a

kb_propose_page with the page's id as slug_hint and

followup_status: "done" — but only on explicit confirmation.

Read-only otherwise. Never call kb_approve; reviewing is the human's job.

How to use it

Copy the folder

Take vouchdev/vouch-standup from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.