Skill UI

This guide provides a quick reference for diagnosing and fixing the top common errors encountered in ClickHouse, including syntax errors, memory limit issues, write permission failures, and data type mismatches. It offers specific error codes, root causes, and actionable SQL solutions for smooth database operation and complex analytics.

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 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.

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.

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 guide provides comprehensive solutions for common API errors encountered when integrating with Persona for identity verification (KYC). It covers critical issues including 401 unauthorized keys, 422 invalid templates, webhook signature mismatches, rate limit handling (429), and state management conflicts. Use this resource when debugging or optimizing automated identity validation workflows.

This guide provides a comprehensive reference for common errors encountered when using the SerpApi. It covers issues like invalid API keys, exhausted search credits, missing parameters, and CAPTCHA blocks. Use this when your automated search results are incorrect, empty, or return unexpected status codes, allowing you to quickly diagnose the root cause and implement fixes.

This comprehensive guide serves as a decision flowchart for developers using Claude Code. It details when to use specific slash commands (/plan, /compact, /loop), select specialized agents (planner, code-reviewer, build-error-resolver), or invoke workflow skills (e2e-testing, tdd-workflow). It helps users select the optimal tool combination for complex tasks across the entire software development lifecycle, including feature planning, bug fixing, testing, and architectural design.

This skill automates the debugging and fixing of failing Continuous Integration (CI) checks on GitHub PRs. It uses the GitHub CLI (gh) to locate failures, fetch detailed logs from GitHub Actions, summarize the failure context, and propose a structured fix plan. After user approval, it can implement the necessary code changes and verify the fix, streamlining the development cycle.

A systematic, non-mutating investigation designed for complex software failures, including bugs, regressions, crashes, and flaky behavior. This skill launches four specialized, read-only sub-agents in parallel to perform deep root-cause analysis, trace code paths, pinpoint the smallest failing seam, and predict the quickest path to confirming or fixing the issue. It is designed purely for diagnosis and hypothesis generation.