World’s largest Grok Bot skill repository
Short SKILL.md units. Name, when to use, short steps. Browse by aisle — Inbound, Decide, Outbound, Grow, Keep.
104 skills · 58 creators · 5 aisles
by Agints
Use when a specialist is blocked after one retry on config, skills, or access.
View skillUse when a Chief of Staff Bot owns inbox/Slack/calendar and a to-do list would go stale.
View skillUse when #customer-escalations contains a ticket link plus “needs repro.”
View skillUse when meetings are recorded in Fathom and the human needs you-committed vs they-committed lists.
View skillUse when the 7:30am Gmail charter runs: easy-archive, glance mail, action-mail drafts.
View skillUse when Research → Write → Review must be a group, not a silent DM pile.
View skillUse when tasks leak across notes, chat, email, docs and standups need one board.
View skillUse when the human needs this morning's standup and the repo is the source.
View skillUse when verifying frontend, screenshots, or browser logs against a local server.
View skillUse when the human says fix this AUN /aun URL and the repo files must match the comments.
View skillUse when a PR is open and the agent should keep it green without merging.
View skillUse when Prettier, protect-files, Stop prompt, or git if-filter must always run.
View skillUse when commits can auto-draft but production deploy must only run on /prod-deploy.
View skillUse when every edit should run a repo-root formatter hook.
View skillUse when a skill would send, pay, deploy, force-push, or merge if the model auto-loaded it.
View skillUse when setting stop lines for send, pay, deploy, delete, and Auto-review rules.
View skillUse when Grok plans, Hermes executes, Grok reviews, and cards must fit 6–8 concurrent tasks.
View skillUse when a coding change needs a spec gate before any PR and a verifier that did not write the PR.
View skillUse when a board should break jobs into cards for other agents, not run the code.
View skillUse when a quiet night is the correct output and a chatty bot would wake the human.
View skillUse when a demo, eval, or article might be theater and the file is the evidence.
View skillUse when a recurring job should not remember in chat.
View skillUse when a long research article is the output, not a pulse blurb.
View skillUse when a coding task is about to start without a written design.
View skillUse when implementation is about to start without a failing test.
View skillUse when daily notes should compact into MEMORY.md overnight.
View skillUse when parallel engineering bots would otherwise collide on the same files.
View skillUse when the manager Bot should not do the compute.
View skillUse when writing or fixing Python and a uv-based TDD skill is installed.
View skillUse when a plan is approved but each stage still needs a human go.
View skillUse when work moves between bots as a HANDOFF block on disk.
View skillUse when a buyer-matching LinkedIn post has engagers and the list is not yet in Instantly.
View skillUse when one agent covering find/watch/write/inbox is averaging four jobs and mistakes are too big.
View skillUse when the site needs an 08:00 pulse and the bot must not publish.
View skillUse before any outbound draft — agents write like you only after they read you.
View skillUse when live X firehose and indexed web both matter (competitive, mentions, pricing).
View skillUse when the page must show up in AI answers by first ranking pages 1–3 of classic results.
View skillUse when the Meta campaign must be created end-to-end and the agent must not spend money.
View skillUse when the Facebook Ads MCP is connected and the user mentions Meta campaigns, budgets, or pixel.
View skillUse when Meta creative should sell the customer's desired outcome, not tinker targeting.
View skillUse when a landing-page URL should become a paused Meta campaign, or a morning brief should run dry-run first.
View skillUse when the account can fire a deep conversion and keywords need family-level ad sets.
View skillUse when lots of sites already link a weaker page you can beat.
View skillUse when organic remix should become a LinkedIn ad with a signup CTA and engager capture.
View skillUse at install, before Google/Meta/Instantly skills.
View skillUse when Search Console and Ahrefs/SEMrush should become a post, meta, and internal links — not a publish.
View skillUse for X vs Y, X alternative, X review, how to X pages you can own.
View skillUse when a new agent or skill needs a hire-style spec before any routine.
View skillUse when packaging a skill directory with required SKILL.md plus optional scripts/references/assets.
View skillUse when placing AGENTS.md at repo root and in nested packages so closer files win.
View skillUse when an LLM must call an external API through well-named tools, not a one-off script.
View skillUse when any PDF extract, merge, form-fill, or OCR is the job — trigger on .pdf, not on the word skill.
View skillUse when a new skill needs write → eval → iterate, or an existing description needs better triggers.
View skillUse when a Claude Code skill needs disable-model-invocation, fork, or allowed-tools beyond the spec six.
View skillUse when a team needs /plugin marketplace add org/repo so skills version together.
View skillUse when a skill is trusted and the next question is which scheduler owns cadence.
View skillUse when instructions and learnings must load at session start as files, not chat.
View skillUse when a Cloud Agent Build must be shared and long-running processes must survive the snapshot.
View skillUse after the skill is trusted and a trigger (cron, PR, Slack) should fire it.
View skillUse when the team needs versioned rules that are not a SKILL.md procedure.
View skillUse when a Cursor skill must live in .cursor/skills/ (or .agents/skills/) with name matching the folder.
View skillUse when a workflow needs a folder with SKILL.md, then references/ and scripts/ on demand.
View skillUse when a CoS or specialist is about to code, browse long, or process data on the Grok Bot computer.
View skillUse when one omniscient agent is mixing mail, evals, and outbound in the same memory.
View skillUse when SKILL.md packages should load the same way plugins do.
View skillUse when two Bots must share files, cookies, or a login.
View skillUse when making a browser agent and the skill does not yet hold.
View skillUse when writing or reviewing a skill's six fields — especially the approval field people skip.
View skillUse when someone is about to paste a giant prompt instead of a reusable recipe.
View skillUse when the first good output is about to be scheduled.
View skillUse when a public playbook URL is the source and save-as-skill is the output.
View skillUse when Teach a task is available and the workflow is visible on the computer.
View skillUse when a taught workflow should be a blueprint others can install.
View skillUse when a Bot is about to 'remember' a fact that will go stale in the profile.
View skillUse when a trusted skill should run non-interactively in CI.
View skillUse after a one-off Build task worked and the method should be reusable.
View skillUse when a trusted Hermes skill should run on a clock without improvising.
View skillUse when the Hermes agent owns orchestration and Grok Build owns the code.
View skillUse when a Hermes skill must meet the hardline layout and cron is opt-in via /suggestions.
View skillUse when Hermes is about to accumulate unbounded chat memory.
View skillUse when a Hermes skill must match hub layout so /learn and skillmanage can find it.
View skillUse at install: smallest useful roster plus a CoS, not 20 bots on day one.
View skillUse when a skill is not bundled and must be installed from hub or git.
View skillUse when a trusted skill should fire isolated from the main chat.
View skillUse when the agent needs gh and the PAT must not sit in a dotenv.
View skillUse when OpenClaw is about to remember in chat instead of the file layout.
View skillUse when a new OpenClaw skill must be created to the bundled contract.
View skillUse when an OpenClaw skill is installed but silent because gates failed.
View skillUse when capturing or editing an OpenClaw skill through the workshop.
View skillUse at every CoS turn before routing work.
View skillUse when a new chat would otherwise forget the last session's state.
View skillUse at the moment the agent is slow or looping, not in the abstract.
View skillUse when writing or reviewing React/Next UI and the skill is installed.
View skillUse when a 3D, game, or scene build is about to start without locked reference stills.
View skillUse when a build must match locked look plates via screenshot → delta → fix loops.
View skillUse when blocking, materials, camera, or render should be driven through Blender MCP (not pasted Python).
View skillUse when Blender/Unreal/Unity must be driven via desktop GUI because MCP is unavailable.
View skillUse when a user photo or reference must become an editable Blender scene matched back to the photo.
View skillUse when a concept still must become a graybox in Blender then a playable slice in Unreal or Unity.
View skillUse when a floorplan image or PDF must become a scaled 3D walkthrough or orbit scene.
View skillUse before art or tech when a game idea needs player fantasy, 30s loop, win/lose, controls, and one unique verb.
View skillUse when a build needs scripted agent play sessions with screenshots, logs, and a bug list with repro.
View skillUse when props, characters, or VFX should be built in parallel under one shared look-lock with a single merge owner.
View skillUse when Grok Bot / agent spend is high, context is bloated, or you want more agents on the same token budget.
View skillNo skills match.