- Home
- Skills
- Euler Xyz
- Agent Skills
- Euler Data
euler-data_skill
0
GitHub Stars
3
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill euler-xyz/agent-skills --skill euler-data- AGENTS.md27.5 KB
- metadata.json893 B
- SKILL.md2.6 KB
Overview
This skill is a developer toolkit for accessing Euler Finance V2 data and deploying vaults. It centralizes Lens contract queries, subgraph lookups, contract interfaces, and Euler Creator deployment flows. Use it to fetch vault and account state, historical metrics, and ABIs needed for integrations.
How this skill works
The skill exposes patterns for querying Lens contracts (AccountLens, VaultLens, OracleLens, IRMLens, UtilsLens, EulerEarnVaultLens) to read live on-chain state like positions, LTVs, IRM parameters, prices, APYs, and time-to-liquidation. It also shows how to fetch indexed historical data via the Euler subgraph for active accounts, vault factories, and per-account vault balances. Contract addresses and ABIs are referenced so integrations and no-code deployments via Euler Creator can be performed reliably.
When to use it
- Query account positions, health factor, and TTL for risk assessments
- Fetch vault configuration, LTVs, IRM details, or vault strategy state
- Check oracle prices and oracle configuration before pricing-sensitive actions
- Retrieve historical account or vault events via the Euler subgraph for analytics
- Access ABIs and addresses to integrate Euler into frontends, bots, or scripts
- Deploy or configure vaults using Euler Creator or no-code deployment flows
Best practices
- Prefer Lens contracts for precise, real-time on-chain reads; use subgraph for bulk historical queries
- Validate oracle price sources via OracleLens before executing trades or liquidations
- Cache ABI and address mappings but revalidate periodically against on-chain registries
- Combine AccountLens and VaultLens queries to compute user-level risk metrics consistently
- Avoid over-reliance on the subgraph for instant state — use it for aggregated or historical insights
Example use cases
- Build a dashboard displaying per-vault TVL, LTV, APY and active strategies using VaultLens and EulerEarnVaultLens
- Create a liquidation monitor that computes health and TTL via AccountLens and OracleLens
- Run a historical analysis of vault usage and active accounts using subgraph queries
- Implement front-end integrations that fetch ABIs and addresses to construct contract interactions
- Deploy a new vault through Euler Creator and verify configuration via VaultLens and IRMLens
FAQ
Use Lens contracts for live, precise risk checks. The subgraph is better for historical or aggregated queries.
Where do I find ABIs and addresses for integrations?
Reference the provided contract interface mappings and validate against on-chain registries before use.