$npx -y skills add vouchdev/vouch --skill vouch-askAnswer a question from the vouch KB with citations, or say what's missing
| 1 | # /vouch-ask |
| 2 | |
| 3 | Answer "$ARGUMENTS" using only reviewed knowledge from the vouch KB. Every |
| 4 | statement in the answer must carry a `[claim-id]` or `[source-id]` citation. |
| 5 | |
| 6 | Steps: |
| 7 | |
| 8 | 1. Call `kb_search` with `query: "$ARGUMENTS"`, then `kb_context` on the same |
| 9 | query to assemble the working set. |
| 10 | 2. If the results answer the question, write the answer citing every claim id |
| 11 | you relied on. Use `kb_read_page` for typed record detail (contacts, |
| 12 | project records, followups). |
| 13 | 3. If the KB cannot support an answer, say so plainly and list the closest |
| 14 | claims found. Do not fill gaps from your own knowledge — an uncited answer |
| 15 | is worse than no answer. |
| 16 | 4. Only when the user explicitly asks about in-flight knowledge, list |
| 17 | `kb_list_pending` items — each labeled `UNREVIEWED` — after the cited |
| 18 | answer, never mixed into it. |
| 19 | |
| 20 | Never call `kb_approve`. Never restate pending proposals as facts. |