Skill UI

This skill provides comprehensive guidance for diagnosing and resolving common Guidewire Cloud API errors. It covers typical HTTP status codes (400, 401, 403, 404, 409, 422) and common Gosu exceptions like ClassNotFoundException, NPE, and ValidationException. Use this resource when integrating with Guidewire systems or troubleshooting failed API calls.

This runbook provides a structured guide for responding to critical Guidewire production incidents. It covers the entire lifecycle of incident management, including initial triage (checking monitoring, API errors, and batch logs), diagnosing performance degradation (JVM metrics and query performance), implementing mitigation steps, and proper escalation procedures to Guidewire Support.

A comprehensive guide for implementing standardized, robust error handling in modern APIs. It utilizes RFC 7807 Problem Details, centralized middleware, and typed error classes to convert diverse failure types (validation, auth, database, upstream service) into consistent, machine-readable responses with correct HTTP status codes. Essential for building production-grade, resilient backends.

This comprehensive guide serves as a quick reference for diagnosing and resolving common Ideogram API errors and exceptions. It covers critical issues such as authentication failures (401), rate limiting (429), safety check failures (422), and incorrect parameter formats (400). Use this resource when debugging failed image generation requests or integrating Ideogram functionality into an application.

This skill provides a comprehensive diagnostic reference for common errors and exceptions encountered with the Instantly.ai API v2. It covers critical areas including HTTP status codes (400, 401, 429, 500), campaign lifecycle issues (e.g., stuck in draft), account health checks, lead duplication handling, and implementing rate limit backoff. Use this when debugging failed API requests or troubleshooting complex campaign, account, or lead management issues.

This skill provides robust patterns for handling API rate limits (e.g., 429 errors) when building high-throughput integrations. It demonstrates best practices including exponential backoff with jitter, request queuing, concurrency control, and specific endpoint throttling mechanisms, ensuring reliable service connectivity.

This comprehensive guide addresses common technical and business logic errors encountered when integrating with the Juicebox API. It covers HTTP status codes (e.g., 401, 403, 429), including authentication failures, quota exhaustion, rate limiting, data validation issues, and analysis timeouts. The resource provides detailed causes, specific fixes, and best practices for building reliable and robust integrations into recruiting and research workflows.

This guide provides comprehensive strategies and TypeScript implementations for managing rate limits when interacting with the Juicebox AI API. It includes a token bucket rate limiter class, a robust retry mechanism for handling 429 errors and transient failures, and utilities for efficient batch processing of large datasets. Use this when building high-throughput applications that rely on Juicebox data analysis or enrichment endpoints.

This guide provides a comprehensive reference for diagnosing and resolving common errors encountered when interacting with the Kling AI API. It covers various HTTP status codes (e.g., 400, 401, 429), task-level failures (e.g., content policy violations, low image quality), proper JWT token management, and implementing rate limit handling with exponential backoff. Use this resource when troubleshooting failed video generation or API integration issues.

This skill provides comprehensive strategies for managing API rate limits, focusing on high-volume and mission-critical workflows. It implements exponential backoff with jitter, task concurrency limiting using `asyncio`, and request queue patterns. Designed to detect and gracefully handle `429 Too Many Requests` errors, ensuring reliable and stable execution even under severe throttling conditions.

A comprehensive diagnostic guide for resolving the 10 most common Langfuse integration errors. This resource covers root causes, specific error codes (like 401 Unauthorized or connection timeouts), and provides tested solutions for debugging missing traces, authentication failures, and general LLM observability issues.

A comprehensive guide for diagnosing and fixing common errors when interacting with the Linear API or SDK. Covers critical topics such as authentication failures (401), rate limiting (429), excessive query complexity, and handling null references. Essential for building robust and reliable software integrations.