Agent skill · software engineering · jeremylongshore
serpapi-local-dev-loop
Build and test SerpAPI integrations locally with sanitized fixtures, injected clients, and an explicit live-recording boundary. Use when developing parsers without repeatedly spending allowance. Trigger with "set up SerpAPI local development".
Why this skill is useful
Adds executable scripts for recording and mocking SerpApi responses, enabling offline testing and cost-effective development.
What it needs
Requires python, vitest 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 Fixture-First Local Development Overview Separate deterministic parsing from live search acquisition so everyday development is fast, private, and allowance-free. Prerequisites A target engine, parameter contract, parser behavior, and repository test framework One approved sanitized response per important schema variant A policy for fixture review, retention, refresh, and sensitive-field removal Tool Discipline Use Read, Glob, and Grep to locate clients, parsers, fixtures, and tests, WebFetch to re-check engine schemas, Write or Edit for adapters and fixtures, and Bash(python3:) or Bash(npm:) for local tests or an explicitly approved recorder. Current Contract SerpAPI response sections vary by engine, query, geography, device, and upstream search layout. The official Python result is a SerpResults mapping; application code should depend on a narrow local adapter rather than a captured response being universal. Authentication Offline tests must not require SERPAPIKEY. Load the key only inside a separately invoked recorder, refuse sentinel or missing values, and never serialize request URLs or metadata fields that reveal it. Instructions 1. Inventory every consumed field and classify it as required, optional, engine-specific, or derived. 2. Create a client interface whose search method can be replaced by a fixture-backed fake. 3. Sanitize fixtures by removing key-bearing URLs, raw HTML links, account identifiers, sensitive queries, and unrelated result content. 4. Add fixtures for normal, empty-success, processing, error, missing optional section, and changed-type cases. 5. Write parser tests against the fixtures and assert normalized application output rather than the entire vendor payload. 6. Put live recording behind a separate command, explicit environment flag, allowance check, and operator approval. 7. When refreshing, review semantic diffs, update the retrieval date and source engine, and rerun all offline tests. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/serpapi-local-dev-loop