How this helps you
A task you repeat after every event takes one sentence from you, and the output keeps your structure every time.
I will describe how I do [task]. Steps: [1. find the item on the site; 2. use the rating I give; 3. write the result in my style]. My output format: [one-line verdict first, then what I liked, what did not work, and who I would recommend it to]. Save this as a skill called [skill name]. Use it automatically whenever I tell you [trigger, e.g. I have finished a book and how I liked it]. Before you publish anything, show me the draft.
Fill in: [task], the numbered steps, [skill name], [trigger] and your own output format.
What they did
Parker Prompts writes out in his Bot's chat how he reviews a book on Goodreads: search for the book, set the star rating he mentions, and write the review in his style (a one-line verdict, what he liked, what did not work, and who he would recommend it to). He asks the Bot to save this as a skill called write a review, and to use it whenever he says he has finished a book and how he liked it, so the skill works like a trigger. To test it he tells the Bot he finished a book, gives five out of five and a few messy thoughts. The Bot opened Goodreads on its computer, found the book, set the rating and posted a review that, he says, reads like him. He suggests the same pattern for expense reports in a work portal, replies to a repeated customer email, or turning notes into a draft laid out your way.
Who it's for: Anyone who repeats the same write-up or form after finishing something.
Before you start
- A Bot that can already do the task once by hand (here, a site signed in on its computer)
- Your own structure for the output, written as a few short parts
How to try it
- Do the task once through the Bot until the result looks right.
- In the Bot's chat, write the steps in order and describe the output structure you want.
- Say what should trigger it: 'use this whenever I tell you I have finished X and how I liked it'.
- Ask the Bot to save it as a skill with a clear name.
- Test it with a short, messy note and check the result before relying on it.
- If it posts anywhere public, add a line telling it to show you the draft first (our suggestion, not from the video).
What to expect
Parker told the Bot he had finished a book, rated it five out of five and added a few messy thoughts. The Bot found the book on Goodreads, set the rating and wrote the review in his structure.
Common mistakes
- Saving a skill before the task has worked once by hand.
- Leaving the trigger vague. Name the exact situation or phrase.
- Skipping the test with messy input. Real notes are messy.
- Letting it publish without a draft check on anything public.
Related tips
- Do it by hand, save a skill, then schedule: Most automations break because they're scheduled before they've worked once.
- A 9-point upgrade audit for the skills you already saved: Your chief of staff checks every private skill for nine missing pieces, from when to use it to what happens if it runs twice, then drafts fixes for your approval.
- Teach a task by doing it once: Do the workflow while it watches; it records the steps.
Worth knowingThe trigger sentence is part of the skill. Write it as carefully as the steps.Next in Skills →Teach a task the smart way: describe it first, record only the gap
Learn more: How to Use Grok Bot: A Beginner's Guide (2026) · All Grok Bot skills tips