What problem does it solve? Exposing new Operately capabilities to ChatGPT or Claude MCP clients requires coordinating API handlers, MCP wrappers, OAuth scopes, and catalog tests across many files, and mistakes like duplicate tools or missing catalog entries fail CI. ## Core Features & Use Cases - API-first workflow: Enforces checking for existing MCP tools and API endpoints before writing code, and requires adding the API handler before the MCP wrapper. - Implementation contracts: Defines module structure, definition/0 fields, OAuth scopes (mcp:read/mcp:write), safety classifications, sort_order bands, and ID decoding conventions. - Two-layer testing: Prescribes exhaustive API tests with TurboCase plus MCP adaptation tests with ToolConnHelper, and mandatory @expected_tool_names catalog updates. - Use Case: When asked to expose a new Operately capability (e.g., listing task statuses) to MCP clients, follow the skill to add the API endpoint, register it, write the wrapper, and update the catalog test. ## Quick Start Ask the agent to add a new MCP tool for an Operately capability, and it will check for existing tools and API endpoints before generating the wrapper, tests, and catalog entry.