Skip to content
Grok Bot

Marketplace

Grok Bot Marketplace Guide: Bots and Templates Worth Studying

A practical tour of the Grok Bot Marketplace, including engineering, marketing, sales, product and personal Bots—and what to check before adding one.

The Grok Bot Marketplace is becoming one of the easiest ways to understand what people think persistent AI agents are actually good for.

Instead of starting from a blank prompt, you can inspect Bots built around specific jobs.

The official Marketplace currently lists on the order of eighty public templates across engineering, sales, marketing, design, personal work, recruiting, product and operations—with a Featured row that rotates notable bots.

Haggle Bot

From Grok Bot Team: maps vendor spend, unused seats and renewals, then drafts negotiation moves. xAI’s procurement write-up is the best public case study—savings figures are author-reported, and every vendor-facing send still needs a human yes.

Projects Manager

Projects Manager turns Notion projects and tasks into a coordination layer for specialist Bots.

What makes it interesting is what it doesn’t do: it manages the project rather than pretending to be every specialist itself.

SEO & AEO Desk

This Bot takes keyword input or Search Console data and turns it into content ideas and writer-ready briefs.

For teams experimenting with agent-assisted content operations, this is a more grounded starting point than “write 100 SEO posts.”

Researchy

Researchy is positioned as a sourced research and fact-check desk using live search. That makes it useful to study if your Bot’s output needs dated evidence rather than pure model memory.

Lingxi’s Engineer Bot

This one acts more like an engineering supervisor: it boards work, launches cloud coding agents, watches pull requests and escalates merge decisions.

Stalk Bot

Stalk Bot is a competitor-intelligence setup that monitors products, newsletters, pricing, jobs, changelogs and public X activity.

Flora

Not every Bot is corporate. Flora keeps a private plant-care log and weekly reminders, showing how persistent memory plus a routine can produce a useful personal workflow.

What to inspect before adding a Bot

A good Marketplace entry should make four things obvious:

  • What does it own?
  • What tools does it need?
  • What can it change?
  • Where does it stop for approval?

If those answers are fuzzy, installing the Bot does not make the job clearer.

Treat a template as a starting configuration, not as proof that a workflow is safe or appropriate for your accounts.