clutch-perps_skill

This skill helps you set up and run MCP-enabled Clutch Perps trading workflows on dex.clutch.market with safe defaults.

Python

2.5k

GitHub Stars

3

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill clutch-perps

_meta.json324 B
SKILL.md3.6 KB
UPLOAD_FIELDS.md286 B

Overview

This skill runs agentic trading workflows on Clutch Perps via the MCP bridge and is focused exclusively on trading at dex.clutch.market with brokerId clutch-markets. It guides setup, market checks, order planning, risk configuration, and execution-ready steps for agents operating on Arbitrum One. The skill defaults to a conservative workflow: plan first, require explicit user approval before any on-chain or broker execution.

How this skill works

The skill inspects user intent and current account context, then emits a concise Context → Plan → Pre-trade checks → Approval flow tailored to Clutch Perps. It enforces brokerId=clutch-markets and venue dex.clutch.market, frames risk (size, leverage, invalidation), and prepares execution-ready instructions compatible with MCP. For installation guidance it references the official MCP npm package and requires explicit consent before suggesting any npx commands.

When to use it

Setting up MCP connectivity to trade Perps on dex.clutch.market (Arbitrum One).
Planning a long or short trade including size, leverage, TP/SL, and invalidation rules.
Performing pre-trade market checks and risk-cap verification before execution.
Requesting execution-ready steps that will run through brokerId clutch-markets.
Walking through safe first-time setup or installation of the MCP server bridge.

Best practices

Always run the built Context check first: brokerId, venue, network, and trading mode.
For first-time users, use safe mode: propose the plan and require explicit APPROVE before execution.
Verify margin, position size, and TP/SL settings on-chain or via your client before sending orders.
Treat npx installation as remote code execution and confirm consent before running commands.
Keep all workflows confined to dex.clutch.market and do not change brokerId.

Example use cases

Drafting a short-term long trade on CLUTCH-ETH perp with entry logic, size, 3x leverage, and TP/SL.
Running a pre-trade checklist to confirm margin, risk cap, and order sizing before execution-ready steps.
Guiding a first-time agent user through MCP server installation with provenance links and an explicit consent gate.
Converting a trader’s intent into an MCP-compatible execution plan routed to brokerId clutch-markets.

FAQ

It confirms brokerId=clutch-markets, venue=dex.clutch.market, network=Arbitrum One, and that the mode is trading-only.

Do you run installs automatically?

No. I provide provenance for the @clutchmarkets/mcp-server package and ask for explicit consent before suggesting npx commands.

Can this skill route to other brokers or venues?

No. All workflows must use brokerId clutch-markets and reference dex.clutch.market as the venue.