Update to MSCI Connector

{
  "name": "methodology",
  "description": "Use this skill for questions about how an MSCI index is constructed, screened, reviewed/rebalanced, weighted, capped, buffered, migrated between size segments, or otherwise governed by MSCI methodology. Use official methodology search rather than memory.",
  "included_files": [],
  "skill_md_contents": "---\nname: methodology\ndescription: >-\n  Use this skill for questions about how an MSCI index is constructed, screened, reviewed/rebalanced, weighted, capped, buffered, migrated between size segments, or otherwise governed by MSCI methodology. Use official methodology search rather than memory.\n---\n\n# MSCI methodology, grounded in official documents\n\nAnswer rule questions from the methodology snippets returned by the MSCI Index app.\n\n## Output\n\nGive the direct rule/explanation, identify the methodology document/layer when returned, and include a short governing excerpt when useful. Keep quotations focused; explain the rule in your own words around them.\n\n## Workflow\n\n### Index-specific question\n\n1. Resolve the index with `search_index_indexes`.\n2. Call `search_index_methodology_stack` with the resolved index code and a concise substantive query. Prefer the stack because an index can inherit rules from several methodology layers.\n3. If the first hits are weak, retry with the MSCI term of art suggested by the retrieved text or user intent.\n\n### Named methodology document\n\n1. Use `list_index_methodologies` for the relevant effective date.\n2. Select the document code matching the user's named methodology.\n3. Call `search_index_methodology` with a concise search term.\n\n### Historical rule question\n\nUse the historical `asOfDate` relevant to the rebalance/event instead of assuming today's methodology.\n\n## Source discipline\n\n- When official methodology `hits`/`results` contain text, answer **only** from those retrieved snippets. Do not blend training-memory rules into the answer.\n- If official methodology search returns no usable text, say the official corpus did not return a matching passage. If you provide a general-knowledge fallback, label it clearly as not sourced from the official MSCI methodology.\n- If the snippets do not settle the exact question, say what they do establish and where the gap remains.\n\n## Handoff to data workflows\n\nMethodology answers the rule; data tools answer whether a security/index meets it. For example, \"what is the liquidity screen?\" is methodology; \"does Company X pass it?\" is eligibility.\n\n## Guardrails\n\n- Never state an MSCI rule as authoritative without retrieved official support when methodology text is available.\n- Do not generalize one index family's rule to another without confirming the governing document stack.\n- Do not use a description/rebalancing-calendar datapoint as a substitute for the methodology when the user asks the review frequency or construction rule.\n"
}