Agent skill · product strategy · jeremylongshore
serpapi-reference-architecture
Design a governed SerpAPI search service with engine adapters, policy enforcement, caching, capacity management, observability, and privacy boundaries. Use when conducting architecture review. Trigger with "design a SerpAPI architecture".
Why this skill is useful
Provides a detailed architecture and project structure for implementing SerpApi in search applications, which includes specific caching and monitoring patterns not commonly known.
What it needs
Requires postgresql, redis 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 Governed Reference Architecture Overview Place SerpAPI behind an application boundary that controls identity, parameters, data, allowance, and failure behavior for every engine. Prerequisites Business use cases, caller identities, engines, data classes, freshness and latency objectives Volume model, account contract, downstream systems, and regulatory/retention requirements Security, product, finance, reliability, and platform owners Tool Discipline Use Read, Glob, and Grep to ground the design in repository and infrastructure topology, WebFetch to verify current vendor contracts, and Write or Edit for diagrams, decision records, interfaces, threat models, and rollout evidence. Current Contract SerpAPI has engine-specific requests and variable response sections, private-key authentication, account-level search and throughput capacity, optional async/archive processing, one-hour exact-query server caching, and Enterprise ZeroTrace. Async depends on archive retrieval, while ZeroTrace intentionally prevents stored search records. Authentication Keep SERPAPIKEY in a server-side secret boundary. Authenticate application callers independently and enforce use-case authorization before the gateway maps input to allowlisted vendor parameters. Instructions 1. Map callers, trust zones, engines, queries, results, stores, consumers, data classes, and systems of record. 2. Define an authenticated gateway with use-case-specific input schemas, engine adapters, output projections, and policy enforcement. 3. Add an application cache with credential-free semantic keys, freshness TTLs, encryption and retention appropriate to the data class. 4. Coordinate admission, concurrency, pagination, retries, and background work against live Account API capacity. 5. Separate synchronous calls from async/archive jobs and prove that any ZeroTrace path does not rely on archive replay. 6. Emit safe metrics and search-ID correlation without query, result, key-bearing URL, or account leakage. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/serpapi-reference-architecture