Teach your bot a chore from a screen recording
Dillon Loomis recorded his screen with narration while sorting a week of desktop files, and his Chief of Staff learned not just what he did but how and why — it compressed the oversized video itself to watch it, answered a question he'd planted mid-recording, and coached him on part two.
plug your Grok Bot in
closeinstall this
Teach your bot a chore from a screen recording
I'm going to teach you a recurring chore by showing you, not by writing it out. I'll give you a screen recording with my voice narrating as I do the task once.
1. Watch the whole recording. If the file is too large to open, compress it under the limit first, then watch it.
2. Learn not just the steps but the WHY — my narration explains the rules, the exceptions, and what I care about. Capture those, not just the clicks.
3. Play it back to me as a drafted skill: the steps, the decision rules, what the output should look like, and where you would stop for my approval.
4. Tell me what would help you learn better next time — what to show or say in a follow-up recording.
5. Once I approve the skill, run the chore on a small safe example first, show me the result, and only then do the full job.
Rules: never delete or move anything irreversibly without my OK; if the recording is ambiguous, ask rather than guess; treat the demonstration as a first draft and confirm the edge cases with me.Copy the prompt and paste it into Grok.
How it’s set up
- Pick a monotonous but well-defined chore you’d never write a procedure for — Dillon’s was sorting hundreds of random desktop files after a busy week.
- Record your screen with voice narration, doing the task once and saying not just what you’re doing but why (the rules and exceptions live in the narration).
- Hand the recording to your Chief of Staff. If the file is too large, it can compress it under the limit itself so it can watch it.
- Let it play the task back to you as a drafted skill, and take its feedback on how to record the next pass so it learns better (Dillon even planted a question mid-video to check it was really watching — it asked him back).
- Test the learned skill on a safe example, then let it run the chore for you. Keep anything destructive (deleting files) behind your approval.
Prompt
I'm going to teach you a recurring chore by showing you, not by writing it out. I'll give you a screen recording with my voice narrating as I do the task once.
1. Watch the whole recording. If the file is too large to open, compress it under the limit first, then watch it.
2. Learn not just the steps but the WHY — my narration explains the rules, the exceptions, and what I care about. Capture those, not just the clicks.
3. Play it back to me as a drafted skill: the steps, the decision rules, what the output should look like, and where you would stop for my approval.
4. Tell me what would help you learn better next time — what to show or say in a follow-up recording.
5. Once I approve the skill, run the chore on a small safe example first, show me the result, and only then do the full job.
Rules: never delete or move anything irreversibly without my OK; if the recording is ambiguous, ask rather than guess; treat the demonstration as a first draft and confirm the edge cases with me.Why it’s cool
It flips how you hand work to an agent: you demonstrate instead of specify. The standout isn’t the file-sorting — it’s that the Chief of Staff learned the how and why from narration, solved its own blocker by compressing an oversized video to watch it, caught a question planted mid-recording, and coached the human on how to teach it better. That’s the lowest-friction on-ramp there is for anyone who’d never write a procedure by hand.
prompt reconstructed by the Curator from @DillonLoomis's published setup — not their verbatim text
I'm going to teach you a recurring chore by showing you, not by writing it out. I'll give you a screen recording with my voice narrating as I do the task once.
1. Watch the whole recording. If the file is too large to open, compress it under the limit first, then watch it.
2. Learn not just the steps but the WHY — my narration explains the rules, the exceptions, and what I care about. Capture those, not just the clicks.
3. Play it back to me as a drafted skill: the steps, the decision rules, what the output should look like, and where you would stop for my approval.
4. Tell me what would help you learn better next time — what to show or say in a follow-up recording.
5. Once I approve the skill, run the chore on a small safe example first, show me the result, and only then do the full job.
Rules: never delete or move anything irreversibly without my OK; if the recording is ambiguous, ask rather than guess; treat the demonstration as a first draft and confirm the edge cases with me.Copy the prompt and paste it into Grok.
what you need
related
Add a Disruptor bot to your team that disagrees with you on purpose
Liam keeps one deliberately difficult Grok Bot around. Mention it in a chat and it goes looking for trouble: it disagrees, challenges the team, pushes back on ideas, and says what it actually thinks - and doesn't care if everyone else agrees. A built-in devil's advocate that kills groupthink and sycophancy.
Run a one-person business on a Grok Bot agent team
Billy Howell runs a 6,000-subscriber local newsletter on a Grok Bot agent team. His method: one project per account, a Chief of Staff that audits the business and proposes the first three revenue agents, perfect each task by hand before spinning off a dedicated bot, then automate the routine work.
One bot, one prompt — it hired its own team
Paste one prompt into a single Grok Bot, Atlas the chief of staff. It interviews you, writes its own operating manual, then specs and launches four teammates — each on its own cloud computer, with a review gate before anything sends.
the week's best, in one email
new plugins, use cases and collections. one email a week. that's it.
▪ you're on the list