Raydium
Audit Raydium liquidity positions before capital is deployed. Analyze pool depth, concentration, liquidity quality, structural risks, and parameter changes so users can make cleaner LP decisions.
Best use case
Raydium is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Audit Raydium liquidity positions before capital is deployed. Analyze pool depth, concentration, liquidity quality, structural risks, and parameter changes so users can make cleaner LP decisions.
Teams using Raydium should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/raydium/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Raydium Compares
| Feature / Agent | Raydium | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Audit Raydium liquidity positions before capital is deployed. Analyze pool depth, concentration, liquidity quality, structural risks, and parameter changes so users can make cleaner LP decisions.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Raydium > **Do not add liquidity to a pool you have not interrogated.** Raydium is a protocol-truth-enforcer skill for liquidity decisions. This skill is designed for users who want to evaluate Raydium pools before adding liquidity, moving size, or treating a pool as trustworthy. Use this skill when you need to: - assess whether a Raydium pool looks healthy enough for LP deployment - evaluate liquidity depth and concentration risk - detect structural weakness before adding capital - reason about pool quality, not just APR or hype - review whether a pool looks durable, shallow, manipulated, or fragile This skill does NOT: - execute trades - add or remove liquidity - connect to Raydium contracts or wallets - guarantee pool safety - replace smart contract review or formal DeFi risk assessment --- ## What This Skill Does Raydium helps: - examine the quality of a liquidity pool before capital is deployed - evaluate whether apparent liquidity is deep, thin, or misleading - identify concentration, slippage, or fragility risks - reason about pool structure in plain language - separate attractive-looking pools from trustworthy pools --- ## Best Use Cases - pre-LP audit before adding liquidity - pool quality review for Solana LP strategies - concentration-risk review - slippage-risk screening - evaluating whether pool depth can support intended size - reviewing whether a pool is too shallow, too unstable, or too dependent on narrow conditions --- ## What to Provide Useful input includes: - pool pair - intended capital size - visible pool depth - recent activity or fee information - whether the pool uses concentrated liquidity - any known concerns about token quality, volatility, or parameter changes - what the user is optimizing for: yield, stability, or execution quality If information is incomplete, this skill should state what is missing instead of pretending the pool can be fully assessed. --- ## Standard Output Format RAYDIUM POOL ASSESSMENT ━━━━━━━━━━━━━━━━━━━━━━━━━━ Pool: [Pair] Intent: [Provide liquidity / assess pool / screen risk] LIQUIDITY TRUTH ━━━━━━━━━━━━━━━━━━━━━━━━━━ Depth Quality: [Strong / Moderate / Thin / Fragile] Concentration Risk: [Low / Medium / High] Execution Risk: [Low / Medium / High] MAIN CONCERNS ━━━━━━━━━━━━━━━━━━━━━━━━━━ ⚠️ [Depth concern] ⚠️ [Concentration concern] ⚠️ [Token / volatility concern] ⚠️ [Structural uncertainty] WHY THIS MATTERS ━━━━━━━━━━━━━━━━━━━━━━━━━━ - [How the pool may behave under size or volatility] - [Why apparent TVL may or may not equal usable liquidity] - [Where LP capital is most exposed] RECOMMENDED ROUTE ━━━━━━━━━━━━━━━━━━━━━━━━━━ - [Deploy now / deploy smaller / monitor first / avoid] NEXT CHECK ━━━━━━━━━━━━━━━━━━━━━━━━━━ - [What should be verified before capital is added] --- ## Protocol Truth Principles - apparent liquidity is not the same as usable liquidity - LP yield without depth quality can be deceptive - concentrated liquidity can improve capital efficiency while increasing range and positioning risk - thin pools punish size disproportionately - protocol familiarity does not remove pair-level risk - never confuse activity with resilience --- ## Risk Review Lens When evaluating a Raydium pool, focus on: - how much liquidity actually supports the intended trade or LP size - whether liquidity is concentrated in a narrow active range - whether the underlying pair is structurally unstable - whether the pool looks durable under volatility - whether the user's size is too large relative to usable depth --- ## Execution Protocol (for AI agents) When user asks about a Raydium pool, follow this sequence: ### Step 1: Parse the setup Extract: - token pair - intended size - purpose (LP / screening / execution) - any visible depth or activity data - user objective (yield / lower risk / execution quality) ### Step 2: Assess pool quality Review: - depth - concentration - volatility exposure - structural fragility - pair-level risk ### Step 3: Identify weak points Flag: - shallow depth - concentrated active liquidity - unstable or low-trust token pair - size that may be too large for the pool - missing information that prevents confidence ### Step 4: Translate into decision language Return: - whether the pool looks robust enough - where the main risks are - what size or caution adjustment is appropriate - whether the user should deploy, reduce size, watch, or avoid ### Step 5: Guardrails If the assessment depends on missing on-chain details: - say so clearly - do not fake precision - recommend further verification before deployment --- ## Activation Rules (for AI agents) ### Use this skill when the user asks about: - Raydium pool quality - whether to add liquidity - LP risk on Raydium - pool depth - concentrated liquidity risk - slippage or liquidity concerns on Raydium ### Do NOT use this skill when: - user wants trade execution - user wants wallet or contract interaction - user wants guaranteed safety - user asks for direct smart contract verification not available in the prompt ### If context is ambiguous Ask: "Do you want a pool-risk and liquidity-quality assessment, or are you asking how to execute a trade?" --- ## Boundaries This skill supports analytical review of Raydium liquidity decisions. It does not replace: - smart contract audit - wallet security review - formal DeFi risk underwriting - tax or legal advice
Related Skills
raydium-heyanon
Safe execution layer for Raydium token launches on Solana with parameter validation and metadata preparation.
8004-skill
ERC-8004 Trustless Agents - Register and manage AI agent identities on TRON and BSC blockchains with on-chain reputation tracking
8004-MCP - Agent Registry Protocol
Multi-chain MCP server for ERC-8004 Agent Registry. Query agents, reputation, and feedback across Solana + EVM chains.
supurr
Backtest, deploy, and monitor trading bots on Hyperliquid. Supports Grid, DCA, and Spot-Perp Arbitrage strategies across Native Perps, Spot markets (USDC/USDH), and HIP-3 sub-DEXes.
senpi-skills
Agent Skills for autonomous crypto trading on Hyperliquid — trailing stops, market scanning, position management, and more.
sdks
Official Azex SDKs — TypeScript, Python, MCP Server, CLI for the crypto-native LLM API gateway
perp-cli
Multi-DEX perpetual futures CLI + MCP server — Pacifica (Solana), Hyperliquid, Lighter (Ethereum). 18 MCP tools for AI-powered trading
okx-exchange-websocket-skill
Subscribe to OKX public exchange WebSocket channels through UXC raw WebSocket mode for ticker, trade, book, and candle events with explicit subscribe frames.
okx-wallet-portfolio
This skill should be used when the user asks to 'check my wallet balance', 'show my token holdings', 'how much OKB do I have', 'what tokens do I have', 'check my portfolio value', 'view my assets', 'how much is my portfolio worth', 'what\'s in my wallet', or mentions checking wallet balance, total assets, token holdings, portfolio value, remaining funds, DeFi positions, or multi-chain balance lookup. Supports XLayer, Solana, Ethereum, Base, BSC, Arbitrum, Polygon, and 20+ other chains. Do NOT use for general programming questions about balance variables or API documentation. Do NOT use when the user is asking how to build or integrate a balance feature into code.
okx-security
Use this skill for security scanning: check transaction safety, is this transaction safe, pre-execution check, security scan, token risk scanning, honeypot detection, DApp/URL phishing detection, message signature safety, malicious transaction detection, approval safety checks, token approval management. Triggers: 'is this token safe', 'check token security', 'honeypot check', 'scan this tx', 'scan this swap tx', 'tx risk check', 'is this URL a scam', 'check if this dapp is safe', 'phishing site check', 'is this signature safe', 'check this signing request', 'check my approvals', 'show risky approvals', 'revoke approval', 'check if this approve is safe', token authorization, ERC20 allowance, Permit2. Covers token-scan, dapp-scan, tx-scan (EVM+Solana pre-execution), sig-scan (EIP-712/personal_sign), approvals (ERC-20/Permit2). Chinese: 安全扫描, 代币安全, 蜜罐检测, 貔貅盘, 钓鱼网站, 交易安全, 签名安全, 代币风险, 授权管理, 授权查询, 风险授权, 代币授权. Do NOT use for wallet balance/send/history — use okx-agentic-wallet.
okx-onchain-gateway
This skill should be used when the user asks to 'broadcast transaction', 'send tx', 'estimate gas', 'simulate transaction', 'check tx status', 'track my transaction', 'get gas price', 'gas limit', 'broadcast signed tx', or mentions broadcasting transactions, sending transactions on-chain, gas estimation, transaction simulation, tracking broadcast orders, or checking transaction status. Covers gas price, gas limit estimation, transaction simulation, transaction broadcasting, and order tracking across XLayer, Solana, Ethereum, Base, BSC, Arbitrum, Polygon, and 20+ other chains. Do NOT use for swap quote or execution - use okx-dex-swap instead. Do NOT use for general programming questions about transaction handling.
okx-x402-payment
This skill should be used when the user encounters an HTTP 402 Payment Required response, wants to pay for a payment-gated API or resource, or mentions 'x402', 'pay for access', '402 payment', 'payment-gated URL', or 'sign x402 payment'. Primary path signs via TEE with a wallet session (JWT); fallback path guides local EIP-3009 signing with the user's own private key if they have no wallet. Returns the payment proof (signature + authorization) that the caller can attach as a payment header to access the resource. Do NOT use for swap or token transfers — use okx-dex-swap instead. Do NOT use for wallet balance or portfolio queries — use okx-agentic-wallet or okx-wallet-portfolio. Do NOT use for security scanning — use okx-security. Do NOT use for transaction broadcasting — use okx-onchain-gateway. Do NOT use for general programming questions.