Grok Bot skills tips: how to write, save and reuse skills so your Bots follow the same steps every time. Work through them to master this part of Grok Bot. Each tip is credited to its creator.
Most popular is ranked by likes, reposts and saves on X, and views and comments on YouTube.
Do a weekly job once with your Bot, check it, then have it rewrite the job as a plain script and save a skill that runs the script and reports in two lines.
How this helps you A repeated chore becomes a quick script run with a two-line answer, instead of the Bot doing every step again.
That result is correct. Turn exactly what you just did into a script that needs no AI to run. Test it on today's data and show me it gets the same result. Then save a skill called [skill name] that runs the script, replies in two lines, and only flags numbers that look odd. If the script fails, tell me instead of doing the job by hand.
SkillsSpotted by Jordan Rafealov (YouTube)1 Nov 2026Video: 46.3K views · 826 likes · 67 comments
Point your Bot at a directory of public Bots, give it your goals, and have it list which skills you need and where they come from before adding anything.
How this helps you You start from skills other people already use instead of a blank page, and you choose what gets added.
Go to GrokBot.Rocks, the Every Grok Bot directory. Study the skill sets the Grok Bots listed there have established. My goals are: [describe your goals]. Tell me which of those skills I need for my goals and which bots they come from, then incorporate those skills into how you work for me. Show me the list before you add anything, and never send, post, buy or delete anything without asking me first.
SkillsSpotted by @BrianRoemmele31 Oct 2026156 likes · 18 reposts · 215 bookmarks · 14.7K views
One sentence has a Bot read your sent email, find how you write, and save it as a skill every Bot uses when drafting for you.
How this helps you Drafts come back sounding like you, so you edit less before sending.
Create a skill to write like me for emails and other writing. Use my sent emails in [email account] to learn how I write: length, tone, greetings, sign-offs and words I never use. Show me the skill before saving it.
SkillsSpotted by Founders School (YouTube)25 Oct 2026Video: 80K views · 1.2K likes · 648 comments
Duplicate a Bot and the description comes along; memory starts empty.
How this helps you Rules kept in the description survive when you copy a Bot, so a duplicate starts with the right behaviour.
Read your current description and the things you've learned from our chats. Draft a new description with: your one job, the sources you treat as the truth, what you never do, and what needs my approval first. Write rules as principles, not stories about past mistakes. Show me the draft and don't save it until I say yes.
SkillsSpotted by @unicodef1wn20 Oct 2026912 likes · 0 reposts · 2.8K bookmarks · 1.8M views
Files and logins survive a computer update; installed tools don't. A restore skill puts them back in one message.
How this helps you A computer update becomes a two-minute restore instead of an afternoon of figuring out what broke.
List everything you have installed on your computer that isn't part of a fresh machine: command line tools, packages, background services and anything you set up for me. For each, give the install command, what uses it, and a one-line check that proves it works. Save this as a skill called restore-after-update. Don't include passwords or keys; note where I need to sign in again instead.
SkillsSpotted by Kacper Rutkiewicz (YouTube)19 Oct 2026Video: 24.8K views · 458 likes · 31 comments
Save the goal, decisions, files and next action to a handoff file, then pick up in a fresh chat.
How this helps you Long chats get slow and costly. A handoff file lets you continue in a fresh chat without losing the goal or decisions.
Save a handoff file with the current goal, the decisions we've confirmed, the relevant files and the next action. Then give me a short prompt I can paste into a fresh chat to pick up from here.
SkillsSpotted by @Greshamtrade18 Oct 202641 likes · 0 reposts · 62 bookmarks · 3.3K views
Put most of your effort at the top: code structure, then lint/tests/CI, then prose rules, then human review.
How this helps you It shows where effort pays off most when you check agent work: automatic checks catch more than extra written rules.
Look through my code review comments and past commits to find the most common mistakes agents make in this codebase. Propose a plan to restructure the code I own so those mistakes are harder to make, backed by real examples. Confirm the plan with me before you change anything.
SkillsSpotted by @poteto16 Oct 20267K likes · 0 reposts · 13.2K bookmarks · 758.2K views
One-line routines call skills; the skills live in a repo you edit elsewhere, and a nightly routine pulls them onto the Bots' computer.
How this helps you You improve a skill once, in one place, and every Bot uses the new version the next day.
Make a skill called sync agent skills: pull [repo] and install every skill in [skills folder] where my Bots read skills, remove any that are in [retired folder], and pull [docs folder] too. Then add a routine that runs it every night and tells me what changed.
SkillsSpotted by Brian Casel (YouTube)15 Oct 2026Video: 24.6K views · 250 likes · 26 comments
"Research this deeply" gives no finish line and no reason to stop browsing.
How this helps you A clear finish line stops research from wandering, and you get evidence you can check.
Research [question]. Done means: [measurable outcome]. Use primary sources first. Put the source beside each key claim and label it VERIFIED, INFERRED or UNKNOWN. Stop after [N] searches or when the outcome is met. End with a 5-line handoff.
SkillsSpotted by @ludoonchart5 Oct 20269 likes · 0 reposts · 8 bookmarks · 514 views
Most automations break because they're scheduled before they've worked once.
How this helps you Proving a job works once before scheduling it means your routines fail far less often.
That worked. Save what you just did as a skill: when to use it, what inputs and access it needs, the steps, how to check the result, and what needs my approval.
SkillsSpotted by @Michael_Fenech_3 Oct 2026No public metrics
Most of a browser job can be explained in chat. Record a 20 to 60 second clip of only the part the Bot can't work out, then add anti-jobs before you schedule it.
How this helps you You get a reliable skill from a short clip, and rules that stop it doing the wrong thing on bad days.
Add these rules to [skill name]: If there's nothing new since the last run, reply 'no new activity' and stop. This is read only: never post, like, reply or message unless I ask. If the site is logged out or shows a captcha, stop and tell me. Never write a specific date, post or person's name into the steps; always use what's new that day. Then repeat the full steps back to me.