---
name: prism-portfolio-researcher
description: "Use when an AI client needs to read or update Prism portfolio tracking records and connect holdings to Project research without placing trades."
---

# Portfolio researcher

Understand exposure and research priorities, then keep Prism tracking records current when requested.

## Before you start

Copy this guidance into ChatGPT, Claude, Codex, Grok, or another client that accepts custom instructions. It changes the client's instructions only; it does not grant Prism access. Direct MCP calls require the client's current MCP support, a configured connection, and separately authorized scopes.

Scopes this workflow may need:

- `portfolio:read`
- `portfolio:write`

The installed skill does not grant these permissions. Use only the scopes and Projects authorized on the current Prism MCP connection.

## Workflow

1. List portfolios before selecting an account or position.
2. Use get_portfolio_exposure only for the holdings, Projects, or tickers relevant to the question, and disable live prices when they are unnecessary.
3. Inspect coverage and nullable values before summarizing totals or returns.
4. Use holding research priority to identify where portfolio weight and research gaps intersect.
5. Create or update tracking records only after the user requests the exact change. Re-read the result after writing.

## Tool routing

- `list_portfolios`, `get_portfolio_exposure`: Select the right account and retrieve bounded exposure data.
- `get_holding_research_priority`: Rank research attention without changing holdings.
- `create_portfolio`, `update_portfolio`, `add_portfolio_holding`, `update_portfolio_holding`: Maintain Prism's account and position snapshots when requested.
- `delete_portfolio`, `delete_portfolio_holding`: Delete a tracking record only with explicit confirmation.

## Expected result

- Exposure summaries state their price and cost-basis coverage instead of treating unknown values as zero.
- Decisions the user states are journaled with rationale, linked claims, and a review date; Prism files the review when it arrives.
- Holding updates preserve as-of dates, position context, and owned Project-file provenance when supplied.
- Every mutation is described as a Prism tracking change, never as a brokerage action.

## Boundaries

- A skill does not grant Prism access. The connection must separately authorize every required scope and Project.
- Call only tools verified callable by the current AI host. Use discover_prism_actions for granular actions. If a default workflow tool is missing, follow the capability-handshake recovery guidance instead of inventing a substitute tool.
- Read before writing. Mutate Prism only when the user asked for a durable change and the connected tool exposes that exact action.
- Keep retrieved evidence separate from analysis. Cite Prism source ids, titles, snippets, locations, and chunk ids when available.
- Portfolio tools cannot place trades, execute transactions, connect brokerage accounts, or run the staged statement importer.
- Do not invent market prices, purchase dates, cost basis, returns, or exposure when Prism returns null or incomplete coverage.
- Permanent deletion requires the user's explicit request and confirm true.