Uniswap Agent Otc Trade

AdvisoryAudited by Static analysis on Apr 30, 2026.

Overview

No suspicious patterns detected.

Findings (0)

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.

ConcernMedium Confidence
ASI02: Tool Misuse and Exploitation
What this means

A mistaken or over-broad invocation could execute an unwanted trade, move tokens, create a cross-chain intent, or incur fees.

Why it was flagged

These tools can initiate token swaps and cross-chain settlement intents. Those actions can move assets and incur irreversible on-chain effects; the provided visible artifacts do not clearly bound execution with a required final approval, amount cap, chain cap, or signing boundary.

Skill content
allowed-tools: ... mcp__uniswap__execute_swap ... mcp__uniswap__submit_cross_chain_intent
Recommendation

Require an explicit final confirmation immediately before any execution, including counterparty, token addresses, amounts, chain, quote, slippage, fees, and receiving address. Prefer wallet-level transaction prompts and spend limits.

ConcernMedium Confidence
ASI03: Identity and Privilege Abuse
What this means

Users may not understand which wallet or account the agent can trade from, what approvals are needed, or what limits protect their funds.

Why it was flagged

For a skill that can settle Uniswap trades, the artifacts do not declare what wallet, signer, account, or delegated authority is used. That makes the financial permission boundary unclear.

Skill content
Required env vars: none ... Primary credential: none ... Capability signals: No capability tags were derived.
Recommendation

Declare the required wallet/signing mechanism and permission scope. Require per-transaction user approval and document supported chains, spend limits, and allowance handling.

What this means

Trade terms, counterparty identifiers, and settlement details may be exposed to counterparties or on-chain systems.

Why it was flagged

The skill’s purpose involves a counterparty agent and trade-term negotiation. This is disclosed and purpose-aligned, and ERC-8004 verification is a mitigating control, but users should still treat counterparty identity and trade terms as sensitive.

Skill content
Facilitate over-the-counter trades between agents ... Verifies counterparty identity via ERC-8004, negotiates terms
Recommendation

Verify the counterparty independently when possible and avoid sharing unnecessary sensitive information during negotiation.

What this means

Financial history and counterparty relationships may persist beyond the immediate trade.

Why it was flagged

The skill describes a persistent audit or reputation history containing financial transaction details. This is relevant to the trading purpose, but storage, retention, and reuse boundaries are not visible in the provided excerpt.

Skill content
Every OTC trade is recorded with counterparty identity, agreed terms, settlement transaction, and fees. This creates a verifiable history for reputation building
Recommendation

Confirm where trade records are stored, who can access them, and whether they can be deleted or limited.

What this means

A future change to the referenced repository path could alter what gets installed if users install from that source.

Why it was flagged

The README documents installation from an external GitHub branch path. This is common for skills, but a branch path is not pinned to a specific commit or release.

Skill content
npx skills add https://github.com/wpank/Agentic-Uniswap/tree/main/.ai/skills/agent-otc-trade
Recommendation

Prefer installing from a trusted registry entry or a pinned commit/release, especially for a financial trading skill.