Vouch record
A git-native, review-gated knowledge base for AI agents: they propose writes, you approve them. Every claim cites a source, every change is a diff in your repo. MCP + CLI.
npx -y skills add vouchdev/vouch --skill vouch-recordAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Propose a typed record (contact, org, project) into the vouch KB
SKILL.md
1.2 KB, as published. Nobody here has run it
/vouch-record
File "$ARGUMENTS" as a typed record: an entity plus a kind-validated page,
both as pending proposals. Requires the company-brain page kinds
(vouch init --template company-brain; check with vouch schema list).
Steps:
- Decide the record shape: person -> entity type
person+contactpage (frontmatter:role, optionalorg,email); organisation ->companyentity +orgpage; project ->projectentity +project-recordpage (frontmatter:record_status, optionalowner). - Call
kb_searchfirst — if the entity already exists, propose only the page update (pass the existing page id asslug_hint) instead of a duplicate. - Call
kb_propose_entity, thenkb_propose_pagewithpage_typeset to the record kind and the frontmatter inmetadata. Cite a registered source when the record distills one (register the conversation viakb_register_sourceif the user is dictating facts). - Link ownership or membership with
kb_propose_relationwhere it's clear. - Report every proposal id filed.
Never call kb_approve. One record per invocation; ask before batching.