Menu
Attestation skill for lobster.cash wallet operations
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
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.
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 | lobster-cash |
| version | 0.1.0 |
| description | Attestation skill for lobster.cash wallet operations |
| metadata | {"compatible_wallets":["lobster.cash"],"requires_bins":["treeship","lobstercash"]} |
This skill delegates wallet operations to lobster.cash. Transaction execution and final status are handled by lobster.cash. Treeship provides cryptographic attestation for every action so there is a verifiable audit trail.
lobster.cash is the compatible and tested wallet for this skill.
Before any session begins, verify the following:
treeship --version and confirm the installed version meets the minimum requirement.lobstercash --help and confirm the binary is on PATH and responds.lobstercash balance and confirm the wallet responds with a valid balance object.If any preflight check fails, halt and report the missing dependency. Do not attempt to work around a missing binary.
Start a Treeship session before performing any wallet operation:
treeship session start --skill lobster-cash
The session ID is used to group all attestations for this interaction.
Every action that touches the wallet must be wrapped with treeship wrap so it is cryptographically attested:
treeship wrap <command>
This produces a signed attestation record that includes the command, timestamp, actor, and result hash.
Follow these five steps in order for every payment:
Parse the user request to identify the payment type (send, card, or x402) and the amount, recipient, and currency.
Present the parsed intent to the human approver. Do not proceed until explicit approval is received. Log the approval attestation.
Run the appropriate command through treeship wrap:
treeship wrap lobstercash send <recipient> <amount> <currency>treeship wrap lobstercash card <merchant> <amount> <currency>treeship wrap lobstercash x402 <url>After execution, verify the transaction landed:
treeship wrap lobstercash tx-status <tx_id>
Report the final status (confirmed, pending, or failed) to the user.
treeship session close
Push the session attestation bundle to the hub.