Read prompts

These prompts assume you’ve connected Claude. They only read, so Read only access is enough. For prompts that record or change something, see Write prompts. Illustrative example. The figures are hypothetical, not a recommendation.

​

Check your rules

How far is my portfolio from my rules? Claude calls list_portfolios to find your portfolio, then get_portfolio_snapshot. The first call comes back without a verdict and lists the holdings that need a price (holdings_to_price). Claude asks you for those prices, or uses a price source you trust, then calls the snapshot again with prices and answers from compliance.status and the statuses per asset class. Allocait’s instructions ask Claude to use only prices you give it or from a source you trust, never a remembered or estimated one, because a wrong price gives a wrong status. If you connected by signing in (not with an API key), the first call also carries standing, read from the last stored quote at its as_of. See Standing. Which holdings are outside their size range? Claude reads the same priced snapshot and answers from compliance.size_violations: each holding outside the size range you set for its class, with its share of the portfolio and the range. Which of my rules would a 10% move put outside range? Claude calls check_allocations with the proposed percentages. Nothing is written; it’s a check against your existing rules. What amounts close the gap to my bands? Claude calls get_portfolio_snapshot with current prices and include_rebalance, then reads its rebalance block: the pro rata amounts that close each gap, and anything they can’t resolve. It’s arithmetic on your own bands. Allocait places nothing.

​

Get a brief

Brief me on my book, and from now on only what changed. Claude calls list_portfolios, then get_portfolio_snapshot for each portfolio with no prices. Signed in, it reads standing and gives its as_of. The first brief states the whole picture. Each later one reports only a change since the last: a range left or re-entered, a monitor whose state or close_state changed, a playbook newly needing input, an expired option.

​

Check a change

What does adding 40 shares of ALFA do to my rules? Claude calls check_trades with the change you describe and the prices you give it. It reports which of your rules the change puts outside range or leaves further outside, which symbols no rule looked at, and when your positions were last updated. It writes nothing and decides nothing. A failed call is no result. Allocait cannot approve, stop or place an order. See Check a change and Check result. You can also run the check_a_change prompt from your client’s prompt menu.

​

Size a holding

What share count would sit inside my size range for a new holding? Claude calls calculate_position_size with your portfolio value, the holding’s size range, and a sizing_mode: MINIMUM, BALANCED or MAXIMUM (the bottom, middle or top of that range). It returns the share count that sits inside the size range you set, and names that range. Nothing is written. To move a holding you already have by a set number of basis points, say so. Claude leaves the sizing mode and the share count out and passes basis_points, up or down. The answer can land outside your size range, and it says so. See Size a position.

​

Report a problem

To tell Allocait about a gap, ask Claude to send feedback. Feedback on tools or a task works on Read only; account help needs Read and change. See Agent feedback and Access levels.

​

Next steps