AI-friendly Web3 investment infrastructure for autonomous agents. Use when (1) discovering and analyzing DeFi/NFT investment opportunities, (2) executing secure transactions via local keystore signer REST API with preview-approve-execute state machine, (3) managing portfolio with dashboards and expiry alerts. Supports base and ethereum chains, configurable security constraints including whitelist protection, transaction limits, and mandatory simulation before execution.
AI-friendly Web3 investment infrastructure for autonomous agents. Use when (1) discovering and analyzing DeFi/NFT investment opportunities, (2) executing secure transactions via local keystore signer REST API with preview-approve-execute state machine, (3) managing portfolio with dashboards and expiry alerts. Supports base and ethereum chains, configurable security constraints including whitelist protection, transaction limits, and mandatory simulation before execution.
Web3 Investor Skill
Purpose: Enable AI agents to safely discover, analyze, and execute DeFi investments.
Core Philosophy: Data-driven decisions. No generic advice without real-time discovery.
⚠️ Critical Rules (MUST FOLLOW)
Rule 1: Discovery First
When user asks for investment advice:
❌ WRONG: Give generic advice immediately (e.g., "I recommend Aave")
✅ CORRECT:
1. Collect investment preferences (chain, token, risk tolerance)
2. Run discovery to get real-time data
3. Analyze data
4. Provide data-backed recommendations
Rule 2: User's LLM Makes Decisions
This skill provides raw data only
Investment analysis and recommendations are the responsibility of the user's LLM/agent
This skill is NOT responsible for investment outcomes
Rule 3: Risk Acknowledgment
APY data comes from third-party APIs and may be delayed or inaccurate
Investment decisions are made at the user's own risk
Always DYOR (Do Your Own Research)
Rule 4: Verify Execution Capability Before Trading
Before attempting any transaction, the agent MUST check signer availability:
❌ WRONG: Directly call preview/execute without checking API
✅ CORRECT:
1. Check if signer API is reachable (call balances endpoint)
2. If unreachable → inform user: "Signer service unavailable, please check SETUP.md"
3. Never proceed with preview if signer is unavailable
Health Check Command:
python3 scripts/trading/trade_executor.py balances --network base
# If success → signer is available# If error E010 → signer unavailable, stop and inform user
Rule 5: Check Payment Capability FIRST (NEW in v0.5.0)
Before asking user for transaction details, ALWAYS check execution readiness:
❌ WRONG: Ask "How much do you want to invest?" without checking payment capability
✅ CORRECT:
1. Run: python3 scripts/trading/preflight.py check --network <chain>
2. Inform user of available payment methods
3. Then ask for transaction details
Preflight Check Output:
{"recommended":"eip681_payment_link","methods":[{"method":"keystore_signer","status":"unavailable"},{"method":"eip681_payment_link","status":"available"}],"message":"⚠️ No local signer. Use EIP-681 payment link."}
Enable/disable whitelist filtering in trade execution
whitelist_tokens
[...]
Allowed tokens for trading
whitelist_protocols
[...]
Allowed protocols for interaction
Note: When whitelist_enabled is false (default), trade execution skips whitelist checks, allowing broader protocol/token access. Set to true to enforce strict whitelist validation.
When using this skill for transaction generation, include this template:
Output structured transaction request (JSON), do not execute directly.
All transactions must go through preview -> approve -> execute.
If transaction parameters cannot be determined, return clarification, do not guess.
