vouch-record
Propose a typed record (contact, org, project) into the vouch KB
npx skills add vouchdev/vouch --skill vouch-record --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-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: 1. Decide the record shape: person -> entity type `person` + `contact` page (frontmatter: `role`, optional `org`, `email`); organisation -> `company` entity + `org` page; project -> `project` entity + `project-record` page (frontmatter: `record_status`, optional `owner`). 2. Call `kb_search` first — if the entity already exists, propose only the page update (pass the existing page id as `slug_hint`) instead of a duplicate. 3. Call `kb_propose_entity`, then `kb_propose_page` with `page_type` set to the record kind and the frontmatter in `metadata`. Cite a registered source when the record distills one (register the conversation via `kb_register_source` if the user is dictating facts). 4. Link ownership or membership with `kb_propose_relation` where it's clear. 5. Report every proposal id filed. Never call `kb_approve`. One record per invocation; ask before batching.
What does the vouch-record skill do?
Propose a typed record (contact, org, project) into the vouch KB
How do I install it?
Run `npx skills add vouchdev/vouch --skill vouch-record --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.