agentleFS
mike-scrapingbotmike-scrapingbot/scrapingbot/skills/google-search/SKILL.md

google-search

Skill0 starsChanged 40 days agoMITView on GitHub

Get Google results as JSON through the ScrapingBot API - web results, images, videos, news, shopping, local places, Google Maps listings and place reviews, for any country and language. Use when the user wants search results, SERP data, local businesses or Google Maps reviews. Requires SCRAPINGBOT_API_KEY.

  • Reads credentials
  • Sends data out

12 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every response: searchParameters (your query echoed), creditsUsed.

    line 52

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Google results with ScrapingBot

POST https://scrapingbot.io/api/v1/google, headers x-api-key: $SCRAPINGBOT_API_KEY and Content-Type: application/json. Body: {"endpoint": "<endpoint>", "params": {...}}. 10 credits per call, charged only on success. Timeout 15 s.

Endpoints

endpointUse forRequiredResults field
/searchWeb resultsqorganic, peopleAlsoAsk, relatedSearches
/imagesImagesqimages
/videosVideosqvideos
/newsNewsqnews
/shoppingProducts, prices, storesqshopping
/placesLocal businessesqplaces
/mapsMaps listings, or one place by IDq, or cid/placeId/fidplaces, ll
/reviewsReviews of a placecid, fid or placeIdreviews, nextPageToken

Params

  • q: query; site:, quotes and - work as on Google.
  • gl country (us, gb, de), hl language (en, es). Use these for market targeting; location is passed through but city-level targeting is not reliable.
  • num (Google returns at most 10 per page), page (from 1), start (offset).
  • tbs: time filter qdr:h|d|w|m|y. autocorrect, safe (booleans).
  • /places, /maps: ll viewport like @30.27,-97.74,12z.
  • /reviews: sortBy = mostRelevant (default), newest, highestRating, lowestRating; nextPageToken for the next page (~20 reviews per page).

Workflow for reviews: /places or /maps with q → take cid (or placeId) from a result → /reviews.

Example

curl -X POST "https://scrapingbot.io/api/v1/google" \
  -H "x-api-key: $SCRAPINGBOT_API_KEY" -H "Content-Type: application/json" \
  -d '{"endpoint": "/search", "params": {"q": "best espresso machine", "gl": "us"}}'

Fields worth reading

  • organic[]: position, title, link, snippet, sometimes date.
  • images[]: title, imageUrl, imageWidth, imageHeight, thumbnailUrl, source, link.
  • videos[]: title, link, channel, duration, date, source.
  • news[]: title, link, source, date.
  • shopping[]: title, price, source (store), rating, ratingCount, link.
  • places[]: title, address, category, rating, ratingCount, website, latitude, longitude, cid; /maps adds phoneNumber, openingHours, placeId, fid.
  • reviews[]: rating, snippet, date, isoDate, likes.
  • Every response: searchParameters (your query echoed), creditsUsed.

Errors

Errors are {"success": false, "error": "..."} and are never charged.

  • 400: missing q (or place ID for /reviews). Fix and resend.
  • 401 bad key; 402 not enough credits (tell the user); 429 concurrency limit (free plan allows 1 request at a time; wait and retry).
  • 408 / 5xx: temporary; retry with backoff.

Docs: https://scrapingbot.io/docs/google

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.