plugins/moody-s/skills/moody-s-explore-mcp/SKILL.md
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.
npx skillsauth add openai/plugins moody-s-explore-mcpInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill to discover Moody's MCP capabilities and run a minimal, read-only probe before deeper credit and financial analysis workflows.
.app.jsonConfirm 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.
List available Moody's MCP tools. Read each tool's schema before calling - tool names and parameters may differ from the reference list below.
If tools appear as deferred, batch-load schemas in a single discovery pass rather than calling tools blindly.
Run 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.
Present matches clearly and confirm which entity to use. Never invent entity IDs - always resolve through entity search first.
After confirming an entity, call one read-only tool to demonstrate connectivity:
getEntityRatings - current rating, outlook, and recent historysearchEntityDocuments - recent research documents for the entitygetEntityPeers - comparable entities for contextPick the tool that best matches the user's question. Read the schema, call once, and summarize results.
Report:
| Tool | Purpose |
| ------------------------ | ------------------------------------------------ |
| findEntity | Search entities by name, identifier, or metadata |
| getEntityRatings | Current ratings, outlooks, and rating history |
| getEntityPeers | Comparable peer entities |
| searchEntityDocuments | Search Moody's research document library |
| getEntityScorecard | Rating scorecard metrics and methodology inputs |
| getEntityRatingDrivers | Upgrade and downgrade factor analysis |
| getEntityEsg | ESG factors affecting credit quality |
Tool names above are reference only. Always confirm against live MCP tool descriptors before calling.
development
Use when the user wants to spin up / create / launch / provision a DigitalOcean droplet (or "a remote dev box on DO") and connect to it from Codex as a remote SSH workspace.
data-ai
Search through Microsoft Teams chats or channels, triage unread or recent activity, draft follow-ups, and manage Planner tasks through connected Teams data.
tools
Motion / animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node.
development
SwiftUI ↔ Figma translation. Use whenever the user mentions Swift, SwiftUI, iOS, iPhone, or iPad — in EITHER direction — translating a Figma design into SwiftUI (design → code), or pushing SwiftUI views / screens / tokens back into a Figma file (code → design). Triggers on phrases like 'implement this Figma design in SwiftUI', 'build this screen in Swift', 'push this SwiftUI view to Figma', 'mirror my Swift code in a Figma file', or whenever a Figma URL appears alongside `.swift` files / an `.xcodeproj`. Routes to a direction-specific reference doc; loads alongside `figma-use` for the code → design path.