Aave Liquidation Monitor
by @jgramajo4
Proactive monitoring of Aave V3 borrow positions with liquidation alerts. Queries user collateral, debt, and health factor across chains (Ethereum, Polygon, Arbitrum, etc.). Sends urgent alerts to Telegram/Discord/Slack when health factor drops below configurable thresholds (critical at 1.05, warning at 1.2). Use when you need continuous monitoring of Aave positions, want alerts before liquidation risk occurs, or need periodic summaries of your borrowing health.
clawhub install aave-liquidation-monitorπ About This Skill
name: aave-liquidation-monitor description: "Proactive monitoring of Aave V3 borrow positions with liquidation alerts. Queries user collateral, debt, and health factor across chains (Ethereum, Polygon, Arbitrum, etc.). Sends urgent alerts to Telegram/Discord/Slack when health factor drops below configurable thresholds (critical at 1.05, warning at 1.2). Use when you need continuous monitoring of Aave positions, want alerts before liquidation risk occurs, or need periodic summaries of your borrowing health."
Aave Liquidation Monitor
Quick Start
Configure your wallet and thresholds once, then the skill runs automatically every 6 hours (configurable).
Step 1: Initialize Your Config
Run /aave-config init to set up:
Example:
/aave-config init
β Wallet: 0x1234...5678
β Thresholds: 1.05 (critical), 1.2 (warning)
β Interval: 6 hours
β Verbosity: quiet (alerts only)
β Channel: telegram
Step 2: Test the Monitor
Run /aave-monitor check to fetch your position immediately and see the alert format:
/aave-monitor check
β Fetching position for 0x1234...5678 on Ethereum...
β Health Factor: 2.31 (Stable β)
β Total Collateral: $50,342.12
β Total Debt: $21,804.00
β Borrowed Assets: USDC (15,000), WETH (0.5), USDT (6,804)
β Supplied Assets: WETH (10), USDC (20,000), DAI (30,000)
Step 3: Enable Proactive Monitoring
Run /aave-monitor enable to start automatic checks every 6 hours. The skill registers a cron job that silently runs in the background and alerts you only when health factor drops below threshold.
For manual override:
/aave-monitor enable --interval 4 # Check every 4 hours
/aave-monitor disable # Stop monitoring
/aave-monitor status # See current config + last check result
Configuration Reference
See references/config-guide.md for detailed config options, chain support, and threshold guidance.
See references/aave-api.md for Aave V3 GraphQL schema and query patterns.
Security & Credentials: See SECURITY.md for how credentials are handled and threat model.
For auditors: See SECURITY.md for code review checklist and architecture details.
How It Works
1. Query Phase: Calls Aave V3 GraphQL API with your wallet address 2. Analysis Phase: Extracts health factor, collateral, debt, borrowed/supplied assets 3. Alert Logic: - If HF < 1.05 β CRITICAL (red alert, send immediately) - If HF < 1.2 β WARNING (yellow alert, send immediately) - If HF > 1.5 β STABLE (no alert, unless verbose mode enables daily summary) 4. Notification Phase: Posts alert to your configured channel with clear summary 5. Retry Logic: If API fails, retries up to 3 times with exponential backoff
Error Handling
Security & Credentials
NO private keys are requested or stored β this is read-only monitoring only.
How messaging credentials work
The skill uses OpenClaw's built-in message routing β it does NOT store Telegram, Discord, or Slack tokens.
1. You configure your messaging channel in OpenClaw (outside this skill) 2. The skill calls OpenClaw's messaging API with just the alert text 3. OpenClaw routes the message using your configured channels
Example:
/aave-config set channel telegram
β OpenClaw sends alerts via your pre-configured Telegram channel
You must have a messaging channel already set up in OpenClaw. See OpenClaw docs for setting up Telegram/Discord/Slack integrations.
Data handling
What the skill accesses
β Aave GraphQL API (public) β reads your position data β OpenClaw message routing β sends formatted alerts to your configured channel β Cron scheduler β runs background checks on your interval
β Does NOT:
Examples
Alert Examples
Critical Alert (HF < 1.05):
π¨ AAVE LIQUIDATION RISK β CRITICAL
Health Factor: 1.02 (Liquidation threshold: 1.0)
β° Action required immediately!π Position Summary:
Total Collateral: $50,000
Total Debt: $48,000
Debt Ratio: 96%
Borrowed (at risk):
USDC: 40,000
WETH: 8 ETH (~$31k) Suggested Actions:
1. Repay debt (especially WETH)
2. Supply more collateral
3. Enable eMode if available (higher LTV on correlated assets)
Last checked: 2026-02-11 08:15 UTC
Warning Alert (HF < 1.2):
β οΈ AAVE WARNING
Health Factor: 1.15 (Approaching 1.2 threshold)Position approaching liquidation. Consider:
Repaying $2,000 USDC or
Adding $5,000 collateral (WETH or stETH)
Stable Position (HF > 1.5, verbose mode only):
β
AAVE POSITION HEALTHY
Health Factor: 2.31
Total Collateral: $50,342.12
Total Debt: $21,804.00All clear. Check again tomorrow.
Command Examples
# One-time position check
/aave-monitor checkStart automatic monitoring
/aave-monitor enableChange thresholds (e.g., earlier warning at HF 1.3)
/aave-config set thresholds 1.05 1.3Check monitoring status
/aave-monitor statusView last 5 check results with alerts
/aave-monitor history 5Disable monitoring temporarily
/aave-monitor disable
Chains Supported
Primary: Ethereum mainnet
Also works (with same config address where applicable):
Edit scripts/monitor.js to add chains or customize per-chain endpoints.
Customization
Change check interval:
/aave-config set interval 4 # Check every 4 hours
Change alert thresholds:
/aave-config set thresholds 1.1 1.25 # Critical at 1.1, warning at 1.25
Enable verbose mode (daily summaries even if stable):
/aave-config set verbosity verbose
Switch notification channel:
/aave-config set channel discord
Implementation Details
See scripts/monitor.js for the core monitoring logic (GraphQL queries, health factor calculation, alert formatting).
See scripts/cron-runner.js for cron job integration with OpenClaw's cron scheduler.
Troubleshooting
"Invalid wallet address"
β Check format: must be 0x... format. Try /aave-config view to see current config.
"Health factor not returned by API"
β Wallet may not have Aave position. Try /aave-monitor check for immediate response.
"API endpoint unreachable" β Aave API may be down. Skill retries automatically. Check https://status.aave.com.
"No notifications sent"
β Check that your notification channel is active. Run /aave-monitor check to test delivery.
Notes
Last Updated: 2026-02-11 | Status: Ready for configuration
π‘ Examples
Alert Examples
Critical Alert (HF < 1.05):
π¨ AAVE LIQUIDATION RISK β CRITICAL
Health Factor: 1.02 (Liquidation threshold: 1.0)
β° Action required immediately!π Position Summary:
Total Collateral: $50,000
Total Debt: $48,000
Debt Ratio: 96%
Borrowed (at risk):
USDC: 40,000
WETH: 8 ETH (~$31k) Suggested Actions:
1. Repay debt (especially WETH)
2. Supply more collateral
3. Enable eMode if available (higher LTV on correlated assets)
Last checked: 2026-02-11 08:15 UTC
Warning Alert (HF < 1.2):
β οΈ AAVE WARNING
Health Factor: 1.15 (Approaching 1.2 threshold)Position approaching liquidation. Consider:
Repaying $2,000 USDC or
Adding $5,000 collateral (WETH or stETH)
Stable Position (HF > 1.5, verbose mode only):
β
AAVE POSITION HEALTHY
Health Factor: 2.31
Total Collateral: $50,342.12
Total Debt: $21,804.00All clear. Check again tomorrow.
Command Examples
# One-time position check
/aave-monitor checkStart automatic monitoring
/aave-monitor enableChange thresholds (e.g., earlier warning at HF 1.3)
/aave-config set thresholds 1.05 1.3Check monitoring status
/aave-monitor statusView last 5 check results with alerts
/aave-monitor history 5Disable monitoring temporarily
/aave-monitor disable
π Tips & Best Practices
Last Updated: 2026-02-11 | Status: Ready for configuration