Grok Bot creates a scheduled specialist team from an owner brief
Sharbel Ayyoub reports giving Grok Bot an exported personal context file and requesting a team. It produced five named specialists, assigned weekday schedules and added a consolidated chief-of-staff brief.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Use my attached work profile to propose a small team of named bots with clear responsibilities and weekday routines. Create the agreed setup, retain my existing bots, and list every role and schedule for review. Keep public posts, outgoing messages and financial actions behind my explicit approval.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- Sharbel Ayyoub
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- Ayyoub reports five named, scheduled specialists plus a chief-of-staff brief, with existing bots retained. This confirms reported configuration, not long-term execution quality.
- Human involvement
- Ayyoub provides the context and asks for creation. Draft-only and no-trading boundaries appear in the generated roster; per-role approval is not described.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Export the operator's existing agent context into a file and supply it to Grok Bot.
- Ask Grok Bot to propose and create named bots with defined roles and recurring routines.
- Create five specialists and assign weekday schedules with limits on sends, posts and trades.
Sharbel Ayyoub tested whether Grok Bot could turn a description of his work into a functioning agent team. He exported context from an existing agent into a file, supplied it to Grok Bot and asked it to propose and create suitable bots with roles and routines.
The reported result was five specialists with weekday schedules. Their jobs covered client success, YouTube growth, X drafts, inbox and partnership triage, and investment research. The setup retained explicit limits on sending, posting and trading. A screenshot description in the article records the roles and scheduled brief times.
Grok Bot also assigned itself a chief-of-staff role and a daily consolidated brief without Ayyoub specifically asking for that extra layer. It left his existing bots in place. The tangible outcome is the configured roster and routines, rather than evidence that each specialist subsequently completed reliable work over a long period.
Ayyoub's wider review reports connector failures, unfinished jobs and losing access after an account suspension. Those are his reported experiences. They limit what a successful initial team setup demonstrates. The user supplied the owner context and requested creation; the article does not describe a separate approval step for every generated role or schedule.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Blog · Sharbel Ayyoub
Frequently asked questions
How did the owner provide the initial context?
Ayyoub says he exported information from an existing agent into a file and attached it to the team-creation request.
What did Grok Bot add on its own?
It assigned itself a chief-of-staff role and a brief consolidating the other specialists' updates.
Does this prove that every routine ran reliably?
No. The supported outcome is the reported configured team. The same review describes connector failures and unfinished jobs during wider testing.
More details
Remaining steps
- Add a consolidated chief-of-staff brief while preserving the operator's existing bots.
About this account
Grok Bot translates an owner brief into specialist roles and schedules and adds its own consolidation routine beyond the explicit team-creation request.
Primary participant account opened with web.run on 2026-10-15; original source date checked on the page. Outcomes are attributed reports, not independently reproduced. Suggested prompt written by Agents In Use, not the source author.
Credit: Sharbel Ayyoub
Source published
Added to Agents In Use
Source checked
Tools and topics
Grok Bot · Exported context file · Weekday routines
Bot setup · Scheduled specialists · Chief of staff
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.