Agent skill · software engineering · jeremylongshore
serpapi-deploy-integration
Deploy a server-side SerpAPI gateway with secret isolation, input policy, capacity controls, canary evidence, and rollback. Use when promoting a search integration. Trigger with "deploy a SerpAPI gateway".
Why this skill is useful
Provides specific integration patterns and deployment commands for SerpApi in serverless environments that the AI wouldn't reliably generate on its own.
What it needs
Requires flask, gcloud, serpapi, vercel 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 Gateway Deployment Overview Promote a narrow backend gateway through preview, canary, reconciliation, and rollback without exposing the SerpAPI key or an open search proxy. Prerequisites A fixture-tested gateway, deployment owner, route, caller identity, and rollback target Approved secret manager, data classification, SLO, capacity budget, and observability Platform-specific release and health-check conventions Tool Discipline Use Read, Glob, and Grep to inspect application and infrastructure changes, WebFetch to verify current SerpAPI contracts, and Write or Edit for deployment configuration, policies, probes, tests, and redacted receipts. Current Contract SerpAPI search calls require a private key and engine-specific parameters. Account capacity is discoverable through Account API. Public browser clients should call an authenticated application backend rather than SerpAPI directly. Authentication Inject SERPAPIKEY from the target platform's server-side secret store. Authenticate gateway callers separately, validate their authorization to the requested use case, and never return vendor account or credential data. Instructions 1. Review the deploy diff, dependency lock, secret references, route exposure, caller authentication, input allowlist, output projection, and data retention. 2. Define readiness without a billable search; expose only internal health and configuration status, not Account API details. 3. Set finite client and request timeouts, concurrency/admission limits, cache policy, retry budget, and maximum pagination. 4. Deploy to an isolated preview with no production key and run fixture, authorization, abuse, redaction, and rollback tests. 5. Present the production mutation, live-search budget, monitoring, owner, and exact rollback command for approval. 6. Deploy a small canary, execute one approved harmless search, and reconcile status, search ID, latency, errors, and capacity. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/serpapi-deploy-integration