grimoire-morpho-blue

franalgaba/grimoire · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/franalgaba/grimoire --skill grimoire-morpho-blue
0 commentsdiscussion
summary

Query Morpho Blue deployment metadata and vault snapshots via the Grimoire CLI.

  • Three command categories: info (general metadata), addresses (contract addresses by chain), and vaults (filterable vault data with APY and TVL)
  • Supports --format spell output to emit snapshot blocks with provenance fields ( snapshot_at , snapshot_source ) and APY data for spell parameters
  • APY values are decimal rates (e.g., 0.0408 for 4.08%); include both decimal and percent display when reporting
  • Ship
skill.md

Grimoire Morpho Blue Skill

Use this skill to query Morpho Blue deployment metadata and vault snapshots for spell params.

Preferred invocations:

  • grimoire venue morpho-blue ...
  • npx -y @grimoirelabs/cli venue morpho-blue ... (no-install)
  • bun run packages/cli/src/index.ts venue morpho-blue ... (repo-local)
  • grimoire-morpho-blue ... (direct binary from @grimoirelabs/venues)

Recommended preflight:

  • grimoire venue doctor --adapter morpho-blue --chain 8453 --rpc-url <rpc> --json

Use --format spell to emit a params: snapshot block.

The snapshot includes provenance fields (snapshot_at, snapshot_source) and APY data.

APY semantics:

  • apy / net_apy are decimal rates (for example 0.0408 = 4.08%).
  • When reporting, include both decimal and percent display when possible.

Commands

  • grimoire venue morpho-blue info — adapter metadata
  • grimoire venue morpho-blue addresses [--chain <id>] — contract addresses per chain
  • grimoire venue morpho-blue vaults [--chain <id>] [--asset <symbol>] [--min-tvl <usd>] [--min-apy <decimal>] [--min-net-apy <decimal>] [--sort <netApy|apy|tvl|totalAssetsUsd|name>] [--order <asc|desc>] [--limit <n>] — list and filter vaults
  • grimoire venue morpho-blue vaults-snapshot [--chain <id>] [--asset <symbol>] [--min-tvl <usd>] [--min-apy <decimal>] [--min-net-apy <decimal>] [--sort <netApy|apy|tvl|totalAssetsUsd|name>] [--order <asc|desc>] [--limit <n>] — generate spell params: block for vaults (agent-only)

Examples

grimoire venue morpho-blue info --format table
grimoire venue morpho-blue addresses --chain 1
grimoire venue morpho-blue addresses --chain 8453
grimoire venue morpho-blue vaults --chain 8453 --asset USDC --min-tvl 5000000 --format table
grimoire venue morpho-blue vaults --chain 8453 --asset USDC --min-tvl 5000000 --format spell
grimoire venue morpho-blue vaults-snapshot --chain 8453 --asset USDC --min-tvl 5000000

Use vaults-snapshot to emit a params: block for spell inputs. This is an agent-only command (output suppressed in interactive mode).

Example provenance output fields to preserve:

  • snapshot_at
  • snapshot_source
  • units (for example net_apy=decimal, net_apy_pct=percent, tvl_usd=usd)

Metric Surface (Spell Comparisons)

Morpho exposes the apy metric surface and supports selector-based market targeting:

morpho_apy_default = apy(morpho, USDC)
morpho_apy_market = apy(morpho, USDC, "weth-usdc-86")
morpho_apy_market_id = apy(morpho, USDC, "0x...")
morpho_apy_generic = metric("apy", morpho, USDC, "wbtc-usdc-86")
vault_apy = metric("vault_apy", morpho, USDC, "vault=0xVaultAddress")
vault_net_apy = metric("vault_net_apy", morpho, USDC, "vault=0xVaultAddress")

Selector behavior:

  • market no selector (apy): resolves by asset on the active chain and picks the highest-TVL match
  • config market selector: use known market ids from adapter config (for example weth-usdc-86)
  • onchain market id selector: use raw market id (0x...)
  • vault selectors (vault_apy / vault_net_apy): vault=<address|name|symbol> or bare vault address/name/symbol
  • vault_apy / vault_net_apy require explicit selector (no implicit fallback)

When multiple vaults/markets exist for one asset, pass an explicit selector for deterministic comparisons.

Spell Constraints

Morpho Blue actions do not support runtime constraints (max_slippage, etc.). Value-moving actions require an explicit market_id.

morpho_blue.lend(USDC, params.amount, "cbbtc-usdc-86")
morpho_blue.withdraw(USDC, params.amount, "cbbtc-usdc-86")
morpho_blue.borrow(USDC, params.amount) with (
  market_id="cbbtc-usdc-86",
)
morpho_blue.supply_collateral(cbBTC, params.amount, "cbbtc-usdc-86")
morpho_blue.withdraw_collateral(cbBTC, params.amount, "cbbtc-usdc-86")

Use with (market_id=...) when positional args are not convenient:

morpho_blue.lend(USDC, params.amount) with (
  market_id="0x1234...abcd",
)

Use grimoire venue morpho-blue vaults to discover available market IDs.

Action Selection Guide

Choose actions by strategy intent:

  • Supply-only strategy (no borrowing planned): prefer vault_deposit / vault_withdraw.
  • Borrowing strategy (or future borrow/repay/collateral management): use market actions with explicit market_id.

Hard rules:

  • vault_deposit / vault_withdraw require explicit vault address and do not use market_id.
  • lend, withdraw, borrow, repay, supply_collateral, withdraw_collateral require explicit market_id.
  • If vault address is missing for a vault action, do not guess: list candidate vaults and require user selection before authoring/executing.

Action Semantics

  • lend(asset, amount, market_id): lend the market loan asset (lender side).
  • withdraw(asset, amount, market_id): withdraw previously lent loan asset.
  • supply_collateral(asset, amount, market_id): post collateral for borrowing (borrower side).
  • withdraw_collateral(asset, amount, market_id): remove posted collateral.
  • borrow(asset, amount, collateral?, market_id): borrow the market loan asset.
  • repay(asset, amount, market_id): repay borrowed loan asset.
  • vault_deposit(asset, amount, vault_address): deposit into MetaMorpho vault.
  • vault_withdraw(asset, amount, vault_address): withdraw from MetaMorpho vault.

lend and supply_collateral are not interchangeable:

  • lend targets lender yield on loan asset.
  • supply_collateral is collateral management for borrowing capacity.

APY expectations:

  • lend accrues market supply APY (plus possible incentives).
  • supply_collateral does not earn market lender APY; it is risk buffer for borrow.
  • Collateral token may have its own native yield behavior (for example wstETH), separate from Morpho supply APY.

Workflow Patterns

Supply-only via vault:

morpho_blue.vault_deposit(USDC, params.amount, "0xVaultAddress")

If vault is not provided, run discovery first and ask user to pick:

grimoire venue morpho-blue vaults --chain <id> --asset <symbol> --sort netApy --order desc --limit 5 --format table

Then use the selected vault address in vault_deposit / vault_withdraw.

Borrow workflow (market):

morpho_blue.supply_collateral(WETH, params.collateral_amount, "weth-usdc-86")
morpho_blue.borrow(USDC, params.borrow_amount, WETH, "weth-usdc-86")

Unwind borrow workflow:

morpho_blue.repay(USDC, params.repay_amount, "weth-usdc-86")
morpho_blue.withdraw_collateral(WETH, params.collateral_out, "weth-usdc-86")

Lend-only via market (when explicit market control is desired):

morpho_blue.lend(USDC, params.amount, "cbbtc-usdc-86")

Default Markets

The adapter ships with pre-configured markets for Ethereum (chain 1) and Base (chain 8453):

Ethereum (chain 1)

Market Loan Collateral LLTV
cbbtc-usdc-1 USDC cbBTC 86%
wbtc-usdc-1 USDC WBTC 86%
wsteth-weth-1 WETH wstETH 96.5%

Base (chain 8453)

Market Loan Collateral LLTV
cbbtc-usdc-86 USDC cbBTC 86%
weth-usdc-86 USDC WETH 86%

Notes

  • Outputs JSON/table; vaults also supports --format spell.
  • Uses the SDK's chain address registry.
  • Prefer --format json in automation and --format table for quick triage.
how to use grimoire-morpho-blue

How to use grimoire-morpho-blue on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add grimoire-morpho-blue
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/franalgaba/grimoire --skill grimoire-morpho-blue

The skills CLI fetches grimoire-morpho-blue from GitHub repository franalgaba/grimoire and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/grimoire-morpho-blue

Reload or restart Cursor to activate grimoire-morpho-blue. Access the skill through slash commands (e.g., /grimoire-morpho-blue) or your agent's skill management interface.

Security & Verification Notice

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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

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

Competitive Analysis

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

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

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

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ 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.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.844 reviews
  • Nikhil Wang· Dec 28, 2024

    We added grimoire-morpho-blue from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Benjamin Kim· Dec 4, 2024

    grimoire-morpho-blue fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Chen Smith· Dec 4, 2024

    Useful defaults in grimoire-morpho-blue — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Yash Thakker· Nov 27, 2024

    grimoire-morpho-blue reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Isabella Johnson· Nov 23, 2024

    grimoire-morpho-blue is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Chen Mehta· Nov 23, 2024

    I recommend grimoire-morpho-blue for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Dhruvi Jain· Oct 18, 2024

    We added grimoire-morpho-blue from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Emma Li· Oct 14, 2024

    Solid pick for teams standardizing on skills: grimoire-morpho-blue is focused, and the summary matches what you get after install.

  • Isabella Smith· Oct 14, 2024

    Keeps context tight: grimoire-morpho-blue is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Naina Lopez· Sep 25, 2024

    We added grimoire-morpho-blue from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

showing 1-10 of 44

1 / 5