Update to Moody’s

{
  "name": "moody-s-explore-mcp",
  "description": "Discover and safely explore Moody's MCP tools. Use when the user wants to see what Moody's data is available, verify MCP connectivity, look up an entity, or run a lightweight ratings/research probe before deeper analysis.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 276
    }
  ],
  "skill_md_contents": "---\nname: moody-s-explore-mcp\ndescription: Discover and safely explore Moody's MCP tools. Use when the user wants to see what Moody's data is available, verify MCP connectivity, look up an entity, or run a lightweight ratings/research probe before deeper analysis.\n---\n\n<!-- To activate this skill, add `\"skills\": \"./skills/\"` to `.codex-plugin/plugin.json`. -->\n\n# Explore Moody's MCP\n\nUse this skill to discover Moody's MCP capabilities and run a minimal, read-only probe before deeper credit and financial analysis workflows.\n\n## When to Use\n\n- User asks \"what can Moody's do?\", \"list Moody's tools\", or \"is Moody's connected?\"\n- User wants a quick entity lookup or ratings snapshot without a full credit memo\n- You need to verify which Moody's tools are available in the current session\n\n## Prerequisites\n\n- Moody's plugin installed with the enterprise store MCP linked via `.app.json`\n- OAuth completed on first use - auth errors mean the user should reconnect the Moody's integration\n\n## Workflow\n\n### Step 1: Verify MCP Availability\n\nConfirm Moody's MCP tools appear in the session. If tools are missing or calls fail with auth errors, stop and ask the user to install or re-authenticate the Moody's plugin.\n\n### Step 2: Discover Tools\n\nList available Moody's MCP tools. **Read each tool's schema before calling** - tool names and parameters may differ from the reference list below.\n\nIf tools appear as deferred, batch-load schemas in a single discovery pass rather than calling tools blindly.\n\n### Step 3: Smoke Test - Entity Lookup\n\nRun `findEntity` (or the equivalent entity-search tool) with a company name or identifier the user provides. If no company was given, ask for one before proceeding.\n\nPresent matches clearly and confirm which entity to use. **Never invent entity IDs** - always resolve through entity search first.\n\n### Step 4: Light Probe (Optional)\n\nAfter confirming an entity, call one read-only tool to demonstrate connectivity:\n\n- `getEntityRatings` - current rating, outlook, and recent history\n- `searchEntityDocuments` - recent research documents for the entity\n- `getEntityPeers` - comparable entities for context\n\nPick the tool that best matches the user's question. Read the schema, call once, and summarize results.\n\n### Step 5: Summarize\n\nReport:\n\n1. Which tools are available in this session\n2. The entity resolved (name + ID)\n3. What data was retrieved in the probe\n4. Suggested next steps (e.g. full ratings history, peer comparison, document deep-dive)\n\n## Known Tools (Reference - Verify Live Schemas)\n\n| Tool                     | Purpose                                          |\n| ------------------------ | ------------------------------------------------ |\n| `findEntity`             | Search entities by name, identifier, or metadata |\n| `getEntityRatings`       | Current ratings, outlooks, and rating history    |\n| `getEntityPeers`         | Comparable peer entities                         |\n| `searchEntityDocuments`  | Search Moody's research document library         |\n| `getEntityScorecard`     | Rating scorecard metrics and methodology inputs  |\n| `getEntityRatingDrivers` | Upgrade and downgrade factor analysis            |\n| `getEntityEsg`           | ESG factors affecting credit quality             |\n\nTool names above are reference only. Always confirm against live MCP tool descriptors before calling.\n\n## Guardrails\n\n- Read tool schemas before every call\n- Do not invent entity IDs - always resolve via entity search first\n- Cite Moody's as the data source\n- This skill provides research context, not investment advice\n- On empty or error responses, report clearly and stop - do not retry blindly or fabricate data\n"
}