Agent skill · software engineering · jeremylongshore
serpapi-prod-checklist
Issue an evidence-backed production-readiness decision for a SerpAPI integration across contract, security, reliability, cost, privacy, and operations. Use when preparing a launch or material change. Trigger with "review SerpAPI production readiness".
Why this skill is useful
Provides specific domain knowledge for SerpApi integrations, including error handling and performance optimization patterns that the AI wouldn't reliably generate on its own.
What it needs
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 Production Readiness Review Overview Fail closed on missing evidence and distinguish deterministic fixture confidence from the separately approved live canary. Prerequisites Immutable release reference, service owner, deployment plan, rollback target, and decision deadline Current SerpAPI documentation and Account API capacity evidence Test, security, privacy, reliability, cost, and operational receipts Tool Discipline Use Read, Glob, and Grep to verify repository and deployment evidence, WebFetch to re-check current vendor contracts, and Write or Edit only for the readiness record and redacted remediation evidence. Current Contract Search behavior varies by engine and optional result sections; 429 can mean throughput or allowance exhaustion; standard records have documented retention while ZeroTrace changes storage and debugging behavior. Production readiness therefore depends on the selected engine, account, data class, and gateway—not a generic SDK smoke test. Authentication Require server-side SERPAPIKEY, an approved secret lifecycle, authenticated gateway callers, and proof that credentials and key-bearing URLs are absent from artifacts, logs, fixtures, and client bundles. Instructions 1. Pin the release SHA and verify dependency, schema, formatting, lint, unit, fixture, integration, security, and deployment gates. 2. Confirm engine-specific parameter allowlists, normalized optional schemas, bounded pagination, timeouts, and retry classifications. 3. Verify secret isolation, caller authorization, abuse controls, redaction, data purpose, cache/log retention, and ZeroTrace decision. 4. Compare forecast demand and concurrency with current Account API searches left and hourly throughput; reserve incident headroom. 5. Prove metrics, alerts, runbooks, support escalation, search-ID correlation, incident response, key rotation, and rollback. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/serpapi-prod-checklist