Browse official xAI listings separately from observed X popularity, or sort the complete directory by X likes and when gtemplate.net first found each Bot.
Worth keeping? Bookmark this page with ⌘D or Ctrl+D.
Showing 25–48 of 751 Bots
Hands meme-making over to a bot: describe the joke and it produces the picture or the short video version through the Memelord API, so you are not stitching a template together yourself. Useful when the reply is funnier as an image than as a paragraph.
Searches rental and home listings around your city, budget, neighborhoods, and must-have constraints.
Sits across people, projects and your other assistants, and its job is to make what you said matters actually turn into work that is moving somewhere.
Starts from proven performers rather than everything you have posted, picks the strong hooks, formats 9:16 with captions, and ships in weekday batches.
Takes footage from X or your own files, watches it, decides what the moment actually is, captions the talking GIFs, and files the output into buckets rather than dumping it in one folder.
Reviews a filmmaker agent's output against the brief you actually gave, calls keep or recut, and keeps the loop running rather than handing back the first render.
Writes short alt text focused on the part of the image that actually matters, so posts stay accessible to blind readers without you writing it every time.
Finds practical award routes from your points and travel plans.
Turns a rough intent into testable, goal-shaped prompts and then keeps the loop honest, so the coding agents underneath it are working against something specific enough to check.
Longform reviews, Setups and the Shortcuts Archive, all answerable in one place. Another creator archive: the corpus is the publication's own writing, not a scrape of the wider web.
Every week it works out who actually showed up in your replies, likes and reposts, ranks the top hundred, and sends you the list as a digest.
Ranks five hundred people by how much they engaged that month, flags who is newly in and who dropped off, and files the result as a private X list named for the month.
Plans a trip from both angles at once: the cheapest way to get there and the least painful way, using live fares alongside the miles, points and current promotions you already hold. The recommendation comes back short, with the reasoning behind it. It works in Japanese.
For someone running more coding work than one person can watch. It queues the work, spins up cloud coding agents to actually do it, checks in on your open pull requests roughly every half hour, and keeps the whole thing moving - an engineering lead for a fleet of agents rather than a single copilot.
Runs a research question through five specialist stages instead of a single pass: a deep-dive brief, a claim-and-source fact check, a competitor sweep, trend monitoring, and a final quality audit on its own output. That last self-verification step is the part most research bots skip.
This one holds the thinking end of a coding setup and is deliberately kept off the keyboard. It works out what a task really requires, argues with the approach until it stands up, and reads back over whatever gets built. Once a job is ready it wraps it up and passes it along to a separate agent that does the writing.
For errands, school things and one-off life admin that a calendar entry feels too heavy for. Send it a screenshot that has the time and place on it, or paste the chat where the plan was made, and it keeps hold of the detail until you need it back.
Goes through the pull requests sitting in your queue and sorts them into what can merge now, what still needs a review and what should simply be closed. The point is to arrive at a queue you can clear rather than a list you keep scrolling past.
Bundles a large skill library for building things with an advisory council of specialist voices covering engineering, business and the general automation of a life.
Takes first pass on customer tickets: answers how-to questions, looks up billing details and keeps the support inbox moving. Anything touching money, such as a refund or a payment dispute, is held for the owner to approve rather than actioned on its own.
Accountability for people whose programme rarely survives contact with a busy calendar. Once a day it asks whether the workout got done; a yes is logged, and a no triggers a reshuffle of everything still to come, so the week's volume is redistributed instead of quietly lost.
It asks what you actually follow before it starts, so the weekly digest is the issues you care about rather than everything that shipped.
Point it at a frontend, interface or architecture job and it drives Anthropic's Claude Code CLI on your behalf, running Opus unless told otherwise. When the run exits it comes back with a pull request already opened, and other models stay parked for the occasional task that calls for unusual judgment.
Reviews the state of your compliance programme each weekday, flags controls that have drifted and vulnerabilities still sitting open, and escalates them to whoever owns the fix. When everything is in order it stays quiet rather than sending another all-clear.