Funding Rate Arbitrage Assistant

Monitor, evaluate, and operate a funding rate arbitrage strategy for crypto perpetual swaps. Use when the user asks to check funding-rate arbitrage opportuni...

Security Scan

The skill's purpose (rule-based funding-rate decision support) matches its instructions, but it mentions pulling live account data and executing orders without declaring how credentials or execution will be supplied or protected — this mismatch warrants caution.

Purpose & Capability

The skill is clearly positioned as a funding-rate arbitrage decision-support and operating guide. That purpose aligns with the included strategy and listing references. However, the SKILL.md also addresses live execution (placing/modifying orders) while the skill declares no required credentials or integration points — acceptable if the skill is advisory-only, inconsistent if it is expected to operate accounts.

Instruction Scope

Instructions are specific to funding-rate workflows (confirm exchange/account mode, gather live funding rates/positions, apply rules, produce action plans). The document tells the agent to 'pull live funding-rate and position data' and to 'restate action before placing or modifying orders' but does not define where or how to obtain data/credentials or what execution endpoints to call. That leaves broad discretion to the agent or to the surrounding integration — a potential scope creep if the agent is given execution privileges.

Install Mechanism

This is an instruction-only skill with no install spec and no bundled code — low install risk (nothing is written to disk by the skill itself).

Credentials

The skill implies needing exchange account data and possibly API keys for live monitoring and execution, but requires no environment variables or credentials. That mismatch is potentially problematic: if the skill will be used to execute trades, explicit, minimal, and well-scoped credential requirements (and guidance to use restricted/read-only keys or manual confirmation) should be documented.

Persistence & Privilege

always:false and no system/config path modifications are requested. The skill does not ask for persistent system privileges or to modify other skills' settings.

What to consider before installing

This skill is an instruction-only decision-support guide for funding-rate arbitrage and appears coherent in strategy and content, but it leaves unspecified how live account data and order execution are provided. Before installing or using it for live trading: 1) Clarify whether the agent will only give advice or will be allowed to place orders. 2) If execution is intended, require explicit, minimal, and documented credentials (use read-only keys for monitoring; use narrowly scoped API keys and IP restrictions for execution). 3) Insist on manual confirmation before any order is placed by the agent (restate-and-confirm). 4) Test the workflow thoroughly in demo/paper mode and verify duplicate-order and stop-loss behaviors. 5) If you need higher assurance, ask the developer to declare required env vars and integration points and to provide code or an install spec that documents exactly how credentials are handled. These clarifications would move the assessment toward 'benign'; lack of them keeps it 'suspicious.'

Funding Rate Arbitrage

Use this skill for crypto perpetual funding-rate arbitrage workflows where the goal is to collect funding while controlling directional exposure.

Quick Start

When using this skill:

1. Confirm the venue and account mode first.
2. Pull live funding-rate and position data before giving advice.
3. Use exchange-returned fields for position value and PnL; do not hand-wave calculations.
4. Apply the strategy rules in references/strategy.md.
5. If the user asks to publish or productize the strategy, use references/clawhub-listing.md.

Operating Workflow

1. Confirm context

Collect or confirm:

• exchange (Binance / OKX / other)
• live or demo / paper mode
• current open positions and pending orders
• whether the user wants monitoring, candidate selection, open, or close decisions

2. Read current market/account state

For live decision support, always gather:

• candidate instruments and current funding rates
• current open positions
• unrealized and realized PnL
• margin usage / leverage / liquidation risk when available

If the user wants execution guidance, do not rely on stale notes alone.

3. Apply strategy rules

Use the rules in references/strategy.md for:

• entry threshold
• position count cap
• nominal size target
• close conditions
• duplicate-order avoidance
• pre-settlement timing

4. Produce one of these outputs

Depending on the request, return one of these:

• Opportunity summary: which symbols qualify and why
• Position review: current positions, funding direction, PnL, and whether they still fit rules
• Action plan: open / hold / close / skip with concrete reasons
• Productized summary: concise explanation suitable for docs, listing pages, or client delivery

Hard Rules

• Treat all financial calculations as high-stakes.
• Prefer exchange API fields over manual calculations.
• Distinguish spot, swap, futures, and options before interpreting values.
• If a platform returns a direct notional or USD value field, use that field.
• If data is incomplete or conflicting, stop and say what is missing.
• For live execution requests, restate the action clearly before placing or modifying orders.

References

• Read references/strategy.md for the current strategy rules and risk controls.
• Read references/clawhub-listing.md when preparing a ClawHub listing or sales copy for this skill.