Trench

SuspiciousAudited by ClawScan on May 10, 2026.

Overview

This is only an instruction file, but it describes AI-driven cryptocurrency trading and automated position actions without clear approval, wallet-scope, or loss-limit safeguards.

Do not connect real wallets or allow autonomous trading based on this artifact alone. Treat it as an unfinished, high-risk crypto trading skill; require explicit trade approvals, isolated low-balance wallets, spending limits, retry limits, and a review of the actual code before use.

Findings (4)

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

An agent using this guidance could place or retry cryptocurrency trades that lose funds, incur fees, or buy risky tokens without adequate human review.

Why it was flagged

These planned capabilities involve direct, fast financial transactions and repeated transaction attempts, but the artifact does not define user confirmation, spending caps, slippage bounds beyond an example, or safe failure limits.

Skill content
- Rapid buy/sell via Jupiter aggregator + Raydium direct
- Pump.fun token sniping and graduation tracking
- Auto-retry on failed transactions
Recommendation

Only use this with explicit per-trade approval, strict spend limits, isolated wallets, clear slippage and retry caps, and a dry-run mode before any real transaction.

ConcernMedium Confidence
ASI03: Identity and Privilege Abuse
What this means

If implemented or paired with other tools, unclear wallet-access boundaries could expose more funds or accounts than the user intended.

Why it was flagged

Multi-wallet trading and position tracking imply access to wallet authority or sensitive account state, but the provided registry metadata declares no credential or configuration requirements to bound how that access would be handled.

Skill content
- Multi-wallet support
- PnL tracking per position
Recommendation

Require an explicit wallet connection model, least-privilege signing flow, wallet allowlist, maximum spend per wallet, and clear disclosure of any stored wallet or portfolio data.

NoteMedium Confidence
ASI08: Cascading Failures
What this means

A bad price feed, wrong token address, or failed transaction loop could trigger repeated or unintended trading actions.

Why it was flagged

Automated trading controls are aligned with the stated trading purpose, but without bounded execution rules they could compound losses or fees across market moves and repeated transactions.

Skill content
- Auto take-profit / stop-loss
- Trailing stops
- Auto-retry on failed transactions
Recommendation

Use circuit breakers, maximum retries, maximum daily loss limits, token allowlists, and human confirmation for new tokens or strategy changes.

What this means

Users cannot verify how future trading scripts would sign transactions, call APIs, handle failures, or protect wallet credentials from the current artifact.

Why it was flagged

The reviewed artifact is instruction-only and says implementation modules are not present yet, so the actual trading code, dependencies, and provenance cannot be assessed from this package.

Skill content
> ⚠️ This skill is under active development. Core modules coming soon.
Recommendation

Review the actual implementation, dependencies, and transaction-signing paths before granting wallet access or using it with real funds.