45 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.
Configure authentication and per-project request limits for Google Cloud API Gateway. Secure access to Cloud Run backends, validate quota changes against existing configurations, and investigate HTTP 429 or Service Control Quota errors, including on MCP-enabled gateways.
Find usable copies of web pages when normal fetching fails. The skill tries archives and alternative retrieval routes, checks that results contain actual page content, and preserves source details and snapshot dates for citation.
Call Gemini and OpenMaaS models such as Llama, DeepSeek, and Qwen through Google Cloud Agent Platform. Prepare authentication and SDK code, run prompts, configure connection endpoints, and troubleshoot common request errors.
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.
Diagnose failed OpenAI API requests by separating network problems, authentication errors, exhausted credits, rate limits, and access restrictions. Use concrete error messages to explain the likely cause and direct users to the appropriate next action.
Analyze and design an Attio request governor with separate read and write budgets, query-score awareness, bounded retries, and observable backpressure. Use when an Attio integration receives 429 responses or needs safe concurrency controls. Trigger with "Attio rate limits", "Attio 429", or "throttle Attio requests".
The English summary is being prepared. Showing the original description.
Implement Anthropic Claude API rate limiting, backoff, and quota management. Use when handling 429 errors, optimizing request throughput, or managing RPM/TPM limits across usage tiers. Trigger with phrases like "anthropic rate limit", "claude 429", "anthropic throttling", "claude retry", "anthropic backoff".
The English summary is being prepared. Showing the original description.
Handle Apify API rate limits with proper backoff and request queuing. Use when hitting 429 errors, optimizing API request throughput, or implementing rate-aware client wrappers. Trigger with "apify rate limit", "apify throttling", "apify 429", "apify retry", "apify backoff", "too many requests apify".
The English summary is being prepared. Showing the original description.
Diagnose and fix common Apify Actor and API errors. Use when an Apify run fails, an API call returns 401/403/404/413/429, a proxy connection drops, an Actor build breaks, or a scrape hits an anti-bot block, and you need the cause plus a copy-paste fix. Trigger with "apify error", "fix apify", "actor failed", "apify not working", "debug apify", "apify 429".
The English summary is being prepared. Showing the original description.
Monitor and optimize Algolia request pressure using observed responses and bounded client behavior. Use when requests return 429, queues grow, or search and indexing compete for capacity. Trigger with "Algolia rate limit", "Algolia 429", or "throttle indexing".
The English summary is being prepared. Showing the original description.
Implement service-specific Adobe admission control, Retry-After handling, bounded retries, and spend-aware queues. Use when scaling workloads or handling 429 responses. Trigger with "Adobe rate limit", "Adobe 429", or "Adobe backoff".
The English summary is being prepared. Showing the original description.
AIOps-style CloudBase inspection skill (v3). Use when users need health checks, log diagnosis, alarm interpretation (CPU alert normal?, peak QPS), metrics via queryEnv(action=metrics), or fault playbooks for 429 / AI model 429 / function timeout / function 404 / ACCESS_TOKEN_INVALID / zero invocations. Triggers on 巡检, 诊断, 告警, 峰值 QPS, 限频, 调用量为 0, troubleshooting.
The English summary is being prepared. Showing the original description.
Implement bounded, idempotency-aware API throttling, backoff, and retry handling for 429 and transient 5xx responses.
The English summary is being prepared. Showing the original description.
DeepSeek利用時の失敗切り分け、再試行、quota確認、provider選定を支援する。応答停止、tool call欠落、429などの症状で使う。
The English summary is being prepared. Showing the original description.
Build Python code for Azure Cosmos DB's NoSQL API to create, read, update, delete, and query documents. Covers authentication, containers for storing data, partition keys for distributing records, throughput settings, asynchronous operations, and error handling.
Build Java applications that store, query, update, and delete data in Azure Cosmos DB. Covers synchronous and asynchronous clients, partition keys for distributing data, consistency settings, request usage, and error handling.
Generate client libraries for REST APIs, with authentication, retries, typed request and response models, error classes, and pagination helpers. Language-specific patterns and usage examples show how applications can call API resources.
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.
Generate Python code for Dataverse integrations with error handling, retries, logging, and shared connection management. Include type hints, usage examples, and queries that retrieve only the records and columns needed for the task.
Collect public posts across a blog, newsletter, or feed archive and save clean Markdown pages for each article. The workflow avoids duplicates, supports resumed runs, repairs empty results, and hands articles to a separate enrichment skill.
Build server-side Zoom integrations for meeting scheduling, user management, and recording downloads. This reference guides API endpoint selection, OAuth authentication, request limits, and error diagnosis, with examples for automated workflows and event notifications.
Retrieve Reddit posts and comments through a browser session for topic research. Search within communities, inspect popular or recent posts, and extract titles, scores, and replies, with procedures for handling blocked access and request limits.
Model selection by provider health, not task complexity. Tier 0 (local) handles most tasks. Paid models are break-glass only. Fallbacks activate on 429 or timeout — never on perceived task difficulty.
The English summary is being prepared. Showing the original description.