Engineering
Tip: make a global skill, not a new bot per capability
Spawning a bot for every capability multiplies A2A chatter and burns quota on middlemen.
What hurt
@jevlorde's common Grok Bot mistake: spawning a whole new bot for every capability. Better: make it a global skill other bots can call — less A2A chatter, less quota burned on middlemen. One tool, many callers. Tip only. Not affiliated with xAI.
What to install or create
List overlapping capability bots → extract one skill → point callers at it → delete middlemen.
Bots
No new bot. Follow the first-run steps.
Plugins
None on day one. Follow the first-run steps.
Routines
None on the first run. Watch one manual pass first.
The prompt
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
First run
- 1Read https://x.com/jevlorde/status/2116331820367376825 (credit @jevlorde).
- 2List bots that exist only to expose one capability to others.
- 3Turn that capability into a global skill (or shared tool) other bots can call.
- 4Update callers to use the skill directly; drop the middleman bot after your OK.
- 5Re-check A2A volume and quota the next day.
Approval fence
Deleting or merging bots waits for your OK.
What to tweak
Steal one-tool-many-callers before you spin up another specialist bot.
Source
jev lorde @jevlorde · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.