Agent skill · marketing growth · jeremylongshore
serpapi-hello-world
Run a controlled first Google search through an official SerpAPI client and validate metadata before consuming result sections. Use when proving a new integration end to end. Trigger with "run a SerpAPI smoke test".
Why this skill is useful
Provides specific commands and structured examples for using the SerpApi with various search engines that the AI wouldn't reliably generate on its own.
What it needs
Requires serpapi 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 Controlled First Search Overview Prove authentication, transport, search status, and schema handling with one bounded query and a redacted receipt. Prerequisites An official SerpAPI client already installed SERPAPIKEY loaded from an approved server-side secret store A harmless query, expected locale, allowance owner, and live-call approval Tool Discipline Use Read, Glob, and Grep to inspect local setup, WebFetch to verify current Google Search parameters, Write or Edit for the smoke-test code and redacted receipt, and Bash(python3:) or Bash(npm:) only to run the approved check. Current Contract Google Search uses engine=google and query parameter q. JSON responses expose searchmetadata.status, a search ID, search parameters, and optional result sections. A successful search may legitimately contain no organic results. Authentication Pass the private key from SERPAPIKEY through the official client. Never interpolate it into source, logs, exceptions, fixtures, screenshots, or receipts. Instructions 1. Confirm the query is non-sensitive and set explicit location, hl, and gl values when geographic reproducibility matters. 2. Check Account API for available searches and hourly throughput without spending allowance. 3. Preview one request with engine=google, q, and the minimum necessary parameters. 4. After approval, execute exactly one search with a finite client timeout. 5. Require searchmetadata.status == "Success"; treat missing result sections as optional schema branches. 6. Extract only the fields required by the caller and preserve the search ID for support correlation. 7. Record client version, normalized parameters, status, elapsed time, result counts, and search ID with the key and sensitive query data redacted. Output Return the approved request shape, search status, result-section counts, search ID, redacted receipt location, and any schema assumptions that need fixtures. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/serpapi-hello-world--2f44cb