When should you use it?
- You keep correcting your AI in the same ways every time you hand it a recurring task
- You want to write a skill, project instructions or a style guide for one kind of work
- You have a few saved or exported chats where you edited the output until it was right
Not for: Tasks you have never done with AI before, since there are no corrections to learn from; Chats that contain client secrets or personal data you cannot share with your AI provider
What do you need, and what do you get?
You need
- Two or three past chat transcripts or exports for one task area
- The name of that task area, for example client emails or product descriptions
- Optionally, a few of your best finished outputs for the follow-up skill-writing step
You get
- A deduplicated list of one-sentence rules, most frequent first
- Rules phrased close to the words you actually used
- Material for a skill file you can attach to future sessions
How does it work, step by step?
- Pick one task areaChoose a single kind of work, such as replying to client emails, so the rules stay focused.
- Collect past sessionsExport or copy two or three chats in that area where you pushed back on the output until it was usable.
- Run the promptPaste the prompt below into a new chat, name the task area when asked, then share only those transcripts.
- Prune and saveRead the ranked list, delete anything that was a one-time preference, and save the rest as the rules section of a skill or instruction file together with your best examples.
- Keep it currentAfter future sessions where you made fixes, ask the AI to add any new rules to that file instead of starting from scratch.
The prompt
The original prompt by Omer Feinholtz, word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in Claude, ChatGPT and Gemini. Values in lime are placeholders.
Original prompt by Omer Feinholtz
Start by asking the user which task domain they are building a skill for. Wait for their answer before moving on. Once you have the domain, ask them to share past session transcripts or exports from that domain only — do not accept or analyze sessions from unrelated domains. Go through those sessions chronologically and flag every moment where the user corrected the AI, rejected an output, deleted AI text, or rewrote it themselves. Include rejections with no explanation — those still carry information. Turn each flagged moment into the specific rule or preference it reveals, using the user's own words where possible. One rule per correction. Never generalize into vague advice like "be more concise." Dedupe the rules, drop one-offs that contradict a repeated one, and output the final list ranked by how often each rule appeared. Most frequent first, one sentence per rule, no commentary before or after. Only extract rules from what actually happened in the transcripts — never invent corrections.
Exactly as published by Omer Feinholtz in How to create your own skills.
Our adapted version (optional)
Fill in the blanks (optional; the copied prompt uses your values)
I want a rules list for my AI, built from my own past corrections, for this kind of work: {task_area}. I will paste {number_of_transcripts} past chat transcripts from that area only. Ignore anything unrelated and tell me if a transcript does not fit. Read them in order and note each point where I changed, rejected or rewrote your output, even if I did not say why. Turn each point into one concrete, checkable rule, using my wording where you can. Merge duplicates, drop one-off preferences that conflict with a repeated rule, and list the rules from most to least frequent with a count next to each. Only use what happened in the transcripts. Return just the numbered list. Transcripts: {transcripts}
What can go wrong?
- Transcripts often contain names, prices and client details; strip anything sensitive before you paste them in.
- The model can still overreach and turn a single remark into a rule; check each rule against what you really meant.
- A long list dilutes attention, so keep the handful of rules that matter most and move the rest into examples.
- Mixing task areas produces muddled rules; run the prompt once per area.
Our take
This is one of the more practical ideas we have seen for improving everyday AI output, because it mines evidence you already have instead of asking you to invent a style guide from memory. The prompt is well built: it asks for the task area first, refuses unrelated transcripts, counts silent rejections as signal, bans generic advice and forbids invented corrections. We ran it word for word on three synthetic chats about weekly client update emails, holding ten corrections (two of them repeated) and one draft rejected with no reason, plus an unrelated chat about a recipe. It asked for the task area before anything else, left out the recipe chat with a one-line note, turned the silent rejection into a rule about length, ranked the two repeated corrections first and returned ten one-sentence rules. Two of them overlapped, both about how to close the email, so the dedupe is good but not perfect, and that one-line note means it did not quite meet its own no-commentary rule. Omer first published this prompt on his own newsletter in September and reused it in a guest post on The AI Maker in October; we link to his original.
Where the time goes back: You stop repeating the same fixes in every session, because the corrections you already made become standing instructions the AI reads before it starts.
FAQ
Which AI does this work with?
What do I do with the list?
Why insist on the user's own words?
Source and credit
The original prompt on this page is by Omer Feinholtz, shown word for word with a link to where it was published. The summary, notes and adapted version are ours.
- Original
- How to create your own skills
- Creator
- Omer Feinholtz
- Published on
- The AI Orchestrator (Substack)
- Original date
- Sep 4, 2026
- License
- Not openly licensed; the original prompt is shown word for word with credit and a link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 22, 2026: passed. Dry-run tested by our AI test agent on sample input. Dedupe good but not perfect; the one-line note slightly bends the no-commentary rule.
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: How My Tiny AI System Saves Me 100 Hours/Year (guest post on The AI Maker) by Omer Feinholtz, hosted by Wyndo. 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.