ClawHub

Tator Trader - AI Trading

v1.0.6

Execute crypto trades using natural language via Tator's AI trading API. Use when: buying tokens, selling tokens, swapping, bridging cross-chain, sending tok...

⭐ 0· 610·2 current·2 all-time
byNinja Dev (QI)@azep-ninja
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
✓
Purpose & Capability
Name/description match the instructions: SKILL.md describes building unsigned trade/bridge/transfer/perp transactions and sending them to an external endpoint (x402/Quick Intel). Operations, supported chains, and payment details align with a transaction-builder service. The file recommends wallet integrations (Sponge, AgentWallet) but these are optional suggestions rather than required credentials.
ℹ
Instruction Scope
The instructions direct the agent to post prompts to an external API (https://x402.quickintel.io/v1/tator/prompt), handle 402 PAYMENT-REQUIRED headers, construct PAYMENT-SIGNATURE payloads, and verify unsigned transactions before signing. This is within the skill's stated purpose, but it exposes the agent/user to signing/payment flows — the doc repeatedly warns not to paste private keys and recommends dedicated hot wallets. The SKILL.md also directs use of a separate quickintel-scan skill for token scans (additional cost).
✓
Install Mechanism
This is instruction-only with no install spec and no code files — lowest install risk. There are no downloads, binaries, or extraction steps.
ℹ
Credentials
The registry declares no required environment variables or credentials. SKILL.md recommends optional wallet integrations (SPONGE_API_KEY, AGENTWALLET_API_TOKEN) and describes programmatic signing patterns, but those are optional and not declared as required. This is a minor mismatch worth noting: if you wire an agent to programmatically sign payments you will need wallet tokens/keys — the documentation warns about using dedicated hot wallets and avoiding main-wallet keys.
✓
Persistence & Privilege
always:false and no special persistence or cross-skill config modification. The skill does not request elevated agent-level privileges or permanent inclusion.
Assessment
This skill appears to do what it says: build unsigned crypto transactions via an external Tator/x402 API and describe how to pay the $0.20 request fee. Before installing or using it, understand the following: (1) the skill posts prompts to an external endpoint (x402.quickintel.io) and payment requires signing a small authorization — never paste your private key or seed phrase into the agent; (2) if you plan to enable programmatic signing, use a dedicated hot wallet with minimal funds and isolate that wallet's keys/tokens from your main holdings; (3) the SKILL.md recommends optional wallet API tokens (SPONGE_API_KEY, AGENTWALLET_API_TOKEN) but the registry doesn't declare them as required — only provide such keys if you trust the wallet provider and understand its permissions; (4) always manually verify every returned unsigned transaction (to, value, chainId, calldata/approval checks) before signing and broadcasting; and (5) be aware that using the skill can incur external costs (x402 $0.20 per request and optional quickintel-scan $0.03). If you need higher assurance, ask the skill author for a canonical homepage/repository and a privacy/security audit of the x402 payment flow.

Like a lobster shell, security has layers — review code before you run it.

aivk97a2tqdm9jr6ehjy7v4krz7n581fr4gbridgevk97a2tqdm9jr6ehjy7v4krz7n581fr4gdefivk97a2tqdm9jr6ehjy7v4krz7n581fr4glatestvk9794mk7h7fbbvytcx2k5bntw181zbdaperpsvk97a2tqdm9jr6ehjy7v4krz7n581fr4gswapvk97a2tqdm9jr6ehjy7v4krz7n581fr4gtradingvk97a2tqdm9jr6ehjy7v4krz7n581fr4gx402vk97a2tqdm9jr6ehjy7v4krz7n581fr4gyieldvk97a2tqdm9jr6ehjy7v4krz7n581fr4g

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments