seek-protocol-fees
Analyze TokenJar profitability and optionally execute a Firepit burn-and-claim. Autonomous pipeline: checks balances, prices assets, calculates profit vs. 4,000 UNI burn cost, simulates, and executes if profitable. Default is preview-only. Use when user asks "Is the TokenJar profitable?", "Execute a burn", or "Claim protocol fees."
Why use this skill?
Analyze TokenJar profitability, simulate Firepit burns, and claim Uniswap protocol fees autonomously with the seek-protocol-fees skill.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/wpank/seek-protocol-feesWhat This Skill Does
The seek-protocol-fees skill is a sophisticated, autonomous pipeline designed to interact with the Uniswap protocol fee ecosystem. Specifically, it monitors the TokenJar (0xf38521f130fcCF29dB1961597bc5d2B60F995f85) and the associated Firepit mechanism. In the Uniswap ecosystem, protocol fees are accumulated, and a specific mechanism exists where users can burn 4,000 UNI to unlock these accumulated assets. This skill automates the complex 9-step workflow required to determine if this action is economically rational. It aggregates balances, fetches real-time price feeds for all assets in the jar, calculates the cost of burning 4,000 UNI, factors in network gas fees, and identifies the net profit. Most importantly, it features a safety-first architecture, defaulting to a preview-only mode that allows users to inspect the profitability report before deciding to commit funds. It also handles the optional post-burn conversion of volatile assets into stablecoins to lock in gains.
Installation
To integrate this skill into your OpenClaw environment, execute the following command in your terminal:
clawhub install openclaw/skills/skills/wpank/seek-protocol-fees
Use Cases
This tool is designed for liquidity providers, protocol observers, and DeFi power users. Primary use cases include:
- Proactive monitoring of the TokenJar to identify "burn windows" where net profit is positive.
- Executing the burn-and-claim sequence efficiently without manual intervention.
- Performing automated arbitrage between the cost of burning 4,000 UNI and the underlying fee assets.
- Generating structured, human-readable profitability reports for DAO treasury management or personal yield tracking.
Example Prompts
- "Is the TokenJar currently profitable to burn? Please show me the breakdown of costs and expected gains."
- "Check the protocol fees, and if the net profit after gas and slippage is over 500 USD, execute the burn."
- "Run the seek-protocol-fees pipeline and show me if it's worth claiming the tokens right now."
Tips & Limitations
- Safety-First: The tool defaults to preview-only mode. You must explicitly configure the skill to allow execution if you intend to trigger the burn.
- Gas Sensitivity: Profitability is highly sensitive to network congestion. The skill uses estimated gas, but periods of high volatility may impact final returns.
- Slippage: When enabling the post-burn conversion to stablecoins, ensure you account for liquidity depth in the target pools to avoid unexpected slippage.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-wpank-seek-protocol-fees": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: network-access, code-execution, external-api
Related Skills
mermaid-diagrams
Create software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams, sequence diagrams, flowcharts, ERDs, C4 architecture diagrams, state diagrams, git graphs, and other diagram types. Triggers include requests to diagram, visualize, model, map out, or show the flow of a system.
api-design-principles
Skill by wpank
auto-context
Automatically read relevant context before major actions. Loads TODO.md, roadmap.md, handoffs, task plans, and other project context files so the AI operates with full situational awareness. Use when starting a task, implementing a feature, refactoring, debugging, planning, or resuming a session.
clear-writing
Write clear, concise prose for humans — documentation, READMEs, API docs, commit messages, error messages, UI text, reports, and explanations. Combines Strunk's rules for clearer prose with technical documentation patterns, structure templates, and review checklists.
track-performance
Track the performance of Uniswap LP positions over time — check which positions need attention, are out of range, or have uncollected fees. Use when the user asks how their positions are doing.