CodeQL, Semgrep and SARIF static-analysis toolkit from Trail of Bits: taint tracking, fast pattern scans and merged, deduplicated security findings for coding agents.
SerpApi Web SearchSkill
Summary
SerpApi's official skill for structured search: which of 130+ engines to call for citations, local businesses, flights, hotels, shopping or jobs, which response key holds the answer, and the gotchas that silently return the wrong field.
Features
- Intent-to-engine table covering 130+ engines, each with its result key and the fields that matter
- Documents the silent failure modes: place_results vs local_results, summary vs organic_results, nested citation counts
- Lists the engines that do not take `q` (youtube, amazon, ebay, walmart, apple_app_store, flights, hotels)
- Copy-paste --jq extractions for citation counts, business details, live flight prices and shopping comparisons
- Fan-out composition patterns and cross-engine agreement as a confidence check
- Billing notes: only successful searches count, identical queries are cached free for an hour
- Works through the hosted MCP server, the serpapi CLI, an SDK or curl
Install This Skill
Add this skill to your favorite AI agent in a few steps.
Skill Content
Usage Instructions
Learn how to use this skill with different AI agents.
Example Usage
How many citations does the "Attention Is All You Need" paper have right now, and what is the phone number and rating of the highest-rated ramen shop in Shibuya? Cite your sources.
Description
A general web_search tool returns prose about the world. SerpApi returns the world as JSON — but only if you call the right engine with the right parameter and read the right key, and getting any of the three wrong fails quietly. serpapi-web-search is SerpApi's official agent skill for closing that gap.
An engine table, not a tutorial
The core of the skill is a lookup table: intent → engine → result key → the fields worth extracting. General web is google_light → organic_results; academic citations are google_scholar; local businesses are google_maps; flights, hotels, jobs, shopping, finance, video and the Apple App Store each have their own engine and their own response shape. It steers toward _light variants, which are faster, cheaper and return cleaner JSON.
The gotchas are the real content
The section that earns the skill its place is the list of things that go wrong without erroring:
- Google Maps returns
place_resultsfor a named business butlocal_resultsfor a category search — check both keys. - Finance returns
summary, Flights returnsbest_flights, Hotels returnsproperties— none of themorganic_results. - A Scholar citation count lives at
.organic_results[0].inline_links.cited_by.total, not a top-level field. - YouTube takes
search_query, Amazon takesk, eBay takes_nkw, Walmart takesquery, the App Store takesterm— notq. - Flights and Hotels need structured parameters (
departure_id/arrival_id/outbound_date; check-in and check-out dates) rather than a query string. - Shopping prices are third-party reseller feeds; for a specific retailer, use
google_lightwith asite:filter.
It also notes that an empty organic_results on a 200 is not an error — widen the query or switch engine.
Composition and cost
The skill pushes fan-out over sequential querying (finance, news and consensus in parallel), gives copy-paste --jq extractions for common exact-data pulls, and documents progressive refinement and cross-engine agreement as confidence signals. Practical billing notes are included: only successful searches are billed, and an identical query and parameter set is a free cached result for an hour. Error handling is explicit about not retrying a 401 with the same key.
One piece of advice generalises well beyond SerpApi: extract inline — pull {title, link, snippet} into working notes after each search rather than trusting raw results to survive context compaction.
Getting it running
It works through the hosted MCP server at mcp.serpapi.com, the serpapi CLI, an SDK, or plain curl — all of them keyed on SERPAPI_KEY. MIT licensed, maintained by SerpApi.
Related Skills
Microsoft's official Playwright skill — drives a real browser from the command line using accessibility snapshots and element refs, and plans, generates and heals Playwright tests.
Google's official agent skill for writing production Maps Platform code — grounded in freshly fetched docs, with a demo key path that needs no billing account.
Railway's official agent skill: create projects, provision databases and buckets, deploy, manage variables and domains, and read build failures back — from the CLI, API or MCP server.