Your AI assistant is smart. It is also unarmed. It can reason about your codebase, your data, and your APIs, but it cannot touch any of them. Zambo's agent skills change that: three installable skill files that give your assistant real execution tools, a verifiable receipt for every call, and a memory that survives switching assistants.
The skills live at https://zambo.dev/skills/. Here is what each one does.
zambo: give your AI hands
The flagship skill connects your assistant to Zambo's execution layer. Install it and your AI can call live tools: prices, site audits, lead research, prompt checks, and more. The default tool list is 12 focused tools, verified against the live MCP endpoint on September 22, 2026, with 100+ more available behind capability search when the job needs a specialist.
Every call returns a verifiable receipt. More on that below.
npx zambo install
Or the per-skill install, exactly as published on the hub:
mkdir -p ~/.claude/skills/zambo && curl -sL https://zambo.dev/skills/zambo/SKILL.md -o ~/.claude/skills/zambo/SKILL.md
Full page: https://zambo.dev/skills/zambo/
zambo-receipt: prove the work happened
This skill teaches your AI to mint and verify execution receipts. Every Zambo tool call returns one: a UUID, the tool name, a UTC timestamp, a SHA-256 hash of the exact output bytes, an execution status, and a public verification URL. Open the URL, recompute the hash over the output bytes, and compare. No account is needed to check.
The honesty contract is the part worth reading twice. A receipt proves a specific tool ran with specific inputs at a specific time, and that the quoted output is exactly what came back, byte for byte. It does not prove the output is correct, and it does not prove anything outside the recorded call. That boundary is the reason the receipt is useful. It is evidence, not marketing.
mkdir -p ~/.claude/skills/receipt && curl -sL https://zambo.dev/skills/receipt/SKILL.md -o ~/.claude/skills/receipt/SKILL.md
Full page: https://zambo.dev/skills/receipt/
zambo-cross-ai: start in one assistant, finish in another
Every Zambo call takes a stable _session_id. Pass mode: "continue" with the same _session_id in a different assistant and the work resumes where it stopped. Pass mode: "verify" and the new assistant can inspect exactly what already ran before touching anything. The journal_log tool stores milestones, decisions, and open threads, so Friday's session in one assistant becomes Monday's session in another with the full thread intact.
mkdir -p ~/.claude/skills/cross-ai && curl -sL https://zambo.dev/skills/cross-ai/SKILL.md -o ~/.claude/skills/cross-ai/SKILL.md
Full page: https://zambo.dev/skills/cross-ai/
What the AI Agent Execution Receipt (AER-1) is (and is not)
AER-1 stands for AI Agent Execution Receipt. It is an open draft RFC with a live reference implementation, not a finalized standard, and it does not pretend to be one. The draft lives at https://zambo.dev/aer-1/.
Pricing
The skills are free to install. Zambo's free tier is 20 calls per tool per day with no account. The hub's FAQ lists Claude, Cursor, Codex, Windsurf, and Cline as supported assistants.
Related reading
- What Is an AI Agent Execution Receipt? https://dev.to/rambozambo/what-is-an-ai-agent-execution-receipt-3io8
- Whole-Job Receipts: One Checkable Timeline for Every AI Tool Call https://dev.to/rambozambo/whole-job-receipts-one-checkable-timeline-for-every-ai-tool-call-95b
- How to Verify Your AI Agent Actually Completed the Task https://dev.to/rambozambo/how-to-verify-your-ai-agent-actually-completed-the-task-4e12
- The full receipt series: https://dev.to/rambozambo
Top comments (0)