Publish Api

**Quick judgement**: This is a strong, broadly useful API-integration reference skill. It’s well-suited when a user asks how to call a known third-party API from their own code and needs concrete endpoints, auth patterns, pagination/rate-limit handling, and examples. **Strengths** - Large catalog (~147 services) spanning AI, payments, comms, productivity, dev tooling, etc. - Organized by category with indices and per-API sections, plus separate pattern docs (auth, pagination, webhooks, resilience). - Emphasizes best practices and common mistakes, which is valuable for preventing fragile or insecure integrations. **Key risks / limitations** - Third-party APIs change frequently; some endpoints, parameters, or limits may be outdated or incomplete, so responses should be treated as a starting point and cross-checked against official docs for critical work. - It’s documentation-only: it cannot validate live credentials, test calls, or confirm actual provider behavior. - It can help users interact with powerful APIs (e.g., payments, data access); secure key management and permission scoping remain entirely the user’s responsibility. **Recommended scenarios** - User: *“How do I integrate with X API?”* for a covered service, especially when they need example requests, auth headers, or pagination patterns. - User debugging integration issues where incorrect auth, missing headers, or pagination/rate limits are suspected. - Designing a robust integration (idempotency, retries, webhooks) where pattern docs (auth, pagination, resilience, webhooks) can be applied. - Teaching or guiding less-experienced developers through standard REST integration practices using real-world APIs as examples.