← Back to library

Chain skills with a yes-gate instead of one giant prompt

Matt Palmer (@mattyp) describes his Demo bot in his Intro to Grok Bot article. Each day it picks one new tool from his X bookmarks, writes a build prompt with his writing skill and waits for his approval. After a yes, his project-planning skill starts a cloud coding agent on a demos repo. We found it via Carnage (@0xCarnagee).

  • OutcomeAssemble a daily pipeline: pick from a source, draft with a writing skill, wait for your yes, then hand to a planning or build skill.
  • SetupUnder an hour
  • LevelIntermediate
  • CreditMatt Palmer (@mattyp)
View original
Works with
Grok BotChatGPT agentClaudeClaude Cowork

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

When should you use it?

  • You already have small skills and keep rewriting one mega-prompt
  • You want a daily prototype or draft loop with a human gate
  • You can point at a repeating source (bookmarks, inbox label, board)

Not for: Running the build step before you approve the draft; Treating a recorded click path as finished judgment; Pipelines that spend money or publish without a second gate

What do you need, and what do you get?

You need

  • A repeating source to scan
  • Selection criteria for the best item
  • Names of writing and planning skills you already have
  • Where approved work should be built or filed

You get

  • A daily loop description with an explicit yes-gate
  • Draft output held until you approve
  • A handoff into the planning or build step after yes

How does it work, step by step?

  1. Name the sourceBookmarks, a label, a board — one place scanned on a schedule.
  2. Attach skillsWriting skill drafts; planning or build skill runs only after yes.
  3. Insert the gateShow the draft. Do not proceed without an explicit yes.
  4. Harden recordingsIf a skill was taught by watching clicks, add rules for edge cases.

The prompt

Our own prompt, inspired by Matt Palmer (@mattyp) and written to work in Grok Bot, ChatGPT agent, Claude and others. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt5 variables
Build a gated skill chain for a daily loop.
Source to scan: {source}.
Pick criteria: {criteria}.
Writing skill: {writing_skill}.
Planning or build skill: {planning_skill}.
Target system after approval: {target_system}.

Every run:
1) Read the source and choose the strongest item against the criteria.
2) Use the writing skill to draft the output.
3) Show me the draft. Do not proceed without an explicit yes.
4) On yes only, use the planning skill to hand work to the target system and report when it is running.

Silence is not approval. Do not spend money or publish.

Inspired by Matt Palmer (@mattyp): Intro to Grok Bot (X Article). The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • A recorded skill captures clicks, not judgment; add rules or it fails when the first odd case appears.
  • One macro is not a pipeline; you need ordered skills plus a human gate.
  • Never let the build step start on silence; require yes.
  • Keep spend and publish behind a second approval even after yes on the draft.

Our take

Prompt tuning is the wrong bottleneck when you already have skills. Palmer's chain — source, writing skill, yes, planning skill, build — is the pattern worth stealing. We keep the gate mandatory and warn that recorded clicks are drafts until you add judgment rules. One macro is not a pipeline; ordered skills plus a human yes are. In our dry run with fictional bookmarks and two named skills, the agent picked one item, drafted a prototype brief, waited, and only after yes produced a plan handoff — never starting the build on silence. Spend and publish stayed behind a second approval even after the draft yes. Use this when skills already exist. If you teach a skill by demonstration, schedule a pass to write edge-case rules before you let it run unattended. Credit goes to Matt Palmer's own article; Carnage's write-up is where we found it. One detail from Palmer is worth copying as well: each of his agents proves its work with a screen recording, so approving the draft never means blindly trusting the finished prototype.

Where the time goes back: You reuse skills you already trust and only spend attention on the yes, instead of rewriting prompts daily.

FAQ

Do I need a perfect prompt?
The article's point is the opposite: assemble skills you already own and gate them. The prompt is thin on purpose.
What is the human input?
Often just approving the draft. Everything else is source, skills and systems.
Can I record a skill by doing the task once?
Yes, but treat that recording as a draft and add explicit rules before you trust it.

Source and credit

Inspired by Matt Palmer (@mattyp). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Intro to Grok Bot (X Article)
Creator
Matt Palmer (@mattyp)
Published on
X
Original date
Aug 11, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Grok Bot
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. Yes-gate held; skill chain order correct.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Also see: The Grok Bot Team's Own Workflow (X Article, where we found this) by Carnage (@0xCarnagee). A related version of the same idea; credited and linked only, nothing from it is reproduced here.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminPrompt✓ AI dry run

Aim the agent at a janky internal app after it maps the UI

Have the agent study a janky internal UI out loud, complete one end-to-end task with a recording, and stop for login walls instead of guessing credentials.

Credit: Carnage (@0xCarnagee)

Under an hour
Operations & AdminPrompt✓ AI dry run

Copy two working bot roles before you invent one

Start from a short list of narrow, already-used agent roles mapped to your week instead of a vague catch-all Assistant.

Credit: Carnage (@0xCarnagee)

Minutes
Operations & AdminPrompt✓ AI dry run

Require the finished work plus the evidence tape

Make every agent delivery include the artifact, recordings or screenshots, linked sources, guesses called out, and skips with reasons.

Credit: Carnage (@0xCarnagee)

Minutes
Operations & AdminRoutine✓ AI dry run

Publish the sprint changelog from completed tickets

On a schedule, pull completed tickets, decide which are user-facing, draft the changelog from ticket context, and wait for your review before publishing or emailing users.

Credit: u/Senseifc on r/ClaudeAI

Under an hour
Operations & AdminRoutine✓ AI dry run

Trigger useful work the moment a matching email arrives

Define filters on sender, recipient or subject so an assistant summarizes, drafts, extracts or researches as soon as matching mail arrives, with results saved for review.

Credit: XFreeze (@XFreeze)

Minutes