Skill UI

A comprehensive toolkit for debugging complex Adobe API issues that resist standard troubleshooting. Covers advanced techniques such as IMS token introspection, Firefly async job failure analysis, mapping PDF Services error codes, and deep network-layer diagnostics (DNS, TLS). Essential for resolving difficult, production-level integration bugs.

A comprehensive diagnostic utility designed to collect all necessary evidence when troubleshooting Attio API connectivity issues or preparing a support ticket. It checks API authentication, object schema definitions, rate limit status, and general endpoint health using shell scripting and cURL.

This comprehensive guide serves as a reference for diagnosing and resolving common errors when interacting with the ClickUp API v2. It covers critical HTTP status codes (400, 401, 403, 404, 429, 500) and specific OAuth error codes (ECODEs). Use this resource when debugging failed API requests, troubleshooting authentication issues, or implementing robust error handling logic in your application.

A comprehensive diagnostic guide for common ElevenLabs API errors, organized by HTTP status code. It provides detailed causes, fixes, and troubleshooting steps for issues such as invalid API keys (401), quota exhaustion, exceeding character limits (400), and rate limiting (429). Essential for developers debugging TTS, voice cloning, or streaming requests.

This guide provides advanced, deep debugging techniques for complex Figma REST API issues that resist standard error handling. It covers full network tracing (cURL), validating unexpected response shapes (TypeScript), measuring rate limits, and safely chunking large files. Use this when standard troubleshooting fails, or detailed evidence is required for support escalation.

This skill provides a comprehensive observability stack for Flexport logistics integrations. It sets up Prometheus metrics for API health tracking, uses structured logging (pino) for debugging, implements OpenTelemetry tracing for latency analysis, and defines actionable Grafana dashboards and alert rules. This ensures reliable, performant, and fully monitored logistics operations.

A comprehensive guide designed to diagnose and resolve common technical errors encountered when integrating with the Glean enterprise search API. It covers critical areas such as token type mismatches, indexing pipeline failures, permission restrictions, and rate limiting, providing actionable fixes for maintaining seamless search functionality.

This skill provides comprehensive guidance and solutions for diagnosing and fixing common technical errors and exceptions encountered when integrating with the Grammarly API. It covers specific HTTP error codes (400, 401, 413, 429), addressing issues such as invalid tokens, payload size limits, rate limit exhaustion, and text formatting requirements. Use it when debugging failed API requests or troubleshooting complex integration workflows.

This bundle collects comprehensive diagnostic evidence for troubleshooting Grammarly API integration issues. It captures API connectivity status, text check responses, authentication details, and rate limit headers. Use this when encountering persistent errors, preparing detailed support tickets, or performing automated health checks on Grammarly services.

This comprehensive skill diagnoses and provides fixes for common errors and exceptions encountered when integrating with the Hootsuite API. It covers issues such as 401 Unauthorized (expired tokens), 429 Rate Limits, and OAuth flow problems. Users can utilize advanced debugging techniques and specific `curl` commands to ensure robust social media automation and integration.

A comprehensive guide for diagnosing and fixing common HubSpot API errors (e.g., 401, 403, 429, 400). It provides real error response bodies, root cause analysis, and actionable code solutions for debugging failed API requests, improving integration reliability, and managing complex CRM interactions.

This structured skill guides users through root-cause-first debugging when an implementer is blocked, verification fails, or repeated attempts at fixing do not converge. It mandates a systematic approach combining local evidence inspection, runtime analysis, and external documentation research to accurately classify the failure's true source (e.g., missing dependency, spec conflict). It prevents speculative patching and generates a clear, actionable fix plan.