Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Interact with DECK-0 digital collectibles platform to browse collections, buy card packs, open packs, view leaderboards, and apply as a publisher. Use when the user asks to collect trading cards, purchase NFT packs, manage their collection, or create their own card collection.
Interact with DECK-0 digital collectibles platform to browse collections, buy card packs, open packs, view leaderboards, and apply as a publisher. Use when the user asks to collect trading cards, purchase NFT packs, manage their collection, or create their own card collection.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
DECK-0 is a digital collectibles platform where users collect trading cards organized in albums. This skill enables agents to: Browse the shop and view collection details Buy card packs via smart contract transactions Open packs to reveal cards Track collection progress and leaderboard rankings Publish โ apply to create your own card collection Base URL: https://app.deck-0.com OpenAPI Spec: GET /api/agents/v1/openapi (no auth required)
Use this wallet resolution order when signing API requests or sending transactions: Existing agent wallet provided by the runtime Existing Base wallet provided by the runtime DECK0_PRIVATE_KEY fallback (only when neither wallet above exists) Fallback setup for step 3: export DECK0_PRIVATE_KEY="0x..." Optional fallback chain override (used only for API auth signature verification; contract operations use the chain from the collection/price response and your RPC selection): export DECK0_CHAIN_ID=8453 Install Foundry using a reviewed method (for example Homebrew), then verify cast is available: brew install foundry cast --version Also uses: curl, jq, shasum (standard on macOS/Linux). Note: The declared requirements (cast, curl, jq, shasum, DECK0_PRIVATE_KEY) are needed for fallback signing and for buy/open flows. Browse-only usage with a runtime-provided wallet may not require DECK0_PRIVATE_KEY or cast. The wallet needs native tokens (APE on Apechain, ETH on Base) to buy packs.
Prefer runtime-provided wallets whenever available. DECK0_PRIVATE_KEY is highly sensitive. Only use it as a fallback when the user explicitly approves and the task requires signing or transactions. Never print, log, or echo private key values.
EndpointMethodDescription/api/agents/v1/shop/albumsGETBrowse available collections/api/agents/v1/collections/{address}GETGet collection details/api/agents/v1/collections/{address}/leaderboardGETView leaderboard rankings/api/agents/v1/collections/{address}/priceGETGet signed price for purchasing/api/agents/v1/me/albumsGETList your collections/api/agents/v1/me/albums/{address}GETYour progress on a collection/api/agents/v1/me/packsGETList your packs/api/agents/v1/me/cardsGETList your cards/api/agents/v1/me/pack-opening/{hash}GETGet pack opening recap/api/agents/v1/publisher/applicationGETCheck publisher application status/api/agents/v1/publisher/applicationPOSTSubmit publisher application/api/agents/v1/openapiGETOpenAPI specification (no auth) See endpoints.md for complete request/response schemas.
All endpoints (except /openapi) require EIP-191 wallet-signed requests via custom headers: HeaderDescriptionX-Agent-Wallet-AddressLowercase wallet addressX-Agent-Chain-IdNumeric EVM chain ID used for authenticationX-Agent-TimestampUnix timestamp in millisecondsX-Agent-NonceUnique string, 8-128 charactersX-Agent-SignatureEIP-191 signature of canonical payload The canonical payload to sign: deck0-agent-auth-v1 method:{METHOD} path:{PATH} query:{SORTED_QUERY} body_sha256:{SHA256_HEX} timestamp:{TIMESTAMP} nonce:{NONCE} chain_id:{CHAIN_ID} wallet:{WALLET} See auth.md for the full signing flow with code examples.
Buying and opening packs are on-chain operations: Buy packs: Call GET /api/agents/v1/collections/{address}/price to get a signed price, then call mintPacks() on the album contract with the signature and payment value. Open packs: Call openPacks(packIds) on the album contract to reveal cards, then poll GET /api/agents/v1/me/pack-opening/{txHash}?chainId=... every 5 seconds to get the recap with card details and badges. Payment formula: value = (packPrice * priceInNative * quantity) / 100 See smart-contracts.md for ABI, payment calculations, and code examples.
NetworkChain IDCurrencyBlock ExplorerApechain Mainnet33139APEhttps://apescan.ioBase8453ETHhttps://basescan.org
All responses follow a standard envelope: // Success { "success": true, "data": { ... }, "share": { "url": "...", "imageUrl": "..." } } // Error { "success": false, "error": { "code": "AGENT_...", "message": "...", "details": { ... } } } See errors.md for all error codes and troubleshooting.
Most responses include URLs that link to the DECK-0 web app. Always present these to the user so they can view, share, or explore further in their browser. share.url โ Present on most responses. Links to the relevant page (collection, leaderboard, shop, pack opening recap, etc.). Show this to the user as a shareable link. share.imageUrl โ When available, an image preview URL (e.g., collection cover). Can be used for rich embeds or previews. data.cards[].url โ On pack opening recap responses, each card includes a direct link to its detail page. Show these to the user so they can view or share individual cards.
Per wallet: 60 requests/minute Per IP: 120 requests/minute Rate limit headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, Retry-After) are included on 429 responses.
When the user says: "Show me available card collections" โ Browse shop albums "Tell me about collection 0x..." โ Get collection details "Buy 3 packs from collection 0x..." โ Get signed price, call mintPacks "Open my packs" โ Call openPacks on contract, then poll pack opening recap "What cards did I get?" / "Show my pack opening results" โ Get pack opening recap "How's my collection progress?" โ Get my albums "Show my packs" / "What packs do I have?" โ List my packs "Show my cards" / "What cards do I have?" โ List my cards "Show the leaderboard" โ Get collection leaderboard "Share my pack opening" / "Show me the link to my card" โ Use share.url or cards[].url from the response "I want to create my own card collection" โ Submit publisher application
auth.md โ Full authentication flow, signing code, payload construction endpoints.md โ Complete API reference with all request/response schemas smart-contracts.md โ On-chain operations: minting packs, opening packs, ABI, code examples examples.md โ End-to-end workflow examples with request/response pairs errors.md โ Error codes, rate limiting, troubleshooting
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.