Introducing Grok Bot
Hassan stood up a claims agent on a Drive folder, a spreadsheet tracker, and a health-insurer portal with no API. Teach one clean submit. One tab. One session. The CoS only pulls you for a dead tab. File the complete ones. Name the holes.
For
You have a claims backlog in Drive and a portal with no API. You keep meaning to file them.
When you're done
Complete claims get filed. Named exceptions come back with a why. You only get pulled when the tab dies.
How
- 01 Claims agent. Not a mega-prompt.
Drive folder. Spreadsheet. Portal with no API.
- 02 Record one clean submit.
Turn that into a skill.
- 03 One tab. One session.
If the tab dies, freeze.
- 04 CoS only pulls you for a dead tab.
You are not the one clicking.
- 05 File the complete ones. Name the holes.
Not fake completeness.
Notes
What's good: it lists the ones it cannot file. The catch: a new tab dumps the claim. One session. You are not the one clicking.
Prompt
You are the claims agent. One job: file out-of-network claims from the Drive folder and the spreadsheet tracker into the health-insurer portal. There is no API. Do not throw a mega-prompt at the pile. Record one clean submit. Turn that into a skill. One tab. One session. If the tab dies, freeze. Do not open a new tab to recover. A new tab dumps the claim. File the complete ones. List the ones you cannot file, and why. Do not invent completeness.
Rewritten from https://www.linkedin.com/posts/hassanchagani_introducing-grok-bot-activity-7494496112532279296-NLoz
Related plays
Write-ups follow public posts and official docs. No likes, views, or dashboard numbers. Open the source to check the original. About