vouch-ask
SolidAnswer a question from the vouch KB with citations, or say what's missing
AI & Automation 122 stars
64 forks Updated today MIT
Install
Quality Score: 77/100
Stars 20%
Recency 20%
Frontmatter 20%
Documentation 15%
Issue Health 10%
License 10%
Description 5%
Skill Content
# /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:
1. Call `kb_search` with `query: "$ARGUMENTS"`, then `kb_context` on the same
query to assemble the working set.
2. 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).
3. 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.
4. 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.
Details
- Author
- vouchdev
- Repository
- vouchdev/vouch
- Created
- 2 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
AI & Automation Solid
vouch-recall
Recall what the project's vouch KB knows about a topic
122 Updated today
vouchdev AI & Automation Solid
vouch-remember
File something the user wants remembered as a cited, review-gated proposal
122 Updated today
vouchdev AI & Automation Solid
vouch-standup
Narrate the vouch digest — pending reviews, decisions, stale claims, due followups
122 Updated today
vouchdev