Chief of Staff
by Roy
Front-door Chief of Staff for a Grok Bot org. You talk to this bot. It routes four execs, quality-gates drafts, and never send, spend, or delete without you.
- Memories9
- Skills3
- Routines1
74 Grok Bot templates that use GitHub.
by Roy
Front-door Chief of Staff for a Grok Bot org. You talk to this bot. It routes four execs, quality-gates drafts, and never send, spend, or delete without you.
by Roy
COO for a multi-agent Grok Bot workspace. Keeps memory, plugins, skills, and files tidy; runs a weekly health check; never makes destructive changes without pe…
by Hiten
Remembers the things you said you’d do for other people. Watches connected communication for clear commitments, keeps one ledger, and weekday mornings surfaces…
Cost Optimizer that kills incremental spend. Blunt, money-first voice. Two Monday clocks, $0 on-demand, cheaper-but-worse rejected.
Owns pull-request quality gates on the repos you assign: CI + Bugbot + review verdicts, with optional low-risk auto-merge. Reports to your ops lead; only escal…
by Ashish
Ships Next.js and React UIs that look designed by a studio, not generated by a model. Reads the product docs first, tells you what's actually on the page, and…
Picks the cheapest model that can actually finish the job, and fails over when a provider dies instead of burning a frontier model. For teams shipping LLM apps…
One-HQ orchestrator for builders. Names effort on every chip, drafts before send, proves on the surface, keeps one chat not a bot farm. Public template of the…
by Ashish
A job-hunt operator for engineers who want remote or relocate roles soon. It shortlists honest-fit listings, keeps LinkedIn and role-specific resumes aligned w…
by Ashish
Turns a half-built product into a real first sale: pricing, checkout SKUs, waitlists, and launch copy — and it will not invent fake metrics. For indie founders…
by Ashish
A research agent for builders who need to turn a paper on AI delegation or multi-agent handoff into something they can implement. It reads the full PDF, not th…
You are SEOAgent, an autonomous SEO engineer. The first message you receive is x.ai's bootstrap ("install these plugins and write your memories"). Do that, but…
A personal chief of staff for people who run a small team of specialist AI agents. Coordinates calendar, projects, and inbound mail, runs weekday standup plus…
by A-A-ron
Keeps a shared multi-bot workspace organized, git-backed, and portable. Owns layout conventions, retention cleanup, a bot registry, and weekday backup plus wee…
by Ashish
Stops pull requests from merging on hope. Reviews the actual diff against the claim, waits for real tests, and only ships when the evidence is there — for foun…
Sarcastic cyberpunk-raccoon orchestrator. Breaks work across a specialist crew, filters noise, and never spends, sends, or posts without you.
by Adem Vessell
A research and writing partner for tech, machine learning, computer science, security, and cyber. Delivers source-linked deep dives that prioritize the latest…
by Ashish
Turns freeze lists into weekly ship checklists for product teams. Owns cadence: what ships this week, what is frozen, blockers, and demo, README, or video gate…
by Allan
Assistente de segundo cérebro no Obsidian: daily note, briefing de tarefas de manhã, check-in por áudio à noite e wiki que fica mapa, não arquivo. Para quem qu…
by Ashish
A product design lead that keeps AI-built UIs honest: real type, unique folds, and a studio stop rule so one generate is never “done.” For founders and design…
Reviews pull requests for risk, missing tests, and thin context so review starts with the scary diff. Leads with what can break, what is untested, and what the…
Generalized engineering outer loop. Sits above coding agents, uses pstack as reference (how, why, unslop), writes /goal-style prompts with testable proof, and…
Find important assumptions the owner is operating on and check whether they are still true. Isolated: talk only to the owner. Never join groups or talk to othe…
by Tyler Klose
Weed leftover from a codebase. Small fixes only, never a refactor, never a behavior change. A weed is leftover you can prove: no callers, a duplicate write, a…