Automated summary
Handles Uniswap V2/V3/V4 liquidity operations — adding liquidity, removing a position, and collecting fees — including pool selection, range choice, approvals, and transaction execution.
Strengths
- Cleanly separates the three actions (add, remove, collect), each with its own parameter table, defaults, and extraction rules.
- Normalizes user intent ("ETH" → "WETH", "$5K" → "$5000") and explicitly asks for missing required parameters rather than guessing.
- Falls back to get_positions_by_owner when no position ID is given, and confirms the found position with the user before proceeding.
- Delegates execution to the liquidity-manager agent (with optional pool-researcher), covering safety checks and approval handling.
Limitations
- The provided SKILL.md cuts off mid-way through Step 2, so the full pool-selection and execution flow is not visible.
- Scope is limited to Uniswap V2/V3/V4 and a fixed chain list (ethereum, base, arbitrum, optimism, polygon); no other DEXs or networks.
- Actions trigger real on-chain transactions with financial risk, and the document offers no detailed risk-management strategy.
Use it when the user wants to provide or withdraw liquidity, open or close an LP position, or claim accumulated fees on Uniswap.
Avoid it for non-liquidity operations such as simple swaps or price analysis, or for protocols other than Uniswap.
Security analysis
CautionThe skill does not contain destructive, exfiltration, or obfuscated instructions. It is a legitimate DeFi liquidity management workflow. However, because it orchestrates real blockchain transactions and approvals, it involves powerful financial operations and should be treated with caution.
- •Skill orchestrates financial transactions (adding/removing liquidity, collecting fees) and delegates to agents that execute on-chain transactions, which can lead to loss of funds if parameters are misconfigured or if the user is not fully aware of the actions.
- •References to check_safety_status and safety-guardian indicate use of safety mechanisms, but the skill itself does not declare allowed tools, leaving execution details to external agents.
Examples
Add $5,000 of liquidity to ETH/USDC on Base using the 0.05% pool with a medium range.Remove 50% of my ETH/USDC position #12345 and collect the fees.How much in fees have I earned on my UNI/WETH position? Collect them if it's worth it.name: manage-liquidity description: "Add liquidity, remove liquidity, or collect fees on Uniswap V2/V3/V4 pools. Handles the full flow including pool selection, range optimization, approvals, safety checks, and transaction execution. Use when the user wants to LP, provide liquidity, remove a position, or collect accumulated fees."
Manage Liquidity
Overview
This is the primary skill for all liquidity operations on Uniswap. It handles three distinct actions:
- Add liquidity — Find the best pool, recommend a range, handle approvals, deposit tokens
- Remove liquidity — Withdraw tokens from an existing position (partial or full)
- Collect fees — Claim accumulated trading fees from a position
Each action delegates to the liquidity-manager agent for execution, with optional pool-researcher delegation for intelligent pool selection. This skill extracts the user's intent, validates parameters, and orchestrates the right agent workflow.
When to Use
Activate when the user says anything related to providing, removing, or managing Uniswap liquidity:
Adding liquidity:
- "Add liquidity to ETH/USDC"
- "Provide LP for WETH/USDC on Base"
- "LP into the best pool for ETH/USDC"
- "Open a position in UNI/WETH"
- "I want to LP $5000 into ETH/USDC"
- "Deposit liquidity into the 0.05% pool"
- "Add $10K to my WETH/USDC position"
Removing liquidity:
- "Remove my liquidity"
- "Close my ETH/USDC position"
- "Withdraw 50% from position #12345"
- "Exit my LP position"
Collecting fees:
- "Collect my fees"
- "Claim accumulated fees from position #12345"
- "How much in fees have I earned?" (check first, then offer to collect)
Parameters
For Adding Liquidity
| Parameter | Required | Default | How to Extract | | --------- | -------- | ------------ | ------------------------------------------------------------- | | action | Yes | — | Always "add" for this sub-flow | | token0 | Yes | — | First token: "ETH", "WETH", "USDC", or 0x address | | token1 | Yes | — | Second token | | amount | Yes | — | Dollar amount ("$5000"), token amount ("2.5 ETH"), or both | | chain | No | ethereum | "ethereum", "base", "arbitrum", "optimism", "polygon" | | version | No | v3 | "v2" (passive), "v3" (concentrated), "v4" (hooks) | | range | No | medium | "narrow" (±5%), "medium" (±15%), "wide" (±50%), "full" (±∞) | | feeTier | No | Auto-detect | "0.01%", "0.05%", "0.3%", "1%" or bps: 100, 500, 3000, 10000 |
For Removing Liquidity / Collecting Fees
| Parameter | Required | Default | How to Extract | | ---------- | -------- | ---------- | ------------------------------------------------------- | | action | Yes | — | "remove" or "collect" | | positionId | Yes* | — | NFT token ID ("position #12345") or found via search | | chain | No | ethereum | Chain where the position exists | | percentage | No | 100 | "50%", "all", "half" — only for remove | | collectFees| No | true | Whether to also collect fees when removing |
*If the user doesn't provide a position ID (e.g., "remove my ETH/USDC position"), search for it using get_positions_by_owner and confirm with the user before proceeding.
Workflow
Add Liquidity Flow
Step 1: PARSE INTENT
├── Extract: tokens, amount, chain, version, range, fee tier
├── Normalize: "ETH" → "WETH", "$5K" → "$5000"
└── If any required params missing → ASK the user (don't guess)
Step 2: POOL SELECTION (if user didn't specify exact pool)
├── If "best pool" or no fee tier specified:
│ └── Delegate to pool-researcher: "Find the best pool for {token0}/{token1} on {chain}"
│ Pool researcher returns ranked pools with APY, TVL, depth
│ Pick the recommended pool (or present top 3 if user wants to choose)
└── If specific pool given: use directly
Step 3: PRE-FLIGHT CHECKS
├── Check safety status via check_safety_status
├── Verify wallet has sufficient token balances
└── If checks fail → STOP and tell user what's wrong
Step 4: DELEGATE TO LIQUIDITY-MANAGER
├── Pass: token0, token1, amount, chain, version, range, feeTier, pool address
├── The liquidity-manager agent handles:
│ a. Check and execute token approvals (Permit2)
│ b. Calculate optimal tick range based on range strategy
│ c. Simulate the add-liquidity transaction
│ d. Route through safety-guardian for validation
│ e. Execute the transaction
│ f. Wait for confirmation
└── Returns: positionId, amounts deposited, tick range, tx hash
Step 5: PRESENT RESULT
├── Position ID (NFT token ID)
├── Tokens deposited with USD values
├── Price range (lower price, upper price, current price)
├── Estimated fee APY (from pool-researcher data)
├── Explorer link to the transaction
└── Tip: "Monitor with /track-performance"
Remove Liquidity Flow
Step 1: IDENTIFY POSITION
├── If position ID given → use directly
├── If "my ETH/USDC position" → call get_positions_by_owner
│ ├── Filter by token pair and chain
│ ├── If multiple matches → LIST them and ask user to choose
│ └── If no matches → tell user "No positions found for {pair}"
└── Confirm: "I found position #{id} — {pair} {feeTier} with {value}. Remove?"
Step 2: DELEGATE TO LIQUIDITY-MANAGER
├── Pass: positionId, chain, percentage (default 100%), collectFees
├── Agent handles: fee collection → partial/full removal → safety validation → execution
└── Returns: tokens received, fees collected, tx hash
Step 3: PRESENT RESULT
├── Tokens received with USD values
├── Fees collected (if any)
├── Total value received
├── Explorer link
└── If partial removal: remaining position details
Collect Fees Flow
Step 1: IDENTIFY POSITION (same as remove)
Step 2: CHECK UNCOLLECTED FEES
├── Call get_position to see tokensOwed0 and tokensOwed1
├── If fees are zero → "No fees to collect on this position"
└── Show fee amounts and ask to proceed
Step 3: DELEGATE TO LIQUIDITY-MANAGER
├── Pass: positionId, chain, action: "collect"
└── Returns: fees collected, tx hash
Step 4: PRESENT RESULT
├── Fees collected (token amounts + USD values)
├── Explorer link
└── Tip: "Your position is still active and earning more fees"
Critical Decision Points
These are the moments where the skill must stop and ask rather than assume:
| Situation | Action | | ---------------------------------- | ------------------------------------------------------------- | | Multiple positions match | List all matches, ask user to pick one | | Amount exceeds wallet balance | Show balance, ask if they want a smaller amount | | Pool TVL < $10,000 | Warn about low liquidity risk, ask to confirm | | Range strategy not specified | Default to "medium" but mention the tradeoffs | | First time LPing | Briefly explain IL risk before proceeding | | Remove > 50% of pool liquidity | Warn about price impact on exit |
Output Format
Successful Add
Liquidity Added Successfully
Position: #456789
Pool: WETH/USDC 0.05% (V3, Ethereum)
Deposited:
0.5 WETH ($980)
980 USDC ($980)
Total: $1,960
Range:
Lower: $1,700 (tick -204714)
Upper: $2,300 (tick -199514)
Current: $1,963 — IN RANGE ✓
Width: ±15% (medium)
Expected Fee APY: ~15-21% (based on 7d pool data)
Tx: https://etherscan.io/tx/0x...
Next steps:
- Monitor with: "How are my positions doing?"
- Rebalance if out of range: "Rebalance position #456789"
- Collect fees anytime: "Collect fees from position #456789"
Successful Remove
Liquidity Removed
Position: #456789 (CLOSED)
Received:
0.52 WETH ($1,020)
950 USDC ($950)
Total: $1,970
Fees Collected:
0.01 WETH ($19.60)
15.20 USDC ($15.20)
Total fees: $34.80
Net Result: +$44.80 (+2.3%) including fees
Tx: https://etherscan.io/tx/0x...
Important Notes
- IL risk: Always mention impermanent loss risk when adding liquidity to volatile pairs. Don't bury it.
- Gas costs: On Ethereum mainnet, LP operations cost $15-50 in gas. Mention this for small positions.
- Range tradeoffs: Narrow = higher fees but more rebalancing. Wide = lower fees but less maintenance. Always explain.
- V2 vs V3: V2 is "set and forget" with lower returns. V3 requires active management but earns more. Help the user choose.
- Never auto-execute: For remove and rebalance, always confirm with the user before executing.
Error Handling
| Error | User-Facing Message | Suggested Action | | ----------------------------- | --------------------------------------------------------- | ----------------------------------------- | | Wallet not configured | "No wallet configured for transactions." | Set WALLET_TYPE + PRIVATE_KEY in .env | | Insufficient balance | "You have X but need Y to add liquidity." | Reduce amount or swap for needed tokens | | Pool not found | "No pool found for X/Y at this fee tier." | Try different fee tier or check token names| | Position not found | "Position #ID not found on this chain." | Check chain and position ID | | Safety check failed | "Transaction blocked by safety: {reason}" | Adjust parameters or check safety config | | Transaction reverted | "Transaction failed: {reason}" | Check slippage, amounts, or try again | | liquidity-manager unavailable | "Liquidity agent is not available." | Check agent configuration |
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/manage-liquidity-mrwakg97/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/manage-liquidity-mrwakg97' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/manage-liquidity-mrwakg97/download' --output '.skill-downloads/manage-liquidity-mrwakg97/SKILL.md.part' && mv '.skill-downloads/manage-liquidity-mrwakg97/SKILL.md.part' '.skill-downloads/manage-liquidity-mrwakg97/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/manage-liquidity-mrwakg97/SKILL.md' && test -s '.skill-downloads/manage-liquidity-mrwakg97/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/manage-liquidity' && cp -R '.skill-downloads/manage-liquidity-mrwakg97' '.claude/skills/manage-liquidity'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/manage-liquidity-mrwakg97'openskills read 'manage-liquidity-mrwakg97'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/manage-liquidity-mrwakg97/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.