Skill UI

A comprehensive guide for generating highly detailed and structured embodiment descriptions for patent specifications. It outlines the necessary workflow for describing how an invention is made and used (method, system, apparatus), ensuring the patent meets enablement requirements while strictly differentiating technical descriptions from empirical experimental results.

This comprehensive runbook provides structured procedures for diagnosing and responding to critical failures when integrating with the Grammarly API. It covers various incident types, including full API outages, OAuth token expiration, rate limit storms, and suggestion quality degradation. The guide includes severity classification, diagnostic `curl` commands, detailed playbooks, and post-incident documentation steps to ensure service resilience and minimal downtime.

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 tool enforces four rigorous coding principles, inspired by Andrej Karpathy's insights on LLM pitfalls. It guides developers to surface assumptions, prioritize simplicity, make surgical changes, and define verifiable goals. Use it when reviewing code, checking diffs, or before committing to ensure high code quality and prevent over-engineering.

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 guide provides a comprehensive reference for diagnosing and resolving common errors encountered when integrating with the Lucidchart API. It covers critical issues such as OAuth token expiration (401), insufficient scopes (403), document locking conflicts (409), and shape validation errors (422). Developers can use this resource to implement robust error handling, manage rate limits, and ensure stable programmatic diagram creation.

This workflow manages the collaboration and lifecycle of diagrams created in Lucidchart. Users can invite specific collaborators with tailored, role-based permissions (e.g., editor, viewer, commenter). It allows for setting granular access controls, such as restricting downloads, limiting link sharing, or setting document expiry dates. Furthermore, it enables tracking revision history and managing comment threads, ensuring secure and organized team knowledge sharing.

A comprehensive guide for rapid incident response and troubleshooting of Miro API v2 integration failures. It covers defining severity levels, quick triage steps, detailed error handling for 4xx/5xx status codes (e.g., token expiration, rate limiting), mitigation strategies, and postmortem evidence collection.

This guide provides comprehensive procedures to diagnose and resolve common HTTP errors (401, 403, 429, 500, etc.) encountered when interacting with the Navan API. It details root causes, necessary prerequisites (like `curl` and `jq`), and step-by-step fix procedures for issues such as expired tokens, insufficient permissions, and rate limiting, helping developers ensure stable integration.

A comprehensive runbook for rapidly responding to Notion API incidents. It provides structured triage flows, automated health checks, and a decision tree to classify failures (Notion-side vs. integration-side). Use it for immediate diagnosis of outages, error mitigation (e.g., rate limits, token expiry), and post-incident reviews.

This skill provides robust implementation patterns for integrating with the Podium API. It covers core business functionalities such as messaging, review management, and payment processing. By utilizing REST API calls and OAuth2 authentication, developers can establish secure, scalable connections, along with detailed error handling for common issues like expired tokens or rate limiting.

Provides patterns for integrating with the Podium REST API. It covers authentication using OAuth2, performing core functions like fetching location data, and implementing robust error handling (e.g., rate limiting, token expiration) to ensure stable business messaging, review management, and payment processing workflows.