Fetch Pendle SDK metadata and validate routing configuration via CLI commands.
Works with
Query supported chains, aggregators, markets, assets, and market token details from Pendle's hosted API
Six command categories: info , chains , supported-aggregators , markets , assets , and market-tokens with filtering by chain, activity status, and asset type
Supports JSON and table output formats; configurable API base URL via flag or environment variable
Preflight validation available through grimoi
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongrimoire-pendleExecute the skills CLI command in your project's root directory to begin installation:
Fetches grimoire-pendle from franalgaba/grimoire and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate grimoire-pendle. Access via /grimoire-pendle in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
3
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
3
stars
Use this skill to inspect Pendle metadata and preflight Pendle routing configuration before running spells.
Preferred invocations:
grimoire venue pendle ...npx -y @grimoirelabs/cli venue pendle ... (no-install)bun run packages/cli/src/index.ts venue pendle ... (repo-local)grimoire-pendle ... (direct binary from @grimoirelabs/venues)Recommended preflight:
grimoire venue doctor --adapter pendle --chain 1 --rpc-url <rpc> --jsongrimoire venue pendle info [--base-url <url>] [--format <auto|json|table>]grimoire venue pendle chains [--base-url <url>] [--format <auto|json|table>]grimoire venue pendle supported-aggregators --chain <id> [--base-url <url>] [--format <auto|json|table>]grimoire venue pendle markets [--chain <id>] [--active <true|false>] [--base-url <url>] [--format <auto|json|table>]grimoire venue pendle assets [--chain <id>] [--type <PT|YT|LP|SY>] [--base-url <url>] [--format <auto|json|table>]grimoire venue pendle market-tokens --chain <id> --market <address> [--base-url <url>] [--format <auto|json|table>]grimoire venue pendle info --format table
grimoire venue pendle chains
grimoire venue pendle supported-aggregators --chain 1 --format json
grimoire venue pendle markets --chain 1 --active true --format table
grimoire venue pendle assets --chain 8453 --type PT --format table
grimoire venue pendle market-tokens --chain 8453 --market 0x... --format json
Pendle requires a market-first approach. Do NOT write a Pendle spell without first querying available markets.
Query markets for the target chain and underlying:
grimoire venue pendle markets --chain 1 --active true --format json
Pick a market — note its address and expiry. Each market has specific PT/YT/SY tokens.
Query market tokens to get the exact token addresses:
grimoire venue pendle market-tokens --chain 1 --market 0x... --format json
Write the spell using token addresses from step 3:
pendle.add_liquidity(0x<SY_address>, params.amount) with (max_slippage=100)
pendle.deposit(USDC, ...) — Pendle has no deposit action. Use add_liquidity, mint_py, mint_sy, or swap.enable_aggregator — Some routes require an aggregator. If no route is found, retry with enable_aggregator=true in the with() clause.| Action | Description | Input | Output |
|---|---|---|---|
swap |
Swap between any Pendle tokens | Single token | Single token |
add_liquidity |
Add single-sided liquidity | Underlying/SY | LP token |
remove_liquidity |
Remove single-sided liquidity | LP token | Underlying/SY |
mint_py |
Mint PT + YT from underlying | Underlying/SY | PT + YT |
redeem_py |
Redeem PT + YT to underlying | PT + YT | Underlying/SY |
mint_sy |
Wrap underlying into SY | Underlying | SY |
redeem_sy |
Unwrap SY to underlying | SY | Underlying |
Pendle exposes quote_out for route output comparisons:
pendle_out = metric("quote_out", pendle, USDC, "asset_out=DAI,amount=1000000,slippage_bps=1000")
Selector fields:
asset_outamount (defaults to 1 unit of input asset), slippage_bps, enable_aggregatorWhen writing Pendle actions in .spell files, use with clauses:
pendle.swap(PT_TOKEN, SY_TOKEN, params.amount) with (
max_slippage=100,
require_quote=true,
)
| Constraint | Type | Description |
|---|---|---|
max_slippage |
integer (bps) | Maximum slippage, validated as integer in [0, 10000], converted to decimal for API |
min_output |
integer (wei) | Minimum output amount floor |
require_quote |
boolean | Fail if Pendle API quote fails |
max_gas |
integer (wei) | Gas estimate cap |
Pendle swap only supports mode: exact_in. exact_out is not supported.
When the Pendle API returns multiple routes, the adapter selects the first (best) route and emits a warning via onWarning. This is logged in non-JSON CLI runs.
Pendle PT, YT, and SY tokens (e.g. PT_FXSAVE, YT_EETH, SY_WSTETH) are automatically resolved via the Pendle API at build time. You can use these symbols directly in spells without providing explicit addresses:
pendle.swap(PT_FXSAVE, USDC, params.amount) with (max_slippage=100)
The adapter converts underscore-delimited names (e.g. PT_FXSAVE) to the Pendle API format and picks the best match. If multiple expiries exist, the first (nearest) is selected.
To target a specific expiry or disambiguate, use the full 0x address instead:
pendle.swap(0xb1e926428ebec4421cce1ec6d9ff65d27f4b4bb6, USDC, params.amount)
Use grimoire venue pendle assets --chain <id> --type PT to discover available tokens and addresses.
https://api-v2.pendle.finance/core.--base-url or PENDLE_API_BASE_URL.--format json for automation and nested payloads.swap currently supports mode: exact_in only.assetOut, outputs), use bare address literals (0x...) and not quoted strings (\"0x...\").QUOTED_ADDRESS_LITERAL.max_slippage is validated as integer bps in [0, 10000] and converted to decimal (bps / 10000) before API requests.Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
I recommend grimoire-pendle for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added grimoire-pendle from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
grimoire-pendle has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: grimoire-pendle is the kind of skill you can hand to a new teammate without a long onboarding doc.
grimoire-pendle reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: grimoire-pendle is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for grimoire-pendle matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in grimoire-pendle — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: grimoire-pendle is focused, and the summary matches what you get after install.
Registry listing for grimoire-pendle matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 62