Skill UI

This utility collects comprehensive diagnostic evidence for troubleshooting Flexport API integration issues. It automatically captures API connectivity tests, authentication status, recent error logs, and platform status, packaging them into a secure, redacted bundle ready for support tickets. Ideal for developers encountering persistent API failures.

This skill provides a comprehensive observability stack for Flexport logistics integrations. It sets up Prometheus metrics for API health tracking, uses structured logging (pino) for debugging, implements OpenTelemetry tracing for latency analysis, and defines actionable Grafana dashboards and alert rules. This ensures reliable, performant, and fully monitored logistics operations.

Collects comprehensive diagnostic information for Fondo support tickets. This bundle checks API connectivity status, filing compliance, integration health (bank/payroll), and detects reconciliation discrepancies. Ideal for troubleshooting complex financial sync errors, tax filing issues, and general platform failures.

A utility designed to collect comprehensive diagnostic evidence for Framer development issues. It automatically gathers runtime environment details, installed package versions, API connectivity status, and necessary configuration files. Use this when preparing detailed support tickets or troubleshooting persistent bugs related to Framer plugins or server-side APIs.

Manages the complete lifecycle of GitHub issues using a structured, label-based state machine. This skill assists maintainers in triaging incoming reports, determining if an issue is a bug or enhancement, and moving it through defined states (e.g., needs info, ready for agent, wontfix). It ensures systematic workflow management for development projects.

A comprehensive guide designed to diagnose and resolve common technical errors encountered when integrating with the Glean enterprise search API. It covers critical areas such as token type mismatches, indexing pipeline failures, permission restrictions, and rate limiting, providing actionable fixes for maintaining seamless search functionality.

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.

This bundle collects comprehensive diagnostic evidence for troubleshooting Grammarly API integration issues. It captures API connectivity status, text check responses, authentication details, and rate limit headers. Use this when encountering persistent errors, preparing detailed support tickets, or performing automated health checks on Grammarly services.

This comprehensive skill diagnoses and provides fixes for common errors and exceptions encountered when integrating with the Hootsuite API. It covers issues such as 401 Unauthorized (expired tokens), 429 Rate Limits, and OAuth flow problems. Users can utilize advanced debugging techniques and specific `curl` commands to ensure robust social media automation and integration.

This bundle collects comprehensive diagnostic evidence for Hootsuite operations. It gathers API connectivity status, social profile health, scheduled post status, and OAuth token validity into a single, portable archive. Use it when troubleshooting persistent issues like failed scheduling, authentication errors, or disconnected social accounts.

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.