patent-search
Skill206 starsChanged 8 months agoMITView on GitHub
Search 100M+ patents via the MCP server's BigQuery tools. No standalone scripts; everything goes through the MCP tools registered by the patent-creator server.
- Reads credentials
6 other projects use a version of this.
Adopted by
Most recently taken up by
- ZimoLiao/scholaraiotheir own version, first seen Oct 8, 2026
- handsomestWei/patent-disclosure-skilltheir own version, first seen Oct 8, 2026
- Open2Loop/claude-patent-skillstheir own version, first seen Oct 8, 2026
- Madyleisured4213/patent-disclosure-skilltheir own version, first seen Sep 3, 2026
- Linearl/reasonix_skill_repotheir own version, first seen Aug 28, 2026
- MrEgg2021/patent-skillstheir own version, first seen Jun 11, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- handsomestWei/patent-disclosure-skill★ 13ksame name
- ZimoLiao/scholaraio★ 585same name
- MrEgg2021/patent-skills★ 8same name
- Open2Loop/claude-patent-skills★ 4same name
- Linearl/reasonix_skill_repo★ 3same name
- Madyleisured4213/patent-disclosure-skill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- bigquery-patent-searchSkill
- development-assistantSkill
- epc-searchSkill
- epo-patent-analyzerSkill
- epo-patent-searchSkill
- index-managerSkill
- mpep-searchSkill
- patent-application-creatorSkill
- patent-claims-analyzerSkill
- patent-diagram-generatorSkill
- patent-reviewerSkill
- pct-applicationSkill
- prior-art-searchSkill
- setup-assistantSkill
- testing-assistantSkill
- troubleshooting-assistantSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 48
All words must match; "double quotes" match an exact phrase.
- Very specific: line 50
Use limit=100: it costs the same one credit as limit=10.
- Very specific: line 57
Use search_patent_family_bigquery to bridge from an EP/WO hit to its US family member when you need claims.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Patent Search Skill
This skill points Claude at the BigQuery patent-search tools registered by the patent-creator MCP server. Call the tools directly; do not shell out to Python.
When to use
- Find prior art by keyword, classification, or family.
- Pull full patent records (title, abstract, claims, description) for US patents.
- Cross-reference an EP/WO patent into its US family member to get full text.
Available MCP tools
| Tool | What it does |
search_patents_google | Recommended. Full-text keyword search worldwide (claims and description included), one search credit per call. Needs SERPAPI_API_KEY (free plan: 250/month). |
check_google_patents_status | Is the key set, and how many searches are left this month (free to call). |
search_patents_bigquery | Fallback keyword search across title / abstract / claims (US only for claims). ~341 GiB, about $2, per search. |
get_patent_bigquery | Patent details by publication number: bibliographic data + claims by default; abstract and description are opt-in. |
get_patents_bigquery | Same, for up to 50 patents in one query at the cost of one lookup. |
search_patents_by_cpc_bigquery | Search by CPC classification prefix. |
search_patents_by_ipc_bigquery | Search by IPC classification prefix (good for older or non-US patents). |
search_patent_family_bigquery | All publications sharing a family ID across jurisdictions. |
check_bigquery_status | Verify auth and quota project before a long workflow. |
Cost notes
BigQuery on-demand pricing is $6.25 / TiB (1 TiB free per month). The MCP server enforces a per-query bytes-billed ceiling, defaulting to 350 GiB. Override via PATENT_BIGQUERY_MAX_BYTES_BILLED if you need a larger scan window.
The patents table is unclustered, so a detail lookup costs the same for one patent or fifty; the cost depends only on which sections are requested:
| Detail lookup | Scan | Cost |
Bibliographic only (include_claims=False): title, dates, family_id, CPC/IPC | ~44 GiB | ~$0.27 |
| Default: + claims | ~160 GiB | ~$1 |
+ abstract (include_abstract=True) | +~200 GiB | exceeds the default cap together with claims |
+ description (include_description=True) | ~1.1 TiB | exceeds the default cap |
So: batch with get_patents_bigquery, pass include_claims=False when you only need codes or family_id, and take abstracts from the search results rather than re-fetching them.
Choosing keywords
search_patents_google:
- All words must match; "double quotes" match an exact phrase. No stemming, so search synonyms and plurals separately.
- Lead with the invention's distinctive terms. Common words match thousands of patents and push the closest art down; in testing, adding "heart valve" to a query buried the target past #300, while its distinctive claim words found it at #48.
- Use
limit=100: it costs the same one credit aslimit=10. - Stay inside a classification by adding a full CPC group:
"voice biometric" CPC=G10L17/00(a bareCPC=G10L17finds nothing). - Results show one row per publication, so a US patent and its EP family member can both appear.
search_patents_bigquery (fallback):
- 2-3 keywords work better than long phrases (BigQuery
LIKEmatching is literal). - For non-US patents,
claimsis empty in the dataset; the MCP keyword tool already searches title/abstract for those jurisdictions. For full text on EP/WO, use the EPO OPS tools instead. - Use
search_patent_family_bigqueryto bridge from an EP/WO hit to its US family member when you need claims.
Common workflows
Prior art sweep:
search_patents_google(query=…, limit=100)— broad full-text scan, worldwide (fallback:search_patents_bigquery(query=…, country="US")).- Pick the top hits' CPC codes with one
get_patents_bigquery(patent_numbers=[…], include_claims=False). search_patents_google(query="<terms> CPC=<group>/00", limit=100)— pull adjacent technology (fallback:search_patents_by_cpc_bigquery, ~234 GiB a search).
Cross-jurisdiction lookup:
search_patents_google(query=…, country="EP")(fallback:search_patents_bigquery(query=…, country="EP")).- For the EP hits, one
get_patents_bigquery(patent_numbers=[…], include_claims=False)to get theirfamily_ids. search_patent_family_bigquery(family_id=…)to find the US member with full claims.
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
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.