A free Claude skill that turns one messy sentence into a finished prompt. But it doesn't remember your decisions in a new chat on its own
Prompt Master is an open source skill you install in Claude. You say what you want in one messy sentence, and it hands back a finished prompt written for the target tool: what the output should look like, which files can be touched, and when the job counts as done. Install is a single ZIP upload. But the English guide going around oversells two things: the skill doesn't kick in on every message, only when you ask for a prompt; and it doesn't carry your decisions into a new chat by itself. Below: the install, the right way to call it, and how to carry your decisions into a new chat.
The skill itself
The repo is MIT licensed and completely free, with over 13k stars on GitHub. If you'd rather go straight there, the button opens the repo; that's where you download the ZIP.
What's extra below: what the skill does and doesn't do, the sentence pattern that triggers it, and how the feature the guide calls "remembers your decisions in every new chat" actually works.
What it does, what it doesn't
The problem is familiar: you write a rough prompt, Claude does exactly what you typed, and you spend three more messages explaining what you actually meant. Prompt Master cuts that loop at the start. From your sentence it pulls out the task, the output format, the limits and the finish condition; if something critical is missing it asks at most three questions, and at the end it gives you one copyable prompt.
What happens in one request
- 1
A messy sentence
"Write a Claude Code prompt for this"
- 2
It identifies the target tool
Asks if it's unclear
- 3
At most 3 questions
Only if critical info is missing
- 4
A finished prompt
One block, a one-line note below
- 5
You run it
Paste into the same chat or the target tool
The last step matters: the skill doesn't do the job itself, it writes the prompt that will. So one message goes to getting the prompt written. The gain is that the "no, I meant this" messages that would have followed disappear.
Install: claude.ai
This is the route the repo recommends, no terminal needed.
- 1
Download the ZIP
Green Code button on the repo, Download ZIP. Don't unzip it
- 2
Open Customize
On claude.ai, Customize in the sidebar, then Skills
- 3
Upload a skill
Pick the ZIP you downloaded
- 4
Make sure it's on
The skill's toggle should be on, then open a new chat
If the skill doesn't show up
Skills on claude.ai depend on code execution. If you can't see the Skills section or the skill you uploaded, check that code execution and file creation is on under Settings, Capabilities. If the skill is on but Claude isn't using it, open a new chat; it isn't added to chats already open.
Install: Claude Code
If you use Claude Code, you clone the repo straight into the skills folder. The repo lists this as the second option; it works, you just have to update it yourself with git pull.
mkdir -p ~/.claude/skills
git clone https://github.com/nidhinjs/prompt-master.git ~/.claude/skills/prompt-mastergit clone https://github.com/nidhinjs/prompt-master.git "$HOME\.claude\skills\prompt-master"After restarting Claude Code you can call it directly by typing /prompt-master.
How to call it
The guide's line "stop writing careful prompts, write messy ones" is half true. The skill's own description is clear: it only kicks in when you ask it to write, fix or adapt a prompt for a specific tool. A plain "build a landing page" message triggers nothing, and Claude just starts on the job. Your sentence has to say you want a prompt and which tool it's for.
Write a Claude Code prompt: a landing page for my agency with a booking section
Write a Cursor prompt: refactor my auth module, touch no other files
Fix this prompt for ChatGPT: [paste your prompt]
Write a Midjourney prompt: a realistic samurai standing in the rain at nightThe prompt that comes out is shaped for the target tool. For coding agents it adds a starting state, the files that may be touched, an "ask before doing this" list and a finish condition; for image tools, comma-separated descriptors and a negative prompt. Read it, tweak if needed, then run it.
Memory: how it actually works
The English guide says "it remembers the decisions you make, every new chat starts already knowing your stack." The skill's own file says something else. Prompt Master has no persistent memory. What it does: it collects decisions already made in that chat, your stack, naming conventions, the things you said not to use, and puts them as a memory block at the top of the prompt it writes. Within the same chat that's very useful, because the new prompt doesn't contradict earlier decisions.
Opening a new chat and carrying on with "you already know my project."
Copying the memory block from the old chat and pasting it into the first message of the new one. The skill's own rule list says the same: re-provide the block in every new session.
## Memory (carried forward from earlier)
- Stack: React 18 + TypeScript + Supabase
- Auth via JWT in httpOnly cookies, not localStorage
- Component names in PascalCase, no default exports
- Tailwind only, no separate CSS filesIf you want it to persist, write this list once and put it in a Project's instructions in Claude; every chat you open in that project sees it. In Claude Code the CLAUDE.md file in your project folder does the same job, covered separately in 114.
The costliest mistakes it catches
The guide says 35, the repo's current version has 37 patterns. You don't need to memorize them, the skill checks them anyway. But knowing the few that burn the most messages fixes the prompts you write without it too.
| Mistake | Before | After |
|---|---|---|
| No success criteria | "Make it better" | "Done when existing tests pass and it handles empty input" |
| No scope boundary | "Fix my app" | "Fix only the login form validation, touch no other file" |
| Two tasks in one | "Explain and rewrite this function" | Explain first, rewrite in a separate message |
| A blank check for the agent | "Do whatever it takes" | "Ask before deleting a file or adding a package" |
| Implicit reference | "Add the other thing we discussed" | Restate the full task every time |
Does it work in ChatGPT and Cursor too
The skill runs inside Claude; it doesn't install into ChatGPT or Cursor. The "works there too" part means this: in Claude you can have it write prompts for ChatGPT, Cursor, Gemini, Midjourney and more than thirty other tools, then paste the result into that tool. Name the target tool in your sentence and the prompt follows that tool's rules.
DOA: Yapay Zeka ve Otomasyon
Installing these tools on your own is one thing; actually building with them is another. The community has people using these daily and people building systems from scratch.
If you want a system that actually runs in your business, let's talk for 10 minutes; I'll look at what you're trying to build and tell you which path fits. Free, and not a sales pitch.
Book a 10-minute callIf you'd rather learn this alongside people doing the same work instead of on your own, the community is always open:
Join the communityThis is an affiliate link.