Portfolio Monitoring Workflow Prompt
Designs a read-only monitoring system across wallets and chains, with exposure limits and drift alerts.
/ quick answer
Use to specify portfolio automation. Read-only by design — no keys involved. Designs a read-only monitoring system across wallets and chains, with exposure limits and drift alerts.
Design a read-only crypto portfolio monitoring system. Addresses per chain: [LIST] Protocol positions: [LIST] Exposure limits desired: [per asset / chain / narrative / protocol] Reporting cadence: [DAILY / WEEKLY] Tools available: [portfolio API, automation platform, notification channel] Produce: 1. Data collection plan per chain and per protocol, including how deposited positions are valued. 2. Aggregation model: how holdings map to asset, chain, narrative and protocol exposure. 3. Limit definitions with thresholds and the rationale for each. 4. Drift detection: what counts as material change versus normal volatility. 5. Alert rules for protocol-level events on held positions (depeg, TVL collapse, governance). 6. Report format: the exact fields in the recurring snapshot. 7. Data-quality safeguards: missing prices, unindexed tokens, double counting of receipt tokens. 8. Explicit statement of what stays manual. No keys, no signing, no execution in this design.
Collection: three chains via portfolio API plus two protocol subgraphs for deposits; receipt tokens mapped to underlying to avoid double counting. Limits: 25% per asset, 50% per chain, 30% per narrative, 15% per protocol. Drift: a breach sustained over 48h, not intraday. Alerts: stablecoin depeg over 0.5%, protocol TVL down 30% in 24h. Report: asset, chain, venue, value, %, 7d delta, limit status. Manual: all rebalancing.
What does the Portfolio Monitoring Workflow Prompt prompt do?
Use to specify portfolio automation. Read-only by design — no keys involved.
Which AI models work with this prompt?
It is model-agnostic: it works with any capable general model. Replace the bracketed variables with your own context before running it.
What output should I expect?
Collection: three chains via portfolio API plus two protocol subgraphs for deposits; receipt tokens mapped to underlying to avoid double counting. Limits: 25% per asset, 50% per chain, 30% per narrative, 15% per protocol. Drift: a breach sustained over 48h, not intraday. Alerts: stablecoin depeg ove.
/ continue exploring
Related concepts
The vocabulary this page depends on.
- →Crypto Risk Management
Risk management in crypto is position sizing plus custody hygiene: deciding what you can lose per trade and what a single compromise can reach.
- →Crypto Automation
Crypto automation is rule-based execution of monitoring, alerting and recurring on-chain actions, so decisions are made once and applied consistently.
- →Stop Loss & Take Profit
Stop loss and take profit are pre-committed exit rules that convert a discretionary decision into an executable instruction.
Related workflows
Turn this into a repeatable process.
- →Crypto Portfolio Monitoring
Aggregate positions across wallets and chains, compute real exposure, and alert on drift instead of checking balances manually.
- →Automated Crypto Alerts
Define the conditions that would change a decision, monitor them automatically, and receive one clean notification instead of watching charts.
- →Build a Research Automation Pipeline
Question in, sourced structured brief out — on a schedule.
- →Automated DCA Workflow
Set a recurring buy schedule that runs without your attention, with sizing and frequency chosen so fees stay negligible.
Related tool stacks
The tools that run it in production.
- →Crypto Automation Stack
Automation platform, data APIs, alerting and optional wallet execution — the operational layer for monitoring and recurring actions.
Related prompts
Reusable prompts for this job.
- →Crypto Risk Analysis Prompt
Runs a pre-mortem on a position or protocol: enumerates failure modes, likelihood, impact and observable early warnings.
- →Recurring Crypto Workflow Prompt
Specifies a safe recurring on-chain automation with spend caps, idempotency, failure handling and a kill switch.
- →Crypto Portfolio Analysis Prompt
Audits a portfolio for hidden concentration, correlated exposure, custody risk and missing exit plans.
- →Build An Alert Workflow Prompt
Designs a complete alerting pipeline — events, sources, thresholds, deduplication and delivery — from a plain description.
Related use cases
How people apply it, and what came out.
- →Monitor A Crypto Portfolio
Aggregating six addresses across three chains revealed that a portfolio believed to hold 14 positions actually held one concentrated bet.
- →Automate Portfolio Monitoring
A weekly automated snapshot with limit breach alerts replaced manual reconciliation and caught a protocol TVL collapse within hours.
- →Get Token Alerts
Replacing price-only alerts with condition-based rules cut notifications by 80% and caught a liquidity withdrawal before price reflected it.
- →Automate DCA
Switching from daily manual buys to a weekly automated schedule cut fee drag from 4.1% to 0.3% of each buy and removed missed cycles.
Comparisons & alternatives
Pick between the options.
- →Best AI Workflow Automation Tools: n8n vs Zapier vs Make
The three tools most operators consider for AI workflow automation — compared on pricing, AI integration and technical flexibility.
- →Manual Trading vs Automated Trading
Manual trading adapts to context; automation enforces consistency. Most durable setups automate monitoring and keep judgement human.
- →DCA vs Lump Sum
DCA spreads entry over time to reduce timing risk and behavioural error; lump sum maximises exposure time at the cost of concentrated entry risk.
- →DeFi vs Traditional Finance
DeFi offers open access, composability and transparent rules; traditional finance offers legal recourse, insurance and stability.