Galleon Aave Position

Name: Galleon Aave Position
Author: galleonlabs

ASecurity

Use when checking an Aave V3 health factor, sizing a borrow, or planning a repay and collateral withdrawal; use for eMode and isolation constraints, not Aave V4.

2 stars

0 votes

0 copies

0 views

Added 9/28/2026

ai-agentsgitdocumentation

Security Analysis

A100/100

Scanned 9/28/2026

Install to Claude Code

$npx -y skills add galleonlabs/crypto-defi-skills --skill galleon-aave-position --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Galleon Aave Position?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Galleon Aave Position

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/galleonlabs-galleon-aave-position/badge)](https://www.skillsdirectory.com/skills/galleonlabs-galleon-aave-position)

More formats (shields.io, HTML) on the badges page.

Files

SKILL.md

---
name: galleon-aave-position
description: "Use when checking an Aave V3 health factor, sizing a borrow, or planning a repay and collateral withdrawal; use for eMode and isolation constraints, not Aave V4."
license: MIT
compatibility: "Read-only EVM RPC or official provider tools; Bun is optional for offline examples. No signer required."
metadata:
  version: "0.2.0"
  author: "Andrew Wilkinson and Galleon Labs"
  source: "https://github.com/galleonlabs/crypto-defi-skills"
---

# Aave V3 position risk

Produce a borrow/repay decision for one **EVM Aave V3 pool**. First identify chain, PoolAddressesProvider, Pool, account, requested debt asset and action. V4 hubs/spokes and Aptos require their own interfaces; stop this recipe if the deployment is not V3.

## Read and reconcile

1. Resolve the pool from the official address book, then call the provider's `getPool()` and `getPriceOracle()`. Pin reads to one block and record its timestamp. Do not reuse another chain's deployment or assume USD base units.
2. Read `getUserAccountData(account)` and `getUserEMode(account)`. Account data includes collateral/debt in the oracle base currency, weighted liquidation threshold/LTV in basis points, and health factor in 1e18 units. Read the oracle base unit and asset prices before converting values.
3. Enumerate supplied and borrowed reserves using the deployment's documented data provider/SDK. For each, collect token decimals, aToken and variable-debt balances, collateral enablement, applicable eMode threshold, current variable rate, caps, available underlying, freeze/pause flags, isolation debt ceiling and borrowable-in-isolation status. An aggregate health factor cannot establish that a particular new borrow is permitted.
4. Reconcile your per-reserve weighted collateral and debt with `getUserAccountData`. Stop sizing if the discrepancy cannot be explained by accrual, rounding, eMode or different blocks. Do not infer available liquidity from supply caps.

## Decide

Build current, requested-post-state and stressed-post-state rows. Health factor is liquidation-threshold-weighted collateral value divided by debt value. Apply collateral and debt price shocks separately; include interest over the requested holding period. Changing eMode or collateral composition invalidates the old weighted threshold. Zero debt means no finite liquidation health factor, not a divide-by-zero error.

Use a user-selected minimum health factor, never a universal safe threshold. Report the protocol's maximum separately from that user's budget. A collateral withdrawal can reduce health faster than its unweighted value suggests. Borrowing at the limit leaves no allowance for debt accrual or oracle moves.

For a requested borrow, prepare `borrow(asset, amount, 2, 0, onBehalfOf)` only after reserve checks. Borrowing for another account requires credit delegation, not ERC20 approval. A repay uses the debt asset, and a subsequent withdrawal must be simulated against the repaid state. Exact full repayment needs an accrual buffer or the documented full-repay mode for the actual caller; never assume a displayed debt amount clears it.

## Evidence and completion

Return the requested decision, exact deployment and chain, block/time, raw-unit observations, calculation assumptions, and the next missing read. Distinguish an indexed estimate, an onchain read, a simulated call and a confirmed transaction. Research ends with an actionable decision record; it does not require connecting a wallet.

For a requested write, prepare the complete unsigned sequence and simulate with the actual sender, amount, recipient and allowance state. Preserve authorization already supplied; research does not grant debt, spending or signing authority. Never request keys. After an authorized transaction, verify its receipt and the relevant balance or position change. On an ambiguous timeout, reconcile its hash and nonce before retrying.

Read [protocol references and worked record](references/recipe.md) only for the selected operation. Documentation checked 2026-09-27; refresh deployments and current parameters at use time. This directory is independently installable.

Attribution

galleonlabs

View source More from galleonlabs →

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

--- name: galleon-aave-position description: "Use when checking an Aave V3 health factor, sizing a borrow, or planning a repay and collateral withdrawal; use for eMode and isolation constraints, not Aave V4." license: MIT compatibility: "Read-only EVM RPC or official provider tools; Bun is optional for offline examples. No signer required." metadata: version: "0.2.0" author: "Andrew Wilkinson and Galleon Labs" source: "https://github.com/galleonlabs/crypto-defi-skills" --- # Aave V3 position risk Produce a borrow/repay decision for one **EVM Aave V3 pool**. First identify chain, PoolAddressesProvider, Pool, account, requested debt asset and action. V4 hubs/spokes and Aptos require their own interfaces; stop this recipe if the deployment is not V3. ## Read and reconcile 1. Resolve the pool from the official address book, then call the provider's `getPool()` and `getPriceOracle()`. Pin reads to one block and record its timestamp. Do not reuse another chain's deployment or assume USD base units. 2. Read `getUserAccountData(account)` and `getUserEMode(account)`. Account data includes collateral/debt in the oracle base currency, weighted liquidation threshold/LTV in basis points, and health factor in 1e18 units. Read the oracle base unit and asset prices before converting values. 3. Enumerate supplied and borrowed reserves using the deployment's documented data provider/SDK. For each, collect token decimals, aToken and variable-debt balances, collateral enablement, applicable eMode threshold, current variable rate, caps, available underlying, freeze/pause flags, isolation debt ceiling and borrowable-in-isolation status. An aggregate health factor cannot establish that a particular new borrow is permitted. 4. Reconcile your per-reserve weighted collateral and debt with `getUserAccountData`. Stop sizing if the discrepancy cannot be explained by accrual, rounding, eMode or different blocks. Do not infer available liquidity from supply caps. ## Decide Build current, requested-post-state and stressed-post-state rows. Health factor is liquidation-threshold-weighted collateral value divided by debt value. Apply collateral and debt price shocks separately; include interest over the requested holding period. Changing eMode or collateral composition invalidates the old weighted threshold. Zero debt means no finite liquidation health factor, not a divide-by-zero error. Use a user-selected minimum health factor, never a universal safe threshold. Report the protocol's maximum separately from that user's budget. A collateral withdrawal can reduce health faster than its unweighted value suggests. Borrowing at the limit leaves no allowance for debt accrual or oracle moves. For a requested borrow, prepare `borrow(asset, amount, 2, 0, onBehalfOf)` only after reserve checks. Borrowing for another account requires credit delegation, not ERC20 approval. A repay uses the debt asset, and a subsequent withdrawal must be simulated against the repaid state. Exact full repayment needs an accrual buffer or the documented full-repay mode for the actual caller; never assume a displayed debt amount clears it. ## Evidence and completion Return the requested decision, exact deployment and chain, block/time, raw-unit observations, calculation assumptions, and the next missing read. Distinguish an indexed estimate, an onchain read, a simulated call and a confirmed transaction. Research ends with an actionable decision record; it does not require connecting a wallet. For a requested write, prepare the complete unsigned sequence and simulate with the actual sender, amount, recipient and allowance state. Preserve authorization already supplied; research does not grant debt, spending or signing authority. Never request keys. After an authorized transaction, verify its receipt and the relevant balance or position change. On an ambiguous timeout, reconcile its hash and nonce before retrying. Read [protocol references and worked record](references/recipe.md) only for the selected operation. Documentation checked 2026-09-27; refresh deployments and current parameters at use time. This directory is independently installable.