Skill UI

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 utility enables multi-camera streaming by converting standard camera protocols (RTSP, RTMP, HTTP) into low-latency WebRTC streams using the go2rtc sidecar. It is essential for building real-time surveillance dashboards, live video monitoring systems, or integrating diverse IP cameras into a single web interface.

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 comprehensive guide serves as a quick reference for diagnosing and fixing common Klaviyo API errors and SDK exceptions. It provides detailed root causes and solutions for standard HTTP status codes (400, 401, 403, 429, etc.) and common coding pitfalls. Ideal for developers integrating Klaviyo into their applications.

This comprehensive guide details common errors encountered when integrating with the Linktree API. It covers various HTTP status codes, such as 400 (Invalid URL), 401 (Authentication Failed), and 429 (Rate Limit). The document provides specific causes (e.g., expired keys, malformed data, plan restrictions) and actionable fixes, helping developers build stable and reliable link-in-bio services.

A comprehensive technical guide for diagnosing and resolving common Miro REST API v2 errors. It details specific HTTP status codes (400, 401, 403, 404, 429, etc.), providing common causes, actionable fixes, and best practices for token refreshing, scope management, and achieving stable API integration.

This tool collects comprehensive diagnostic evidence for troubleshooting Miro REST API v2 integration problems. It gathers environment details, performs connectivity tests (DNS, HTTPS), checks rate limits, and aggregates recent application logs into a single, structured bundle. Use this when preparing a detailed support ticket or diagnosing persistent API issues.

This guide provides comprehensive procedures to diagnose and resolve common HTTP errors (401, 403, 429, 500, etc.) encountered when interacting with the Navan API. It details root causes, necessary prerequisites (like `curl` and `jq`), and step-by-step fix procedures for issues such as expired tokens, insufficient permissions, and rate limiting, helping developers ensure stable integration.

This skill implements resilient API interaction patterns for external services. It uses adaptive rate-limiting techniques, including exponential backoff and jitter, to gracefully handle HTTP 429 errors, adapting to undocumented server limits. Furthermore, it provides a dedicated request queue mechanism to manage concurrency, ensuring reliable execution of large-scale, bulk data operations without triggering service throttling.

This guide provides a comprehensive reference for diagnosing and fixing common Notion API errors. It covers critical HTTP statuses and specific error codes (such as 401 Unauthorized, 403 Restricted Resource, 404 Object Not Found, 400 Validation Error, and 429 Rate Limited). Use it when debugging failed Notion integrations, managing permissions, or resolving data structure issues for reliable development.

This skill provides a comprehensive checklist and detailed methodology for detecting HTTP Request Smuggling vulnerabilities. It covers various desynchronization types (CL.TE, TE.CL, TE.TE), including HTTP/2 and modern variants. Use this when penetration testing multi-server architectures, proxies, or load balancers to identify potential security bypasses, unauthorized access, or cache poisoning risks.

This comprehensive guide serves as a complete error decoder for the OneNote Graph API. It analyzes major HTTP status codes (400, 403, 404, 429, 500, 502, 507) and provides root cause analysis, diagnostic steps, and code fixes for common issues. It specifically addresses critical failure modes like deprecated authentication methods and silent 200 OK failures, helping developers debug complex API integrations in production.