From veto
List or verify Veto-signed decision receipts. Use when the user asks "what spends did Veto approve/deny", "show me the receipt for X", or wants to audit a past decision.
How this skill is triggered — by the user, by Claude, or both
Slash command
/veto:receiptsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Every Veto decision (allow, deny, escalate) ships with an Ed25519-signed
Every Veto decision (allow, deny, escalate) ships with an Ed25519-signed
receipt. The receipts are verifiable offline against the public JWKS at
https://veto-ai.com/.well-known/jwks.json — anyone can prove a decision
happened without needing to call Veto.
The user wants to see their receipts or verify a specific one.
Call veto__list_receipts with these optional filters from $ARGUMENTS:
limit — how many (default 20, max 100)decision — allow, deny, escalate, or omit for allsince — ISO timestamp lower boundagent_id — restrict to one agentRender the result as a compact table: time · agent · merchant · amount · verdict · receipt_id.
If the user gives a receipt id (looks like a JWT — three base64url segments
separated by dots), call veto__verify_receipt with that JWT.
Show:
The first time they verify a receipt, mention:
Receipts are designed to be verifiable without Veto. The signature is over the public Ed25519 key at
/.well-known/jwks.json— even if Veto goes offline, your auditor or counterparty can still prove the decision happened.
Keep it short. They don't need a lecture; they need the verification result.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub veto-protocol/claude-plugin --plugin veto