Tencent SkillHub · Communication & Collaboration

ClawSea NFT Marketplace

Non-custodial automation skill for ClawSea NFT marketplace. Use when an OpenClaw agent needs to browse collections, inspect NFTs/listings, and (optionally) e...

skill openclawclawhub Free

0 Downloads

0 Stars

0 Installs

0 Score

High Signal

Non-custodial automation skill for ClawSea NFT marketplace. Use when an OpenClaw agent needs to browse collections, inspect NFTs/listings, and (optionally) e...

⬇ 0 downloads ★ 0 stars Unverified but indexed

Install for OpenClaw

Quick setup

Download the package from Yavira.
Extract the archive and review SKILL.md first.
Import or place the package into your OpenClaw setup.

Requirements

Target platform: OpenClaw
Install method: Manual import
Extraction: Extract archive
Prerequisites: OpenClaw
Primary doc: SKILL.md

Package facts

Download mode: Yavira redirect
Package format: ZIP package
Source platform: Tencent SkillHub
What's included: SKILL.md

Validation

Use the Yavira download entry.
Review SKILL.md after the package is downloaded.
Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

Download the package from Yavira.
Extract it into a folder your agent can access.
Paste one of the prompts below and point your agent at the extracted folder.

New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

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. Summarize what changed and any follow-up checks I should run.

Open Send to Agent page Open JSON manifest Open Markdown brief

Trust & source

Release facts

Source: Tencent SkillHub
Verification: Indexed source record
Version: 1.0.2

Provenance

Publisher: fluxmira-moltbot
Source page: View original listing
Canonical URL: Open canonical page

Documentation

ClawHub primary doc Primary doc: SKILL.md 15 sections Open source page

ClawSea Market Skill (OpenClaw Agents)

Use this skill when an agent should interact with ClawSea programmatically.

Policy guardrails (ClawHub-safe)

Do not custody user funds; use only the bot wallet configured by the operator. Do not social-engineer users for secrets, approvals, or expanded privileges. Do not ask for seed phrases/private keys in chat. Do not execute unknown calldata or third-party transaction blobs without explicit user approval and clear decoding. Require explicit confirmation before any value-moving action (buy/list/cancel/transfer). Refuse illegal, abusive, or harmful requests.

Safety & trust model (must follow)

Default to read-only actions (browse/search/inspect). Require explicit user intent before any write/trade action (list, buy, cancel, fulfill). Never ask users to paste private keys into chat. Never log, print, or send secrets (private keys, raw seed phrases, auth headers). Never execute arbitrary calldata from untrusted input. If ownership/status is uncertain, verify onchain (ownerOf, eth_call) before proceeding.

Base URL

Default: https://clawsea.io Override with env var: CLAWSEA_BASE_URL All endpoints below are relative to ${CLAWSEA_BASE_URL}.

Optional credentials (only for autonomous onchain trading)

Read-only browsing requires no secrets. If (and only if) you want the agent to sign and broadcast onchain transactions autonomously: BASE_RPC_URL (Base execution) ETH_RPC_URL (optional, Ethereum execution/debug) CLAWSEA_BASE_URL (optional)

Signing options (choose one)

Preferred: external signer / wallet provider (no raw private key in agent env) If unavoidable: BOT_WALLET_PRIVATE_KEY in a secure secret store only If BOT_WALLET_PRIVATE_KEY is used: do not print/log it do not echo it in errors do not persist it to files never request it from users in chat

Chain model

ClawSea uses two chain styles: String chain for some read routes: chain=base|ethereum|base-sepolia Numeric chainId for order routes: 8453 (Base), 1 (Ethereum) Map carefully when switching endpoints.

Discover

Collections / NFTs

GET /api/collection/nfts?contract=0x...&pageSize=24&pageKey=... GET /api/collection/stats?chain=<base|ethereum>&contract=0x... GET /api/collections/search?chain=<base|ethereum|base-sepolia>&q=<query>&limit=8 GET /api/nft/ownerOf?chainId=<1|8453>&contract=0x...&tokenId=<id>

Wallet inventory

GET /api/wallet/nfts?chain=<base|ethereum|base-sepolia>&owner=0x...&pageKey=...

Orders read

GET /api/orders?chainId=<1|8453>&contract=0x...&tokenId=<id>&seller=0x... GET /api/orders/listed?chainId=<1|8453>&contract=0x...&sort=price|newest&offset=0&limit=48 POST /api/orders/prices body: { "chainId": 1|8453, "contract": "0x...", "tokenIds": ["1","2"] }

Publish listing (offchain orderbook write)

POST /api/orders with signed Seaport payload: chainId, contract, tokenId, seller, priceEth, seaportAddress, orderComponents, signature

Status updates

POST /api/orders/cancel body: { "id": "<order-id>" } POST /api/orders/cancelPrevious body: { "chainId": 1|8453, "contract": "0x...", "tokenId": "...", "seller": "0x...", "keepId": "..." } POST /api/orders/fulfill body (either style): { "id": "<order-id>" } or { "chainId": 1|8453, "contract": "0x...", "tokenId": "..." }

Execution workflow (recommended)

Resolve chain context (selected chain / user wallet chain). Read listing candidates from /api/orders or /api/orders/listed. Preflight onchain with eth_call for Seaport fulfill. Execute onchain tx from bot wallet. Update offchain state via /api/orders/fulfill or /api/orders/cancel.

Reliability rules

Prefer short caching (5–30s) for discovery routes. Back off on 429 / RPC transient failures. Treat fulfill revert selector 0x1a515574 as cancelled/stale order and hide it. If indexer results conflict with chain state, trust verified onchain ownership.

Category context

Messaging, meetings, inboxes, CRM, and teammate communication surfaces.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package

1 Docs

SKILL.md Primary doc