Coinbase OpenAPI Skill
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This skill is transparent about using Coinbase, but it can use stored Coinbase keys to read accounts and place or cancel live trades without a clearly enforced confirmation or limit policy.
Install only if you want an agent to operate Coinbase Advanced Trade. Use a least-privilege Coinbase API key, keep it read-only unless you truly need trading, require manual approval for every live order or cancellation, and consider pinning or locally reviewing the OpenAPI schema before linking it through UXC.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If run with a Coinbase key that has trading permissions, the agent could place or cancel real trades that affect the user's funds.
These documented commands can create and cancel real Coinbase orders. The artifacts acknowledge high-risk writes, but do not require explicit user confirmation, dry-run/sandbox mode, or spend/order limits before execution.
# Create a live limit order coinbase-openapi-cli post:/api/v3/brokerage/orders ... # Cancel orders in batch coinbase-openapi-cli post:/api/v3/brokerage/orders/batch_cancel ...
Use read-only Coinbase keys unless trading is required, require manual approval for every order or cancellation, and verify product, side, size, price, and order IDs before allowing execution.
A credential with broad Coinbase permissions could allow account reads and trading actions through this skill.
The skill intentionally uses Coinbase API key material and a private key to mint request-scoped JWTs for private account and order endpoints. This is expected for the stated purpose, but it is sensitive account authority.
Private account and order endpoints require a Coinbase Advanced Trade bearer JWT... Store those values in a local credential... --field private_key=env:COINBASE_PRIVATE_KEY
Create a least-privilege Coinbase API key, prefer read-only permissions unless trading is necessary, protect the private key, and revoke the credential when no longer needed.
A changed remote schema could affect which Coinbase operations the linked CLI exposes, which matters for a financial trading integration.
The default link command fetches the OpenAPI schema from GitHub's mutable main branch. Future schema changes could alter the operations exposed through UXC.
uxc link coinbase-openapi-cli https://api.coinbase.com --schema-url https://raw.githubusercontent.com/holon-run/uxc/main/skills/coinbase-openapi-skill/references/coinbase-advanced-trade.openapi.json
Prefer the reviewed local schema or a pinned commit/tag URL, and re-check the schema before enabling trading permissions.