بنقرة واحدة
vulcan-risk-management
Pre-trade risk checks, leverage tiers, margin health thresholds, and when-to-warn rules.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Pre-trade risk checks, leverage tiers, margin health thresholds, and when-to-warn rules.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Development conventions and architecture guide for the Clawd Code CLI repository — a Solana-native AI coding agent with perps trading, image generation, voice, and x402 payments.
Register, discover, and hire autonomous AI agents on Solana. On-chain identity via Metaplex Core NFTs (8004-solana SDK or REST API). Search by capability, check reputation backed by $CLAWD payment proofs, browse the service catalog, and get machine-readable hiring instructions. Supports Google A2A agent-card.json and Anthropic MCP server-card.json. No EVM — Solana only.
Solana RPC data toolkit — 8-command CLI for live on-chain data: SOL balance + SPL token portfolio with USD values, transaction detail with balance changes, SPL token metadata + top holders, recent activity history, NFT portfolio (SPL + cNFT via Helius DAS), whale detector, network stats (TPS/epoch/price), and quick price lookup. Pure Python stdlib, no extra packages. Optional HELIUS_API_KEY for compressed NFT detection.
Clawd Guard — the sovereign secrets sentinel. Mandatory reading for every Solana developer before they push a single commit. Use when: setting up a new repo, reviewing a .gitignore, onboarding a dev, or after any "oops I committed my private key" incident. Covers every secrets pattern that must never touch git: wallet JSON files, keypairs, .env files, private keys, API tokens, service account credentials, and IDE/OS junk. Built by Clawd to stop you from becoming a cautionary tale.
AI code reviews via Greptile — trigger PR reviews, run local CLI reviews, query codebase graphs, apply auto-fixes, manage custom rules, and analyze review analytics. Use for code review, PR feedback, issue triage, and codebase exploration.
Clawd TUI perps screen integration. Use when the user asks about the Clawd terminal UI, the Phoenix perps screen inside the TUI, paper trading from the TUI, or how the TUI drives Vulcan.
| name | vulcan-risk-management |
| version | 1.0.0 |
| description | Pre-trade risk checks, leverage tiers, margin health thresholds, and when-to-warn rules. |
| metadata | {"openclawd":{"category":"finance"},"requires":{"bins":["vulcan"],"skills":["vulcan"]}} |
Use this skill for:
Before every trade, call these tools:
1. vulcan_margin_status → {} # risk_state, collateral, PnL
2. vulcan_position_list → {} # existing positions
3. vulcan_trade_orders → { symbol } # resting orders consuming margin
4. vulcan_market_orderbook → { symbol } # slippage check for market orders
| State | Meaning | Action |
|---|---|---|
Healthy | Sufficient collateral | Safe to trade |
HighRisk | Margin getting thin | Warn user before any new trades |
Liquidatable | At risk of liquidation | Do NOT open new positions. Suggest reducing exposure or adding collateral |
Markets have tiered leverage limits. Larger positions get lower max leverage.
vulcan_margin_leverage_tiers → { symbol: "SOL" }
The first tier gives max leverage for typical small trades. Always check it before proposing a live notional.
For live strategies, calculate the maximum smooth live notional before asking for launch approval:
max_tier_leverage = first_applicable_leverage_tier.max_leverage
max_notional = deposited_collateral * max_tier_leverage
smooth_notional = max_notional * 0.97 # leave fee/spread/headroom
requested_leverage = requested_notional / deposited_collateral
If the requested notional is above smooth_notional, do not attempt the over-cap live launch and do not frame it as a scary collateral mismatch. Present the largest smooth live amount first, then ask the user to approve that adjusted amount or deposit more collateral. Once the user approves the adjusted amount, execute it without re-litigating the original request.
vulcan_market_ticker → { symbol: "SOL" } # check funding_rate field
When the user doesn't specify exact size:
vulcan_market_info for lot size conversion.When the user specifies a size but collateral is thin, recommend lower live notionals instead of only offering paper/dry-run/cancel. Use market leverage tiers first, then optional lower-risk examples:
collateral * market_max_leverage * 0.97collateral * 5collateral * 7.5collateral * min(10, market_max_leverage) * 0.97Example: with $9.23 deposited collateral and a 10x first-tier cap, max notional is about $92.30; a smooth launch target is about $89.50. If the user requested $100, suggest a live $89-$90 TWAP before paper/dry-run/deposit options.
Alert the user when:
Do not warn solely because notional / collateral is greater than 1x or because the trade uses a large share of available collateral. On perps, this is expected. If risk state is Healthy, the request is comfortably inside the market leverage tier, and estimated liquidation distance is not close, present leverage/exposure as neutral context instead of a caution. Example: a 4x SOL position on a 15x tier should not be called risky just because it is 4x.
For market orders, check the orderbook:
vulcan_market_orderbook → { symbol: "SOL", depth: 10 }
If order size is large relative to available liquidity at the best levels, warn about potential slippage.