Orderly Positions Tpsl
WarnAudited by ClawScan on May 18, 2026.
Overview
The skill is coherent for Orderly trading, but it includes high-impact trading actions such as closing positions and changing leverage without explicit approval or safety-guard instructions.
Review this skill carefully before use with a real Orderly account. It appears purpose-aligned, but because it covers live trading actions, configure your agent or app to require explicit approval for every leverage change, TP/SL update, and position close, and use restricted API keys whenever possible.
Findings (2)
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 used carelessly or invoked by an agent without a clear confirmation step, it could close real trading positions and cause financial loss.
This gives an actionable API pattern for closing a leveraged trading position at market price. That is purpose-aligned, but it is a high-impact financial action and the provided artifacts do not pair it with explicit confirmation, review, or user-authorization requirements.
// Close entire position at market price
POST /v1/order
Body: {
symbol: 'PERP_ETH_USDC',
side: positionQty > 0 ? 'SELL' : 'BUY',
order_type: 'MARKET',
order_quantity: Math.abs(positionQty).toString(),
reduce_only: true,
}Require explicit user confirmation before any order, TP/SL, position-close, or leverage-change request, and show the symbol, side, quantity, order type, leverage, and expected impact before submission.
Anyone or any agent with access to that key may be able to view trading data and perform trading actions permitted by the key.
A trading-scoped API key is expected for Orderly position and TP/SL management, but it grants sensitive account authority to read positions and place or manage trades.
API key with `read` and `trading` scopes
Use the least-privileged key possible, prefer read-only mode for monitoring, restrict trading keys by account/IP if supported, and do not share or store the key outside the trusted Orderly integration.