Menu
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.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Attestation skill for lobster.cash wallet operations
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.
Work on the Treeship source repository safely. Use when Codex or another coding agent is asked to modify, review, document, or test the zerkerlabs/treeship repo, especially packages/core, packages/cli, packages/hub, docs, SDKs, MCP bridge, DSSE artifacts, approvals, handoffs, Hub/Dock/DPoP, or cryptographic verification behavior. This skill provides repo scope, required read order, crypto invariants, CLI UX rules, and validation commands for contributors.
| name | treeship-report |
| description | 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. |
| allowed-tools | Bash |
The receipt is the cryptographic artifact that lives in .treeship/sessions/ after treeship session close. The session report is the human-readable page at treeship.dev/receipt/<id> that someone else can open in a browser. Publishing the report uploads the receipt to the Treeship hub and returns the URL.
This is the only step that sends data off the user's machine. Until they ask for a report (or have set auto_push: true in .treeship/config.yaml), every receipt stays local. The receipt is theirs -- publishing is opt-in, per session.
# 1. Make sure the session is closed (skips silently if already sealed by SessionEnd)
treeship session close --headline "<headline>" --summary "<summary>" --review "<review>"
# 2. Upload the sealed receipt and print the report URL
treeship session report
The URL printed by treeship session report is what the user shares. It looks like https://treeship.dev/receipt/art_f7e6d5c4b3a2.
When you hand the URL back to the user, mention that:
treeship verify <url>.This matters because Treeship is local-first. The user owns the source of truth; the hub is a publishing surface, not a custodian.
Some users do not want anything on a hub. Two options:
.treeship/sessions/ssn_<id>.treeship) -- they can attach the file directly to whatever they're sharing through..treeship package directory (.treeship/sessions/ssn_<id>.treeship/) is self-contained — zip and share it; the recipient verifies with treeship package verify <dir>.Either path produces a verifiable receipt without ever calling treeship session report.