361 skills · sorted by relevance
Implement controlled retries and request throttling for external APIs. Covers retryable errors, provider-specified waiting times, increasing delays with random variation, retry limits, and checks that repeating a request will not cause unintended duplicate changes.
Build dashboard panels in plain TypeScript with automatic retries for failed requests, error messages, and retry buttons. Save expanded or collapsed state and panel dimensions in localStorage, the browser’s local storage.
Add retries and timeouts to Python service calls, with increasing and randomized waits between attempts. Use examples to distinguish temporary failures from permanent errors, limit retry duration, and record retries in logs.
Monitor selected GitHub Actions checks on an SGLang pull request until they pass on its latest commit. Diagnose failures, push small validated fixes, and retry only failed jobs within defined limits.
Open the hosted context-mode Insight dashboard in your default browser to access analytics for AI-assisted engineering teams, including productive rates per engineer, retry waste, blockers, and views tailored to different roles.
Reproduce model connection failures and interrupted responses in the desktop app using a local fault server and test providers. Check error messages and retry behavior for refused connections, DNS failures, HTTP errors, stalled requests, and cut streams.
Add error handling to n8n workflows with connected error outputs, retries, and failure notifications. Return HTTP status codes that explain what went wrong, distinguish invalid requests from service failures, and keep internal error details out of public responses.
Handle failed tool calls with a clear recovery process. The skill distinguishes temporary problems from input or setup issues, chooses whether to retry or change approach, and records failures so unsuccessful tasks are not silently lost.
Build dashboard panels in plain TypeScript, with regularly refreshed content, loading indicators, item counts, and error messages. Provides a shared panel class and examples for stocks, news, and weather, including retry handling and small trend charts.
Build dashboard panels in vanilla TypeScript with resizing, saved layout state, loading indicators, and retry controls. Examples also show how to wrap existing data-fetching functions with caching and temporary request pauses after repeated failures.
Recover from Pandoc PDF generation failures by checking installed PDF engines and retrying alternatives. The guide matches engines to Unicode text, simple Latin documents, or HTML-based layouts, and includes an automated fallback script.
Break a larger goal into two to six tasks and assign a worker agent to each in sequence. Check results with shell commands, retry failed work, and report completion using the configured default model.
Build failure handling into n8n workflows with separate error paths, retries, alerts, and clear API responses. Use it for webhooks and unattended jobs to make failures visible and return status codes that explain what went wrong.
Build workflows with Vercel's Workflow DevKit that preserve progress and resume after restarts. Structure operations as persistent steps, wait for external events, retry temporary failures, and inspect runs to understand how a process is progressing.
Fix test failures when adding retry/fallback logic causes mock call count mismatches. Use when: (1) Test fails with "Expected: <1>, Actual: <2>" or similar call count errors after adding retry or fallback mechanisms, (2) MissingStubError appears for methods in new fallback code paths, (3) Mockito verify().called(N) assertions fail after behavior changes. Applies to Dart/Flutter with Mockito, but pattern is universal.
The English summary is being prepared. Showing the original description.
Use when running background tasks with Celery - worker and broker configuration (Redis, RabbitMQ), task routing by name vs queue, chains/groups/chords, retry patterns (autoretry_for, retry_backoff), acks_late semantics, failure detection, and monitoring with Flower
The English summary is being prepared. Showing the original description.
Design error handling strategies for TypeScript and Python applications — exception hierarchies, Result/Either types, retry patterns, error boundaries, and structured error logging. Use when designing error handling architecture, choosing between exceptions and Result types, implementing retry logic, or building error recovery flows. Activate on "error handling", "exception hierarchy", "Result type", "retry pattern", "circuit breaker", "error boundary", "Pokemon exception". NOT for debugging specific runtime errors, logging infrastructure setup, or monitoring/alerting configuration.
The English summary is being prepared. Showing the original description.
Design error handling strategies for TypeScript and Python applications — exception hierarchies, Result/Either types, retry patterns, error boundaries, and structured error logging. Use when designing error handling architecture, choosing between exceptions and Result types, implementing retry logic, or building error recovery flows. Activate on "error handling", "exception hierarchy", "Result type", "retry pattern", "circuit breaker", "error boundary", "Pokemon exception". NOT for debugging specific runtime errors, logging infrastructure setup, or monitoring/alerting configuration.
The English summary is being prepared. Showing the original description.
Generates Retry pattern for PHP 8.5. Creates resilience component with exponential backoff, jitter, and configurable retry strategies. Includes unit tests.
The English summary is being prepared. Showing the original description.
Design or review repeating agent workflows with machine-checkable goals, protected boundaries, independent verification, and retry limits. It helps identify endless retries, manipulated checks, and incorrect completion while keeping final judgment with a human.
Design continuous agent workflows with quality checks, evaluations, and recovery controls. Helps choose a loop pattern for the task and define how to pause, audit, narrow scope, and retry when work stalls or fails.
Design APIs and interfaces between modules with clear inputs, outputs, naming, and errors. The skill guides compatible extensions, input validation, and retry handling so callers can use interfaces consistently without accidentally repeating state-changing operations.
Inspect OmniRoute connection restrictions, usage quotas, and retry delays from the command line. Reset stuck providers and adjust failure thresholds, cooldowns, and recovery timing to manage how connections respond to errors.
Coordinate child agents on tasks that must happen in a particular order. Define dependencies, pass results through handoff files, verify the outcome, and recover individual failed tasks while reusing work that has already finished.