Portfolio Manager analyzes an investment portfolio in seven steps. It fetches account equity, positions and history from Alpaca through the MCP server, or through a REST fallback, enriches each holding with market data, and examines allocation, concentration, risk metrics and performance. It then reviews the largest positions and lists rebalancing candidates ranked by priority.
A limited offline mode reviews a CSV of holdings or saved Alpaca positions JSON with no credentials and reports gross allocation and unrealized profit and loss only. The report carries an informational-only disclaimer, and the skill never places orders.
What You Get
- A Markdown portfolio report with allocation, diversification, risk and performance sections
- Per-position reviews for the top holdings with a stated action label
- Rebalancing candidates ranked by priority with a rationale each
- An offline CSV review with gross allocation and per-position unrealized profit and loss
- Holdings reconciliation reports that compare broker and memory snapshots
Common Use Cases
- Reviewing allocation and sector concentration across a brokerage account
- Checking a paper trading account through the connection check script
- Running a limited review of a CSV export without any credentials
- Reconciling broker positions with a saved snapshot before a weekly allocation review
What Makes It Unique
It supports three data routes in one skill: the Alpaca MCP Server, a REST fallback for scheduled jobs that do not expose MCP tools, and an offline CSV mode. It tells Claude to compute exposure against equity so a margin-funded account does not look benign, and it includes a reconciliation gate that stops the review when snapshot completeness or freshness cannot be established. Related skills handle dividend review monitoring and tax planning.
Under The Hood
Claude uses the Alpaca MCP tools for account info, positions and portfolio history when they are connected, and can fall back to the Alpaca REST API using your Alpaca key, secret and paper-or-live setting from environment variables. The connection check script runs from the shell, prints a redacted diagnostic and places no orders. Claude can also use web search for fundamentals and news on holdings. The CSV and reconciliation scripts read local files and write JSON and Markdown reports, and the final analysis report is saved to the repository root. The setup reference suggests that you append your Alpaca key and secret to a shell startup file such as .bashrc and create a config file under your home folder; that is a step for you to take and the scripts do not do it. The connection check script only prints those same suggestions in its error message. Personal holdings stay on your machine in the offline mode.