vouch-standup
Narrate the vouch digest — pending reviews, decisions, stale claims, due followups
npx skills add vouchdev/vouch --skill vouch-standup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# /vouch-standup Give the user a morning briefing from the KB, then get out of the way. Steps: 1. 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. 2. 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). 3. 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.
What does the vouch-standup skill do?
Narrate the vouch digest — pending reviews, decisions, stale claims, due followups
How do I install it?
Run `npx skills add vouchdev/vouch --skill vouch-standup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From vouchdev/vouch, a repository with 120 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.