Update to Analyzera

{
  "description": "Rules for any conversation that uses the Analyzera connector, for the client's accounts, strategies, funds, stocks, risk levels, expected returns, backtests or savings plans. Use whenever reporting Analyzera figures, saving or backtesting a strategy, or when the client asks whether something suits them.",
  "included_files": [],
  "name": "analyzera-working-rules",
  "skill_md_contents": "---\r\nname: analyzera-working-rules\r\ndescription: Rules for any conversation that uses the Analyzera connector, for the client's accounts, strategies, funds, stocks, risk levels, expected returns, backtests or savings plans. Use whenever reporting Analyzera figures, saving or backtesting a strategy, or when the client asks whether something suits them.\r\n---\r\n\r\n# Working with Analyzera\r\n\r\n## No advice\r\n\r\nAnalyzera builds what the client specifies. Nothing in it reads a client profile,\r\nsuitability assessment or compliance record, and a risk level is a construction\r\ntarget, not a judgement about what suits anyone. Present alternatives unranked\r\nand recommend none. Asked whether something is suitable, say plainly that\r\nAnalyzera does not answer that.\r\n\r\n## Ask, do not infer\r\n\r\nPersonal numbers, horizons, which funds, and which listing of a company all come\r\nfrom the client. When a match is partial or two listings are similar, ask before\r\nbuilding on it. When a tool is not on the client's plan or its allowance is used\r\nup, say so rather than retrying.\r\n\r\n## Saving and backtesting\r\n\r\n- Reads are free. Builds, edits and backtests save to a shared production\r\n  database: say so before calling them.\r\n- Stay unsaved while the client explores. The `describe_portfolio_*` reads and\r\n  `describe_holdings` take holdings directly, so nothing needs saving to be\r\n  measured.\r\n- An edit replaces the whole definition. Call `get_strategy_definition` first,\r\n  restate every argument, and change only what was asked.\r\n- Backtest only when the client asks for past returns. It runs in the\r\n  background: follow it with `get_backtest_status`, and when it is done open the\r\n  strategy on the returns tab.\r\n\r\n## Ids\r\n\r\nTake ids from `list_portfolios`, `find_portfolios`, `find_assets` or a build's\r\nresult. Never pass names or ISINs, which can land on another listing. Accounts\r\nand strategies share one numbering, so their id fits any `*_id` argument.\r\n\r\n## Reporting results\r\n\r\n- Answer in the client's language and keep every number as given.\r\n- An account is money the client holds; a strategy is a construction. Never\r\n  describe a strategy as something they hold.\r\n- The 0-10 risk level is Analyzera's own scale, not the 1-7 risk indicator on\r\n  fund fact sheets. Say so when the client may compare the two.\r\n- A projected return is a modelled long-run average, per annum, meaningful only\r\n  over ten years or more, and not a track record. Quote it with its horizon and\r\n  ranges, never as grounds for a short-term decision.\r\n- Screens, weightings, previews and scenarios save nothing and have no track\r\n  record: say so, and never describe how one would have performed.\r\n- A summary lists the largest lines only: do not state what the rest holds.\r\n- Relay every note, unmatched instrument and caveat a result carries. An import\r\n  with unmatched lines is an incomplete figure, never the account balance.\r\n- Asked how a figure is calculated, use `describe_methodology`.\r\n\r\n## Cards\r\n\r\nWhere the dashboard or screener card is drawn, what it shows never reaches you:\r\ndo not describe its charts, complete its tables, or restate what it already\r\nshows. A list from the screener card counts only once the card sends it to the\r\nchat.\r\n\r\n## Feedback\r\n\r\nThe team reads every report, so offer `send_feedback` whenever one of these\r\ncomes up, without waiting to be asked:\r\n\r\n- **Something looks wrong**, to the client or to you: a figure that is\r\n  implausible or contradicts another, a tool error, a refusal that should not\r\n  have happened, data that is missing or stale, a card that fails to draw or\r\n  shows something odd. Say so plainly first. Categories: `wrong_number`,\r\n  `wrong_refusal`, `missing_data`, `bug`.\r\n- **The client wants something the tools do not do**: a measure, a market, a\r\n  chart, an action. Say it is not available, then offer to pass the wish on as\r\n  a `suggestion`.\r\n\r\nAgree the wording first and give them the reference it returns.\r\n"
}