Skill UI

A comprehensive guide to troubleshooting the most common Algolia API errors, including 400, 403, 404, and 429. This document details the root causes and provides step-by-step fixes for issues related to invalid API keys, rate limits, missing indexes, and data structure validation, ensuring reliable search functionality.

A comprehensive reference guide for diagnosing and fixing common Anthropic Claude API errors, categorized by HTTP status codes (400, 429, 500, etc.). Includes specific error JSON patterns, root causes (e.g., role alternation, rate limits), suggested fixes, and code examples in Bash and Python for effective troubleshooting.

This guide provides a comprehensive reference for diagnosing and resolving common integration errors encountered when using the AppFolio Stack API. It covers specific HTTP error codes (e.g., 401, 404, 409, 422, 429), detailing the root cause, recommended fixes, and best practices for robust error handling, such as implementing backoff strategies and re-authentication.

This advanced tutor covers a wide range of university-level STEM subjects, including Computer Science, AI/ML, Physics, Chemistry, and Engineering. It moves beyond rote memorization, focusing instead on developing deep conceptual understanding and transferable problem-solving skills. The methodology emphasizes Socratic questioning, first principles reasoning, and diagnosing the root cause of knowledge gaps across disciplines.

A comprehensive guide for diagnosing and resolving common technical errors across various Adobe APIs, including Firefly, PDF Services, and Photoshop. It provides detailed root causes and actionable fixes for common HTTP status codes (e.g., 401, 403, 429), helping developers troubleshoot complex integration issues and authentication failures.

A comprehensive debug bundle designed to collect diagnostic evidence from AppFolio property management API integrations. It captures essential data points including API connectivity status for properties, tenants, and work orders; authentication status using client credentials; recent integration error logs; and environment metadata. This allows support engineers to perform root cause analysis and diagnose issues like connectivity failures or authentication rejections without needing live environment access.

A comprehensive runbook providing structured guidance for rapid incident response when encountering failures with the Canva Connect API integration. It guides users through initial triage (checking status, error rates), outlines immediate mitigation strategies for common API errors (401, 429, 5xx), and covers standardized communication templates and detailed post-incident procedures, including log collection and root cause analysis.

This comprehensive guide serves as a quick reference for diagnosing and resolving common Cohere API v2 errors and exceptions. It covers specific error codes (400, 429, 401, etc.), details the root causes, and provides actionable code fixes for various tasks, including Chat, Embed, and Rerank. Use this when debugging failed Cohere requests or encountering rate limits.

A multi-phase workflow designed to guide users through complex problem analysis and solution design. Instead of providing immediate answers, it systematically enforces deep thinking by reviewing the problem's validity, assessing information gaps, performing root cause analysis, and iterating through solution vetting (self-check and final review). Ideal for complex technical troubleshooting, decision-making, or theoretical discussions requiring rigorous methodology.

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.

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.