mcpbeat

Vouch Followup

vouchdev/vouch-followup

Propose a dated followup the vouch digest will surface until closed

254 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-followup

The instruction itself

1 sections, as written by the author

/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:

  • Extract what's owed, by whom, and when. If no due date is stated, ask —

an undated followup never surfaces.

  • 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.

  • 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.

  • Report the proposal id and the due date filed.

Never call kb_approve.

How to use it

Copy the folder

Take vouchdev/vouch-followup 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.