Menu
Use when the user shares a Treeship session report URL or a local .treeship receipt file and wants you to confirm it is authentic, the signatures hold, and the recorded actions match what the report claims.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Attestation skill for lobster.cash wallet operations
Use when the user asks for "the URL", "a shareable link", "the proof I can send to <someone>", or otherwise wants the current Treeship session published as a session report on treeship.dev.
Create cryptographic attestations for AI agent actions using Treeship.dev. Use when the user wants to sign agent actions, create verifiable receipts, wrap commands with attestations, verify artifact chains, push artifacts to the Treeship Hub, integrate Treeship into their agent workflow, or capture model/token provenance. Covers the CLI (treeship), Python SDK (treeship-sdk), TypeScript SDK (@treeship/sdk), MCP Bridge (@treeship/mcp), and Hub API (api.treeship.dev). Trigger on any mention of attestation, verifiable receipts, signed receipts, agent trust, Treeship, action signing, cryptographic proof of agent work, model provenance, or token attestation.
Use when operating Hermes Agent in a repo or organization where AI work should produce Treeship-verifiable receipts. Captures Hermes sessions, MCP-routed tool calls, wrapped shell commands, approvals, handoffs, and publishable session reports while avoiding raw secrets in receipts.
Use Treeship (treeship.dev) from Perplexity Computer — install, configure, sign agent actions, verify receipts, push to the Hub, run approval-gated workflows, and work on the zerkerlabs/treeship source repo via GitHub. Trigger on any mention of Treeship, treeship.dev, signed receipts, agent attestation, verifiable agent actions, cryptographic proof of agent work, DSSE artifacts, Merkle proofs, approval-gated actions, session receipts, or the treeship CLI. Also load when asked to contribute to or inspect the zerkerlabs/treeship GitHub repository.
Create cryptographically signed, portable trust receipts for AI agent workflows using Treeship.dev. Use when the user wants to sign agent actions, create verifiable receipts, wrap commands with attestations, verify artifact chains, push artifacts to the Treeship Hub, manage approval-gated actions, or integrate Treeship into their agent workflow. Covers the Treeship CLI (treeship), Python SDK (treeship-sdk), TypeScript SDK (@treeship/sdk), MCP bridge (@treeship/mcp), and Hub API (api.treeship.dev). Trigger on any mention of attestation, verifiable receipts, signed receipts, agent trust, Treeship, action signing, cryptographic proof of agent work, portable receipts, approval workflows, session receipts, Merkle proofs, decision cards, or coverage levels.
| name | treeship-verify |
| description | Use when the user shares a Treeship session report URL or a local .treeship receipt file and wants you to confirm it is authentic, the signatures hold, and the recorded actions match what the report claims. |
| allowed-tools | Bash |
A Treeship receipt is the cryptographic artifact -- the signed evidence of what an agent did. A Treeship session report is the human-readable URL at treeship.dev/receipt/<id> that wraps the receipt with a narrative timeline. Verifying confirms that the report's narrative actually matches its embedded receipt and that the receipt's signatures are valid.
Verification is offline and does not require an account. The verifier ships in the treeship CLI (and as a pure-WASM library at @treeship/verify); it does not phone home.
The user shares something like https://treeship.dev/receipt/art_f7e6d5c4b3a2. Run:
treeship verify https://treeship.dev/receipt/<id>
This downloads the receipt, recomputes the Merkle root, checks every signature against the embedded public key, and prints a per-step breakdown.
Receipts produced by treeship session close live at .treeship/sessions/ssn_*.treeship. Verify any of them with:
treeship package verify .treeship/sessions/ssn_<id>.treeship
This is the same set of cryptographic checks, run entirely locally. No network. Use this when the user wants to confirm a receipt without trusting the hub at all.
treeship hub attach and the certificate flow.Surface the per-step failure verbatim from the CLI output. The most common causes:
Do not gloss over a verification failure. If the receipt does not verify, the report is not trustworthy and the user needs to know.