mcpbeat

Vouch Ask

vouchdev/vouch-ask

Answer a question from the vouch KB with citations, or say what's missing

253 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-ask

The instruction itself

1 sections, as written by the author

/vouch-ask

Answer "$ARGUMENTS" using only reviewed knowledge from the vouch KB. Every

statement in the answer must carry a [claim-id] or [source-id] citation.

Steps:

  • Call kb_search with query: "$ARGUMENTS", then kb_context on the same

query to assemble the working set.

  • If the results answer the question, write the answer citing every claim id

you relied on. Use kb_read_page for typed record detail (contacts,

project records, followups).

  • If the KB cannot support an answer, say so plainly and list the closest

claims found. Do not fill gaps from your own knowledge — an uncited answer

is worse than no answer.

  • Only when the user explicitly asks about in-flight knowledge, list

kb_list_pending items — each labeled UNREVIEWED — after the cited

answer, never mixed into it.

Never call kb_approve. Never restate pending proposals as facts.

How to use it

Copy the folder

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