Skill UI

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.

A comprehensive index of 46 production-grade test automation skills, covering E2E, unit, mobile, BDD, and cloud testing across 15+ languages. This skill equips AI coding assistants to act as senior QA architects, generating structured, real-world test code for major frameworks like Playwright, Selenium, Cypress, and Jest. It supports project setup, CI/CD integration, and cross-platform debugging.

A comprehensive guide to ensuring robust state management for LangGraph agents. This skill addresses common checkpointing pitfalls (like missing thread_id or non-JSON serializable state) and details best practices for implementing reliable state persistence using MemorySaver or PostgresSaver. It covers thread discipline, schema migration, and time-travel debugging for production-ready 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.

This comprehensive debug bundle collects all necessary diagnostic evidence from Lucidchart's API integrations. It systematically checks document access, data linking integrity, shape rendering, and export status by capturing API responses, page metadata, and rate limit information. It is essential for support engineers diagnosing complex integration failures without needing direct account access.

This utility provides a local, mock development loop for integrating and testing the Lucidchart diagramming API. It simulates document, page, and shape data, allowing developers to build and validate diagram automation tools (CRUD operations) without needing a live Lucid account. This enables fast iteration and robust debugging in a controlled sandbox environment.

Provides comprehensive observability for Miro REST API v2 integrations. It captures critical metrics using Prometheus (request rates, latency, error tracking) and OpenTelemetry traces for end-to-end request flow visibility. Includes structured logging for detailed debugging and robust rate limit management, ensuring your applications are highly reliable and maintainable.

This comprehensive guide establishes a structured local development environment for integrating with the Navan API. Since Navan does not provide a sandbox, this workflow is crucial for minimizing calls to the production API. It implements token caching to persist access tokens, detailed request logging for debugging, and mock fixtures to allow for reliable, safe offline testing during the development cycle.

Provides advanced debugging techniques for Notion API issues that standard troubleshooting cannot resolve. It covers response ID inspection, tracing complex permission chains, detecting property type mismatches, managing pagination edge cases, and resolving block nesting limits across Notion databases and pages. Essential for robust integration development.

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 details the most common and tricky mistakes developers encounter when building integrations with the Notion API. It covers critical pitfalls such as incorrect page ID formats, handling rich text arrays, ensuring proper page sharing permissions, and correctly retrieving nested block content. Essential reading for debugging and optimizing Notion-related code.