vouch-ask

スター156

フォーク60

更新日2026年7月4日 04:17

Answer a question from the vouch KB with citations, or say what's missing

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

vouchdev

vouchdev/vouch

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

/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:

Call kb_search with query: "$ARGUMENTS", then kb_context on the same query to assemble the working set.
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).
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.
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.

このリポジトリの他の Skills

同じリポジトリ

vouch-followup

vouchdev/vouch

Propose a dated followup the vouch digest will surface until closed

2026-07-04156

vouch-record

vouchdev/vouch

Propose a typed record (contact, org, project) into the vouch KB

2026-07-04156

vouch-remember

vouchdev/vouch

File something the user wants remembered as a cited, review-gated proposal

2026-07-04156

vouch-standup

vouchdev/vouch

Narrate the vouch digest — pending reviews, decisions, stale claims, due followups

2026-07-04156

vouch-propose-from-pr

vouchdev/vouch

Distill a merged PR into vouch claim proposals

2026-07-02156

vouch-recall

vouchdev/vouch

Recall what the project's vouch KB knows about a topic

2026-07-02156

name	vouch-ask
description	Answer a question from the vouch KB with citations, or say what's missing

/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:

Call kb_search with query: "$ARGUMENTS", then kb_context on the same query to assemble the working set.
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).
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.
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.