Agentic Lending Morpho

This skill is the Morpho-side counterpart to the EVK skill. It is still more conservative than the EVK path, but it now supports a real end-to-end flow for compatible requests: resolve the requested collateral and borrow assets, check feed readiness, execute funding when available, deploy the oracle adapter, deploy the Morpho market, and verify the result.

Read next

1. references/workflow.md
2. references/current_capabilities.md
3. references/morpho-oracle-adapter.md

Minimum required inputs

Gather these before attempting a Morpho-first workflow:

• chain name and chain id
• explicit collateralAssets
• explicit borrowAssets
• target market shape or risk intent
• whether the user wants planning only, dry-run, or live execution
• live RPC availability for the chain if anything beyond planning is expected
• Morpho policy inputs needed for deployment on that chain when live execution is requested

If any of those are missing, stop and ask instead of inventing them.

Request-shape rule

When preparing a request for this skill, always express the market assets explicitly as:

• collateralAssets: array of { symbol, address }
• borrowAssets: array of { symbol, address }

Do not leave asset selection implicit. The planner needs the exact collateral and borrow assets in order to resolve feeds, choose a direct-versus-composed oracle route, and verify the final market correctly.

Default workflow

1. Normalize the request into:
   • chain
   • collateralAssets
   • borrowAssets
   • protocol = morpho
   • market or risk intent
   • desired execution mode
2. Treat asset selection as a first-class input.
   • confirm the exact collateral asset set and borrow asset set the user wants
   • for multiple collateral assets, remember this becomes a Morpho market set: one market per supported collateral/borrow pair
3. Resolve the oracle path before any deploy step.
   • prefer a direct pair when the exact requested route is available and usable
   • otherwise use a supported composed route when the planner can prove it cleanly
   • keep feed-name matching generic: literal exact pair first, alias-normalized fallback second
4. Check feed readiness before deployment.
   • if feeds are already live on the deployable on-chain path, continue
   • if funding is needed and executable, run the funding path first
   • if the funding branch is browser-assisted or unsupported, stop and report that honestly instead of pretending deployment can continue
5. Prefer the orchestration wrapper for the real sequence.
   • use ensure-feeds-and-deploy-morpho-market when the goal is to check feeds, fund if needed, wait for propagation, deploy, and verify in one coherent run
   • use lower-level commands only when debugging or resuming a prior run
6. Prepare and deploy the Morpho oracle adapter path.
   • use the Api3-backed Morpho oracle adapter design as the canonical oracle shape
   • preserve artifact handoff from adapter deployment into market deployment
   • keep proxy-first ordering whenever a communal proxy deploy is required
7. Verify the deployed market.
   • confirm the market exists on-chain
   • confirm params, IRM, and LLTV expectations
   • confirm oracle price() succeeds and is positive
8. Stop at the honest boundary.
   • if the request can only reach planning or funding handoff, say so clearly
   • do not present Morpho deployment as equivalent to the EVK live deploy path unless the code actually supports the requested environment

Preferred command path

For a deployable request, prefer this command shape:

node bin/part2-morpho-planner.js ensure-feeds-and-deploy-morpho-market --input-file ./request.json

Use it when the agent already has a concrete request file with the selected collateral and borrow assets.

Use --resume-from-run-dir \x3Cdir> when continuing a previously persisted run.

Output expectations

Always report:

• whether the request was normalized successfully
• which collateral assets and borrow assets were selected for the Morpho market or market set
• whether the required Api3 feeds are already live, fundable, browser-assisted, or unsupported
• whether feed funding was executed, skipped as unnecessary, or handed off
• what oracle adapter shape is planned or deployed for Morpho
• which steps are planning-only versus executable today
• exact blockers preventing a full Morpho deployment flow, if any
• the next concrete command, file, or implementation gap to close

Tone

Be blunt about current Morpho limits. Do not blur design-doc intent into executable support. But do not understate the implemented path either: if the selected-asset request is executable, say so plainly and use the resolve → feed-check → funding → deploy → verify sequence.