Monday.com

**Judgement:** This skill is a strong, focused integration for Monday.com. It is well-suited when you explicitly need to interact with Monday.com boards, items, and related objects through GraphQL, and are comfortable managing an external MATON API key and OAuth connections. **What it does well:** - Exposes nearly the full Monday.com GraphQL surface area via a single POST endpoint. - Handles OAuth via Maton so you don’t need to store Monday.com tokens yourself. - Provides clear examples for common operations (creating boards/items, updating columns, pagination). **Key risks / limitations:** - Hard dependency on two external services: Maton’s gateway and Monday.com’s API. Outages, rate limits, or breaking changes in either will affect reliability. - Requires a valid MATON API key and a configured Monday.com OAuth connection; misconfiguration is a common failure mode. - All operations are raw GraphQL strings; complex workflows may be harder to maintain compared to a higher-level client SDK. - Access scope and data exposure are governed by Monday.com OAuth; incorrect scopes or key handling can lead to security or access issues. **Recommended scenarios:** - Automating Monday.com task/board management (create/update/delete boards, groups, items, columns). - Integrating Monday.com with other tools or data pipelines where you can safely store and inject the MATON API key. - Building internal dashboards or reporting tools that read from Monday.com using custom GraphQL queries. **Use with caution when:** - You cannot securely manage environment variables/API keys. - You need offline robustness or low-latency guarantees; you are dependent on external gateway and Monday.com availability. - The user’s needs involve other third-party apps beyond Monday.com—in that case, the separate `api-gateway` skill is more appropriate.