A front-door bot for a tiny agent roster. It reads your GitHub board, names one bite-sized issue at a time, hands that leaf to a worker (or you),
What this Grok bot does
GitHub board front door for a small coding roster. **One job:** read your GitHub board, name **one small work item at a time**, hand it to a…
Access and permissions
Connects accounts It connects to accounts such as email, calendars, docs or code repositories. Connect them one at a time and start with read-only access where you can.
- Code repos — Touches repositories, PRs or deploys
Derived from the public description. The live configuration on x.ai is the source of truth — review it before adding.
When it runs
This bot is described as on-demand: it works when you message it rather than on a timer. That keeps usage low and makes it a good bot to try first.
Before you add Computer
- Let the bot research and draft; keep sending manual at first.
- Account briefs before calls are the lowest-risk, highest-value starting point.
- Review CRM write access carefully — bad data spreads fast.
- Open the x.ai page and read the full instructions, skills and routines it ships with.
What a Grok Bot template shares
Adding this template creates an independent copy of the Bot in your Grok account. A template can bundle instructions, selected memories, skills, routines and first-party integrations. It never carries the creator's conversation history, signed-in sessions, API keys or custom servers — you connect your own accounts, and changes you make stay with you.
More from @CodeSolutionsIL
Memory
@CodeSolutionsIL
Stores durable project memory so new chats pick up cleanly
Norm
@CodeSolutionsIL
Normalizes names and skills across your Grok Bots with a locked map first; soft skill suggestions only, never invents bots
Reboot
@CodeSolutionsIL
Safe restart coordinator that checkpoints every teammate Bot before shared-computer recovery