Install
Terminal · npx$
npx skills add https://github.com/franalgaba/grimoire --skill grimoire-pendleWorks with Paperclip
How Grimoire Pendle fits into a Paperclip company.
Grimoire Pendle drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.
S
SaaS FactoryPaired
Pre-configured AI company — 18 agents, 18 skills, one-time purchase.
$27$59
Explore packSource file
SKILL.md142 linesExpandCollapse
---name: grimoire-pendledescription: Fetches Pendle Hosted SDK metadata using the Grimoire venue CLI. Use when you need supported chains, aggregators, markets, assets, or market token details.--- # Grimoire Pendle Skill 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> --json` ## Commands - `grimoire 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>]` ## Examples ```bashgrimoire venue pendle info --format tablegrimoire venue pendle chainsgrimoire venue pendle supported-aggregators --chain 1 --format jsongrimoire venue pendle markets --chain 1 --active true --format tablegrimoire venue pendle assets --chain 8453 --type PT --format tablegrimoire venue pendle market-tokens --chain 8453 --market 0x... --format json``` ## Authoring Workflow Pendle requires a market-first approach. **Do NOT write a Pendle spell without first querying available markets.** 1. **Query markets** for the target chain and underlying: ```bash grimoire venue pendle markets --chain 1 --active true --format json ``` 2. **Pick a market** — note its address and expiry. Each market has specific PT/YT/SY tokens. 3. **Query market tokens** to get the exact token addresses: ```bash grimoire venue pendle market-tokens --chain 1 --market 0x... --format json ``` 4. **Write the spell** using token addresses from step 3: ```spell pendle.add_liquidity(0x<SY_address>, params.amount) with (max_slippage=100) ``` ### Common mistakes - **`pendle.deposit(USDC, ...)`** — Pendle has no `deposit` action. Use `add_liquidity`, `mint_py`, `mint_sy`, or `swap`.- **Using token symbols without addresses** — PT/YT/SY tokens are auto-resolved via the Pendle API, but standard tokens like USDC need raw amounts in the token's smallest unit.- **Missing `enable_aggregator`** — Some routes require an aggregator. If no route is found, retry with `enable_aggregator=true` in the `with()` clause. ### Supported actions | 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 | ## Metric Surface (Spell Comparisons) Pendle exposes `quote_out` for route output comparisons: ```spellpendle_out = metric("quote_out", pendle, USDC, "asset_out=DAI,amount=1000000,slippage_bps=1000")``` Selector fields: - required: `asset_out`- optional: `amount` (defaults to 1 unit of input asset), `slippage_bps`, `enable_aggregator` ## Spell Constraints When writing Pendle actions in `.spell` files, use `with` clauses: ```spellpendle.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. ## PT/YT/SY Token Resolution 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: ```spellpendle.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: ```spellpendle.swap(0xb1e926428ebec4421cce1ec6d9ff65d27f4b4bb6, USDC, params.amount)``` Use `grimoire venue pendle assets --chain <id> --type PT` to discover available tokens and addresses. ## Notes - Default API base URL is `https://api-v2.pendle.finance/core`.- Override base URL with `--base-url` or `PENDLE_API_BASE_URL`.- Use `--format json` for automation and nested payloads.- Pendle `swap` currently supports `mode: exact_in` only.- Aggregators are disabled by default in adapter actions unless explicitly enabled.- For Pendle token outputs (`assetOut`, `outputs`), use bare address literals (`0x...`) and not quoted strings (`\"0x...\"`).- Quoted address-like token values trigger validator code `QUOTED_ADDRESS_LITERAL`.- `max_slippage` is validated as integer bps in `[0, 10000]` and converted to decimal (`bps / 10000`) before API requests.