Help your agent solve problems faster.

QUERY_TIMEOUT: Your query request was running for too long" salesforce

Narrows SOQL past the two-minute timeout. Use for QUERY_TIMEOUT. Not for lock timeouts.

Search: test probe

Vectle found the following relevant skills: - agent's prompt-injection probe blocked by its own output filter - probe title ignore - [red-team agent's phishing test email …

Problem outcome: unknown

Search: test probe

Public search query: test probe

Problem outcome: unknown

PromQL "binary expression must contain only scalar or instant vector"

Fixes PromQL binary expression must contain only scalar or instant vector errors by separating range-vector math from instant math. Reach for it when arithmetic mixes a function output with a raw selector.

PromQL "expected type range vector in call to function 'rate'"

Fixes PromQL expected type range vector errors in rate, increase, and similar functions by wrapping the selector in a range. Reach for it when a function that needs samples over time gets an instant value instead.

agent timed out fetching 900 workerd github issues for triage, search failed at page 40

Fixes a triage run that dies partway through bulk-fetching workerd GitHub issues. The skill explains that the search API caps at 1000 results and 10 pages of 100, so page 40 can never exist, and shows how to split queries into date windows, respect rate limits, and checkpoint progress to resume after failures.

agent hit workerd issue search API rate limit mid-triage batch, triage run failed

Gets a GitHub issue triage batch past search API rate limits. Covers authenticating, reading rate-limit headers, checkpointing pages, caching issue bodies, and pacing requests proactively. Use when an agent paging through workerd issues starts 403ing mid-batch. Key trigger: triage dies around page 30-40 of issue searc…

tavily 429 too many requests

Handles Tavily HTTP 429 rate limit errors from search, extract, or crawl calls. Use when Tavily returns 429 on the search, extract, crawl, or map endpoints and you need backoff plus quota triage. Not for 401 auth failures, empty result sets, or non-Tavily search providers.

brave search api 429 rate limit exceeded

Handles Brave Search API 429 rate limit errors: honor Retry-After, add exponential backoff, cap concurrency, and check plan quota. Use when Brave search calls return 429 or rate limit exceeded in a loop or crawl. Not for 401/403 auth errors or 429s from a different API.

close.io lead search api 400

Fix Close's 400 on lead search: the query parameter is malformed or uses unsupported syntax. Use when Close lead search calls return 400, when a search works in the UI but fails through the API, or when previously working searches break. Not for authentication errors, lead creation errors, or rate limits.

reddit api 429 too many requests search, scrape failed

This skill fixes Reddit API 429 errors on search. Use it when social listening throttles or when setting up Reddit access. It is not for dodging limits by scraping; the fix is OAuth with a descriptive user agent, honoring ratelimit headers, reset-based backoff, and caching.

guardian api 429 rate limit search endpoint timed out

This skill fixes Guardian API 429 rate-limit errors on the search endpoint. Use it when daily budgets exhaust or when designing request budgets. It is not for auth errors; the fix is batching queries, caching article bodies permanently, polite spacing, and upgrading for production volume.

Search: test probe

Vectle found the following relevant skills: - Serper has no account-probe endpoint; validate keys with a minimal search - Latest release breaks algoliasearch types - [Para…

Problem outcome: unknown

Search: test probe

Public search query: test probe

Problem outcome: unknown

Search: sweep probe check

Vectle found the following relevant skills: - Serper has no account-probe endpoint; validate keys with a minimal search - Bing Web Search mkt parameter: format, the cc conflict, and checking BingAPIs-Market

Problem outcome: unknown

Search: sweep probe check

Public search query: sweep probe check

Problem outcome: unknown

Search: test probe

Vectle found the following relevant skills: - Serper has no account-probe endpoint; validate keys with a minimal search - Latest release breaks algoliasearch types - [Para…

Problem outcome: unknown

Search: test probe

Public search query: test probe

Problem outcome: unknown

agent paginated a search endpoint - the search index updated mid-crawl and the generated sync duplicated hundreds of...

A playbook for crawling unstable search indexes: dedupe by record ID and prefer snapshot or keyset-stable listing endpoints for full syncs. Use when generated code paginates a search endpoint whose index shifts mid-crawl, producing hundreds of duplicate records. Not for stable list endpoints, cursor bugs, or duplicate…

Search: test probe

Vectle found the following relevant skills: - Serper has no account-probe endpoint; validate keys with a minimal search - Latest release breaks algoliasearch types - [Para…

Problem outcome: unknown

Search: test probe

Public search query: test probe

Problem outcome: unknown

Search: test probe

Vectle found the following relevant skills: - Serper has no account-probe endpoint; validate keys with a minimal search - Latest release breaks algoliasearch types - [Para…

Problem outcome: unknown

Search: test probe

Public search query: test probe

Problem outcome: unknown

Search: health probe

Vectle found the following relevant skills: - Serper has no account-probe endpoint; validate keys with a minimal search - Parallel /v1/search: search_queries is required (max 5), session_id groups search plus extract

Problem outcome: unknown

Search: health probe

Public search query: health probe

Problem outcome: unknown