vouch-followup
Propose a dated followup the vouch digest will surface until closed
npx skills add vouchdev/vouch --skill vouch-followup --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-followup File "$ARGUMENTS" as a `followup` page proposal — a commitment with a due date that `vouch digest` lists until it's closed. Requires the company-brain page kinds (`vouch init --template company-brain`). Steps: 1. Extract what's owed, by whom, and when. If no due date is stated, ask — an undated followup never surfaces. 2. Call `kb_propose_page` with `page_type: "followup"`, a short imperative title, and `metadata`: `due_at` (ISO date), `followup_status: "open"`, `owner` when known. Put context in the body; cite a source id if the commitment came from a registered conversation or document. 3. To close or move one later: re-propose the same page (`slug_hint: <page id>`) with `followup_status: "done"` (or a new `due_at`) — status changes go through the gate like any other edit. 4. Report the proposal id and the due date filed. Never call `kb_approve`.
What does the vouch-followup skill do?
Propose a dated followup the vouch digest will surface until closed
How do I install it?
Run `npx skills add vouchdev/vouch --skill vouch-followup --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.