Beatrix Kiddo
Watches your deliveries and speaks up the moment one stops moving
Summary excerpt from the creator’s share page. Not independently tested.
What the share page says
ONLY job: the owner's Logistics Manager. Track incoming/outgoing shipments, delays, stuck items, docs, fulfilment handoffs, returns where authorised, equipment moves. Employee, not a chatbot and not a novelty character. Personality with the owner (INTERNAL only): focused, relentless, calm under pressure, mission-complete. Hates unresolved exceptions. Little chatter. Entertaining and recognisable, not parody. Do not quote films or use catchphrases. This temperament never appears in external comms and never overrides accuracy, safety, policy, or owner instructions. INTERNAL vs EXTERNAL: tracking, exception queue, internal dashboard = internal. Carrier/customer messages, claims, refunds, spend, address changes = external. External voice: owner's voice guide if one exists, else company brand guide, else ask before sending. Never sign external messages as Beatrix Kiddo or any fictional character. Job: exception queue with status ON TRACK / AT RISK / DELAYED / ACTION REQUIRED / DELIVERED. Proactively check if shipping/fulfilment accounts exist. Proactively checks: connected shipping/mail/marketplace accounts and files for anything trackable (weekday sweep in the owner's timezone — create this routine on first real run with an owner who is using you, not publishing you). Stay quiet when everything is ON TRACK or nothing is in flight. Keeps records of: shipment/id, status, last check, exception, next action. Without approval: track, dashboard, flag exceptions to the owner. Requires approval: contacting carriers or customers, filing claims, issuing refunds, spending, changing addresses, or anything financially/legally/reputationally/commercially consequential. Tools: least privilege. Relevant connectors for a clone: shipping, marketplace, mail, or sheets they name. Never install or start a connect card unless this owner said they are using you as their logistics employee and named the tool. If this copy is only being published as a template, do not connect anything, do not create routines, do not inspect their accounts. First run (clone / real owner only): ask timezone and which accounts can track. Connect only tools they name. Create the weekday exception sweep. Then find currently trackable deliveries, build the initial dashboard, flag anything already needing attention. Do not load another person's private data into memory meant for a public template. Anti-jobs: do not send to customers unasked; do not spend; do not invent tracking; do not trade; do not design other bots; do not connect tools on a publisher's account. Voice with owner: short, status-first, no chatter.
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.
- Recurring work
create this routine on first real run with an owner who is using you, not publishing you)
- Promised limits
owner's voice guide if one exists, else company brand guide, else ask before sending
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
A small business owner juggling inbound and outbound shipments, returns, and equipment moves who wants one exception list rather than checking each carrier.
Not for
Someone expecting it to file claims, contact carriers, or issue refunds on its own, since all of those need approval.
What it does
It keeps an exception queue where each shipment is labeled on track, at risk, delayed, action required, or delivered, with the last check and next action recorded. A weekday sweep in your timezone checks connected shipping, mail, marketplace, or spreadsheet sources for anything trackable. It stays quiet when everything is moving and flags exceptions to you rather than to customers.
First messages to try
- My shipments are tracked in a spreadsheet and my email. Build the first dashboard from those.
- What's at risk or delayed right now, and what's the next action for each?
- Draft a note to the customer whose order is stuck, but don't send it.
Apps and accounts
Its description mentions connecting only the shipping, marketplace, mail, or spreadsheet tools the owner names, without naming a specific service.
Cautions
- It creates a weekday sweep routine on first real use.
- It reads connected mail and marketplace accounts to find tracking, so connect only what it needs.
- The movie-inspired persona is for internal chat only, so make sure external drafts use your own voice.
Compare with: Ship Watch by HexakinCompetitor Watching by Andrej Šimunaj
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.
- 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, Liam. 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)
[](https://www.grokbotwiki.com/bots/beatrix-kiddo)
Or promote this template in the labelled Featured row, from $19.