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 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 enforces rigorous governance and discipline when AI modifies systems, debugs code, or makes root-cause claims. It mandates safety gates (e.g., backup, blast radius check), demands evidence for every diagnosis, and prevents common AI shortcuts like guessing or deflecting. Use this for critical code modifications, complex debugging, and high-stakes deployments to ensure thoroughness and safety.

AWT provides AI coding tools with the ability to perform sophisticated End-to-End (E2E) web testing using a real browser. It accepts declarative YAML scenarios and executes them via Playwright. Key features include visual matching (OpenCV + OCR) instead of relying on fragile DOM selectors, automatic platform detection (React, Vue, etc.), and structured failure diagnosis for improved AI coding workflows.

This skill provides a comprehensive, structured workflow for diagnosing performance bottlenecks in SwiftUI applications. It guides users through a code-first review to detect common issues like invalidation storms, layout thrash, or heavy main-thread work. When code review is insufficient, it provides detailed guidance on collecting runtime evidence using Instruments, enabling precise root cause analysis and targeted remediation strategies.

This skill provides comprehensive observability tooling for Go services, covering the five essential signals: structured logging (slog), Prometheus metrics, OpenTelemetry tracing, continuous profiling, and RUM. Use it for proactive production monitoring, correlating logs with traces, setting up SLOs, and ensuring all new features are fully instrumented for robust diagnosis.

This comprehensive guide serves as a quick reference for diagnosing and fixing common Flexport API v2 errors. It covers standard HTTP status codes (e.g., 401, 403, 422, 429, 5xx), detailing the causes and providing actionable fixes, including cURL examples and validation best practices. Essential for developers integrating supply chain solutions with Flexport.

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 guide for rapid incident response when Algolia search functionality fails. This runbook provides structured procedures for triage, differentiating between infrastructure outages and internal configuration errors (e.g., API keys, indexing failures). It includes severity classification, diagnosis steps, and code examples for immediate remediation, such as key rotation or implementing circuit breakers.

This comprehensive guide serves as a reference for diagnosing and resolving common errors when interacting with the ClickUp API v2. It covers critical HTTP status codes (400, 401, 403, 404, 429, 500) and specific OAuth error codes (ECODEs). Use this resource when debugging failed API requests, troubleshooting authentication issues, or implementing robust error handling logic in your application.

A comprehensive runbook for managing ClickUp API v2 integration failures and outages. It guides users through rapid incident triage, diagnosis based on specific error codes (401, 429, 500), and implementing advanced mitigation techniques like circuit breakers and graceful degradation. This ensures systematic and efficient service recovery.

This bundle is designed to collect comprehensive diagnostics for CoreWeave clusters, including GPU node status, Kubernetes Pod logs, event history, and API connectivity. It aggregates critical cluster-level resource allocation and failure data into a single, actionable archive. Use it when preparing a support ticket to expedite the diagnosis of complex infrastructure issues like stuck pods, OOM errors, or resource bottlenecks.