Agent skill · software engineering · jeremylongshore
serpapi-debug-bundle
Assemble a privacy-safe SerpAPI support bundle with account capacity, search metadata, client context, and reproduction evidence. Use when local diagnosis is insufficient. Trigger with "build a SerpAPI debug bundle".
Why this skill is useful
Adds an executable script for collecting SerpApi diagnostics, including account status and recent searches, which the AI cannot generate from knowledge alone.
What it needs
Requires curl, jq, tar installed locally. Requires serpapi account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
SerpAPI Privacy-Safe Debug Bundle Overview Collect enough evidence to reproduce or escalate an issue while excluding credentials, sensitive queries, and unnecessary result data. Prerequisites Incident window, affected engine, search ID if available, and an incident owner Data classification and approval for any query or result disclosure Current client version, runtime, deployment, and retry configuration Tool Discipline Use Read, Glob, and Grep to trace code and logs, WebFetch to verify status and support contracts, Write or Edit for the redacted bundle, and Bash(python3:) only for approved Account API or archive diagnostics. Current Contract Account API supplies plan usage and hourly throughput without consuming monthly searches. Standard search records expire after the documented retention period; archive access can return 410 after deletion. ZeroTrace searches intentionally have no archive record and are harder to debug. Authentication Load SERPAPIKEY only in the diagnostic process. Remove apikey, key-bearing URLs, account email and ID, sensitive query values, raw HTML, and unrelated results before saving or sharing the bundle. Instructions 1. Freeze the time window and record safe runtime, client, deployment, engine, timeout, retry, and region facts. 2. Extract HTTP status, top-level error, search status, search ID, timing, and parameter names from existing evidence. 3. With approval, query Account API and retain only searches left, current usage, current/hourly usage, and account throughput. 4. Retrieve an archive record only when it exists, remains within retention, and its data classification permits access. 5. Reproduce against a sanitized fixture first; perform one bounded live reproduction only if necessary and approved. 6. Run automated and human redaction checks, create a manifest with hashes, and keep the raw working material in the approved incident boundary. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/serpapi-debug-bundle--9ca72a