grokbotwiki

Prior Art Desk

by Stephen Michael Schmitt (@SM_Schmitt) ↗Personal admin Share link liveChecked

named write-up only · overlap ≠ FTO · I do not file. British bridge-captain register: measured cadence, formal address, dry wit used sparingly. Light seasoning only, one or two idioms per reply: Make it so; Engage; Report; Number One; Tea. Earl Grey. Hot.; The line must be drawn here.; Things are only impossible until they are not. Never claim to be a copyrighted character. Never use franchise names, ship names, series titles, or marks. Never replace the patent answer with the bit. Paste an invention note; get a ranked public-overlap digest and a packet draft for your counsel—never a clearance. One job only: compare a locked F1…Fn feature map against two separate evidence lanes: (A) US patents/applications and (B) dated non-patent literature and market-product disclosures. Patent hits and NPL/MARKET LEADS stay in separate tables. A product is never called prior art unless reliable public evidence predates the relevant critical date; without one, temporal status is UNASSESSED. Weekly watches report only Evidence Diff Ledger deltas (NEW / CLOSER / STATUS-CHANGED). Tavily powers public search when connected. Google Drive is optional for saving the packet. Hard rules: refuse if no pasted/attached write-up; never invent the invention, claims, dates, or sources; never say FTO or clear to file; never file at USPTO.

The creator's description, as published on the x.ai share page when last checked (2026-11-07). Not independently tested.

Open on x.ai and add to Grok BotOriginal post ↗Report a problem

What its description mentions

Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.

Apps it names
Google Drive
Recurring work
Weekly watches report only Evidence Diff Ledger deltas (NEW / CLOSER / STATUS-CHANGED)
Our take

Editorial notes

From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .

Best for

An inventor or small team with a written invention disclosure who wants an organized digest of possibly overlapping public patents and products to bring to their patent attorney.

Not for

Anyone looking for a clearance opinion, freedom-to-operate answer, or filing help, all of which it refuses outright.

What it does

Given a pasted or attached write-up, it locks a numbered feature map and searches two separate lanes: US patents and applications, and dated non-patent literature plus market products. Results stay in separate tables, and a product is only labeled prior art when dated public evidence predates the critical date, otherwise its timing is left unassessed. Weekly watches report only changes, such as new or closer hits, and the deliverable is a packet draft for counsel.

First messages to try

  1. Attached is my invention note for a foldable bike lock. Build the feature map and show it to me before searching.
  2. Run the patent lane only for features F1 through F3 and rank the closest hits.
  3. Set up a weekly watch and tell me what counts as a closer hit.

Apps and accounts

Its description mentions Tavily for public search when connected and Google Drive as an optional place to save the packet.

Cautions

  • Overlap findings are not legal conclusions, and the description says so, so bring the packet to your own counsel.
  • Without Tavily connected its public search may be thinner, so confirm what it actually searched.
  • The formal bridge-captain voice is part of the design; ask for plain replies if it gets in the way.

Compare with: Gazetteer Scout by John BurcheciTwo Lenses: Decide & Cut by SmileHub Dental Labs

Before you add it

Specific to this Bot, from what its description says:

  • It describes recurring work. After adding it, open its routines, confirm the times, and pause any schedule you did not choose.
  • It names Google Drive. Connect those as plugins where one exists rather than signing in through the shared browser, and give it the narrowest access the task needs. What to check for Google Drive ↗
The standard checks for any shared Bot

Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.

  • Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
  • Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
  • Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
  • Give it one small bounded task and read the usage screen afterwards before scaling up.

Related reading: the shared computer permission boundaries the weekly meter

If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task

Attribution

This Bot belongs to its creator, Stephen Michael Schmitt. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, cs68614-hash/awesome-grokbot-templates, ZeroPointRepo/GrokBotDev and kydlikebtc/awesome-grokbot. Imported catalog prose retains CC BY 4.0 attribution; share-page excerpts are labeled separately. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).

Made this Bot? Add a “Listed on Grok Bot Wiki” badge

Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗

Markdown (README)

[![Listed on Grok Bot Wiki](https://www.grokbotwiki.com/badge/listed-dark.svg)](https://www.grokbotwiki.com/bots/prior-art-desk)

Or promote this template in the labelled Featured row, from $19.