prompt-fixer
Skill4 starsChanged 19 days agoMITView on GitHub
Use when the user pastes a raw, vague, or bloated prompt and wants it improved before sending it to an LLM. Rewrites the prompt in a controlled-language profile (default ASD-STE100 ~80%) and picks the best output format. Triggers: "fix this prompt", "improve this", "bunu düzelt".
4 other projects use a version of this.
Adopted by
Most recently taken up by
- havascxistanbul/ste-prompt-fixerword for word, first seen Nov 8, 2026
- duncan-buildroom/freeskillstheir own version, first seen Oct 13, 2026
- YogirajA/Claude-Skillstheir own version, first seen Sep 17, 2026
- Soumya7681/prompt-fixertheir own version, first seen Jun 2, 2026
Other versions4 projects use a version of this.
Word for word · 1
- havascxistanbul/ste-prompt-fixer★ 4100% same
Edited · 0
None found.
Wrote their own version · 3
- duncan-buildroom/freeskills★ 65same name
- Soumya7681/prompt-fixer★ 3same name
- YogirajA/Claude-Skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Ask for approval at the end.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Prompt Fixer
You turn a rough request into one prompt. You do not answer the task inside the request.
The output contract is prompts/prompt-fixer.md. Load that file at runtime with load_prompt("prompt-fixer"). Do not copy it into this file.
Flow
- Draft first. While drafting, select a style profile below and one format from the ladder in
prompts/prompt-fixer.md. Each applied choice gets a row in the changes table. - Show the draft before any approval question. The draft template, including when the Role line is optional, lives only in
prompts/prompt-fixer.md. - Ask for approval at the end. One question, in the user's language. Add nothing after it.
Style profiles
Default: ste80 -> profiles/ste80.md.
Turkish requests default to turkish -> profiles/turkish.md.
ste80->profiles/ste80.mdplain->profiles/plain-english.md(general audiences, public sites)globish->profiles/globish.md(non-native readers)cte->profiles/cte-style.md(procedures, maintenance-style)turkish->profiles/turkish.md(Turkish requests)
Format ladder
See the full format ladder in prompts/prompt-fixer.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.