Invention Detective
Watches named GitHub repos for technical invention candidates you confirm
Summary excerpt from the creator’s share page. Not independently tested.
What the share page says
Watches the GitHub repos you name for technical invention candidates. After you approve one, it builds an invention disclosure (IDF) and technical appendix from the code in a private repo you own, checks it against a completeness checklist, and prepares questions for the people involved, so the record stays in a private repo under your own GitHub account. Not a lawyer; your counsel decides what to file.
Description as published on the x.ai share page when last checked (2026-11-01).
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
- GitHub
- Promised limits
After you approve one, it builds an invention disclosure (IDF) and technical appendix from the code in a private repo you own, checks it…
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 engineering team or solo builder who wants a first pass at spotting patentable work buried in their own GitHub commits, drafted into the paperwork a patent attorney would actually want to start from.
Not for
Anyone looking for legal advice on whether to file, since its own description is explicit that it is not a lawyer and leaves that call to your counsel.
What it does
It watches the GitHub repositories you name and surfaces candidates for a technical invention disclosure as it spots them in the code, rather than waiting for you to go looking. Once you approve a candidate, it drafts the invention disclosure form itself plus a technical appendix pulled straight from the relevant code, and runs the draft against a completeness checklist before handing it back. It also prepares the questions an attorney would likely ask the people who actually wrote the code, so that conversation starts prepared instead of cold. Everything it produces lives in a private repository under your own GitHub account, not a third-party service, and the description is careful to say your counsel still decides what, if anything, gets filed.
First messages to try
- Watch the acme-org/core-engine repo and tell me the next time a commit looks like it might be worth an invention disclosure.
- Here's a pull request I think is novel — draft the IDF and technical appendix for it and run it against your completeness checklist.
- Before I loop in our outside counsel, prepare the questions you'd want answered by whoever wrote this module.
Apps and accounts
Its description mentions GitHub repositories you name for it to watch, and a separate private GitHub repository you own where it keeps the disclosure record. It names no other outside account and does not claim to replace a patent attorney.
Cautions
- It flags candidates and drafts paperwork, but the decision about what actually counts as an invention, and what to file, is still your counsel's call.
- Giving it repo access means it can read your code history closely, so scope it to the repos you actually want scanned.
Compare with: PR Reviewer by MustafaGrok Bug Bot by zachery miller
Before you add it
Specific to this Bot, from what its description says:
- It names GitHub. 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 GitHub ↗
- Its description makes a promise about limits. Confirm it in the Bot's skills and rules before relying on it.
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, Andre Marais. 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 and kydlikebtc/awesome-grokbot. Row metadata is CC0. 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)
[](https://www.grokbotwiki.com/bots/invention-detective)
Or promote this template in the labelled Featured row, from $19.