Agent skill · marketing growth · jeremylongshore
serpapi-core-workflow-b
Design a multi-engine SerpAPI workflow with explicit parameter maps, result adapters, budgets, and provenance. Use when combining Google, Bing, YouTube, News, Shopping, or Maps. Trigger with "build a SerpAPI multi-engine search".
Why this skill is useful
Provides specific API commands and error handling for multi-engine search queries that the AI wouldn't reliably 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 Multi-Engine Search Workflow Overview Model each engine as a distinct contract, then normalize only the fields needed for a cross-engine product. Prerequisites An explicit engine set, query intent, locale, data-use policy, and per-engine result needs Current engine documentation and sanitized fixtures A total search, latency, and concurrency budget Tool Discipline Use Read, Glob, and Grep to map engine consumers, WebFetch to verify each engine's current parameters and response sections, and Write or Edit for parameter maps, adapters, tests, and redacted receipts. Current Contract Engine contracts are not interchangeable. Google, Bing, Google News, and Google Shopping accept q; YouTube uses searchquery; Google Maps search uses q with type=search and can use ll. Common result sections include organicresults, videoresults, newsresults, shoppingresults, and localresults, but their records have different shapes. Authentication Supply SERPAPIKEY only through the server-side gateway. Preserve engine and search ID for provenance, but strip the key and key-bearing URLs from normalized output. Instructions 1. List the approved engines and define the exact user value each contributes; remove redundant calls. 2. Re-fetch each engine's first-party API page and record its query, locale, pagination, safety, and result-section contract. 3. Build an allowlisted engine map rather than forwarding arbitrary client parameters. 4. Set per-engine timeouts, maximum records, concurrency, and total searches before execution. 5. Execute independently so one engine failure does not erase successful results from another. 6. Normalize to a tagged union retaining engine, searchid, source URL, rank, and engine-specific payload where required. 7. Test normal, empty-success, missing-section, partial-failure, and duplicate-source fixtures; report searches consumed by engine. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/serpapi-core-workflow-b