← MSCI ConnectorCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to MSCI Connector
Snapshot Sep 30, 2026 · 22:51 UTC · version 8.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use this skill when the user asks how much AUM is benchmarked to an MSCI index, the ETF/non-ETF split, which linked exchange-traded products track the index, who provides them, or passive ownership linked to an MSCI security.",
"included_files": [],
"name": "index-aum",
"skill_md_contents": "---\nname: index-aum\ndescription: >-\n Use this skill when the user asks how much AUM is benchmarked to an MSCI index, the ETF/non-ETF split, which linked exchange-traded products track the index, who provides them, or passive ownership linked to an MSCI security.\n---\n\n# AUM benchmarked to an MSCI index\n\nUse the MSCI Index app to report benchmark-linked AUM, distinct from index market capitalization and distinct from fund flows.\n\n## Output\n\nLead with total benchmarked AUM, then ETF/non-ETF split and their own as-of dates. If the user asks for linked products, include provider and show how many rows are displayed versus available.\n\n## Workflow\n\n1. Resolve the index with `search_index_indexes` using a concise name such as `EAFE`, `World`, `EM`, or `ACWI`.\n2. Discover the AUM aggregate datapoints with `search_index_datapoints`; do not hardcode ids without discovery. Search concepts should include total AUM, ETF AUM/as-of date, and non-ETF AUM/as-of date.\n3. Read `constraints.notes` and fetch supported point-in-time data with `fetch_index_data`.\n4. For linked products, discover the list-cardinality linked-ETP datapoint. Use `fetch_index_data` with pagination, ordering, and supported filters such as provider/management style/taxonomy only when documented by the tool contract.\n5. For security-level benchmark-linked AUM, resolve the security with `search_index_securities` and discover the constituent/security AUM fields before fetching.\n\n## Presentation\n\n- Identify the index as `<name> (<msci_index_code>)`.\n- State AUM units exactly; if returned in millions of USD, convert to billions only with an explicit conversion label.\n- ETF and non-ETF as-of dates may differ. Put each date beside its figure rather than assigning one common date to the total unless the returned dates actually agree.\n- If useful, show ETF and non-ETF as percentages of the summed split, but do not imply those percentages are fund flows.\n\n## Guardrails\n\n- Benchmarked AUM is not index market capitalization.\n- AUM level is not period fund flow. If the user wants inclusion/rebalance flow sizing, use the `index-flows` workflow.\n- Product coverage reflects the connected MSCI product dataset; absence from the returned list is not proof a product does not exist.\n- Respect entitlements and pagination. Do not claim complete coverage when only one page was fetched.\n"
}SHA-256 of public snapshot: 02ac3b96d1fb3322ad3629d981c28e7c05fd2796db1020040922cd0093633882