vouch-remember
File something the user wants remembered as a cited, review-gated proposal
npx skills add vouchdev/vouch --skill vouch-remember --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-remember Turn "$ARGUMENTS" into durable KB knowledge — proposed, never self-approved. Steps: 1. Call `kb_register_source` with the user's exact wording as `content` (`source_type: "message"`, a short descriptive `title`). Sources are evidence intake; registering one writes no knowledge. 2. Distill the durable fact(s) into one `kb_propose_claim` each, citing the registered source id in `evidence`. Keep each claim one sentence, present tense, self-contained. 3. If the fact is about a person, org, or project the KB doesn't know yet, also file `kb_propose_entity` (and `kb_propose_relation` to link it). 4. Report the proposal id(s) and remind the user: pending items are invisible to retrieval until a human runs `vouch approve <id>` or `vouch review`. Never call `kb_approve` — the human at the gate decides what the KB believes.
What does the vouch-remember skill do?
File something the user wants remembered as a cited, review-gated proposal
How do I install it?
Run `npx skills add vouchdev/vouch --skill vouch-remember --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.