On the bundled sample: 8 findings (5 errors, 3 warnings) in 1 file from 19 rules - ?key=, cx, start, dateRestrict, siteSearch, items[] and link/snippet.

Who it’s for
Developers whose RAG agent, support bot or site search calls the Google Custom Search JSON API or Bing Search API v7 and is moving to Brave Search.

What breaks, and when
Google’s Custom Search JSON API: existing customers have until 2027-01-01 to transition; Microsoft retired the Bing Search APIs on 2025-08-11. A half-ported call fails quietly: data.items is undefined.

What you get
• SKILL.md, an offline Node scanner and the 19-rule table

See it first
The real output of the bundled example is on getreadystack.com/skills/bing-google-search-api-migration-check/ — free, no sign-up, so you see what it finds before you pay.

Install in 30 seconds
Unzip into ~/.claude/skills/, then ask Claude Code: “Google says our Custom Search JSON API has to move by January 2027 and we want to switch to Brave Search. What in this repo has to change? Don’t edit anything yet.”. Needs Node 16+.

What it does not do
It does not call Brave, Google or Bing and needs no API key; it reads source text.

FAQ
Q: How is this different from asking Claude without the skill?
A: The skill carries a dated rule table and a scanner that reads every file, so Claude quotes the exact date and line instead of guessing from memory.
Q: How do I get the files?
A: In your Whop library after paying: the lesson “bing-google-search-api-migration-check.zip”.