Agent skill · data analytics · jeremylongshore
serpapi-core-workflow-a
Build a reproducible Google Search workflow that validates parameters, optional result sections, and bounded pagination. Use when implementing search, SEO monitoring, or evidence collection. Trigger with "build a SerpAPI Google workflow".
Why this skill is useful
Adds executable scripts for extracting structured data from Google Search using SerpApi, which the AI wouldn't generate on its own.
What it needs
Requires serpapi 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 Google Search Workflow Overview Turn a search question into a bounded, reproducible Google Search request and normalize only the result sections the application actually needs. Prerequisites A business question, permitted query class, geography, language, device, and freshness target An authenticated official client behind a server-side gateway A search/page budget and fixtures for expected optional sections Tool Discipline Use Read, Glob, and Grep to inspect call sites and result consumers, WebFetch to verify current Google parameters and schemas, and Write or Edit for request builders, normalizers, tests, and redacted receipts. Current Contract Google Search uses engine=google and q. Locale and device inputs include location, hl, gl, and device; pagination commonly uses start. JSON sections such as organicresults, answerbox, knowledgegraph, relatedquestions, and local results are query-dependent and optional. Authentication The server-side gateway supplies SERPAPIKEY. Exclude the key and key-bearing URLs from application output, cache keys, logs, telemetry, fixtures, and error reports. Instructions 1. Convert the business question into a minimal query and document permitted use, location, language, device, safe-search setting, freshness, and requested fields. 2. Validate parameters against the current Google Search API rather than copying options from another engine. 3. Estimate the maximum searches, check the account budget, and present the live execution boundary. 4. Execute the first page and require a terminal Success or Error status before parsing sections. 5. Normalize each required section independently and retain provenance fields such as position, source link, and search ID. 6. Follow serpapipagination.next or a documented start offset only while results continue and the page budget remains. 7. Reconcile counts, deduplicate stable links, test empty and missing-section fixtures, and store a redacted receipt. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/serpapi-core-workflow-a