Agent skill · software engineering · jeremylongshore
serpapi-ci-integration
Gate SerpAPI code with sanitized fixtures and isolate optional live searches behind trusted CI environments and allowance controls. Use when adding integration tests to automation. Trigger with "add SerpAPI CI".
Why this skill is useful
Adds a complete CI/CD setup with fixture-based testing scripts specifically for SerpApi, which the AI wouldn't generate on its own.
What it needs
Requires pytest, python 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 CI Integration Overview Make parsing and policy gates deterministic on every change while restricting live search to a separately approved, trusted workflow. Prerequisites Sanitized fixtures and an injected client boundary Repository CI conventions, required checks, and fork threat model A protected environment, allowance budget, and owner for any live smoke test Tool Discipline Use Read, Glob, and Grep to inspect tests and workflows, WebFetch to verify current client behavior, Write or Edit for fixtures, tests, and CI, and Bash(gh:) only to inspect or operate the approved GitHub workflow. Current Contract Offline fixture tests require no SerpAPI credential or search allowance. A live search is external, variable, and potentially billable; untrusted pull-request code must not receive SERPAPIKEY, including through unsafe workflow-trigger patterns. Authentication Store SERPAPIKEY only in a protected CI environment. Never expose it to fork PRs, logs, artifacts, command traces, caches, or fixture updates. Give live jobs read-only repository permissions unless a documented need proves otherwise. Instructions 1. Inventory CI triggers, fork behavior, permissions, secret scopes, environments, artifacts, and dependency installation. 2. Put parser, adapter, error, pagination, redaction, and policy tests on sanitized fixtures with network disabled. 3. Run fixture tests on every pull request and push using pinned actions and locked dependencies. 4. Define an optional live smoke job on a manual, scheduled, or trusted-main trigger; bind it to a protected environment and explicit concurrency/search budget. 5. Check account capacity first, execute one harmless request, and emit only status, search ID, and safe counts. 6. Make live failure diagnostically visible but decide deliberately whether it is required or advisory; never let provider variance weaken deterministic gates. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/serpapi-ci-integration