promptify
Skill0 starsChanged 10 months agoCC0-1.0View on GitHub
Transform user requests into detailed, precise prompts for AI models. Use when users say "promptify", "promptify this", or explicitly request prompt engineering or improvement of their request for better AI responses.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- tahabozdemir/promptifytheir own version, first seen Oct 8, 2026
- tolibear/promptify-skilltheir own version, first seen Jan 29, 2026
- tolimarchuk/promptify-skilltheir own version, first seen Jan 29, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- tolibear/promptify-skill★ 46same name
- tolimarchuk/promptify-skill★ 46same name
- tahabozdemir/promptify★ 0same 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.
In this repository20 other files it gives its agents.
- anki-connectSkill
- beautiful-mermaidSkill
- context7Skill
- copilot-sdkSkill
- gog-cliSkill
- gpt-image-1-5Skill
- here-be-gitSkill
- lorem-ipsumSkill
- markdown-converterSkill
- mgrep-code-searchSkill
- nano-banana-2Skill
- nano-banana-proSkill
- notion-apiSkill
- raindrop-apiSkill
- ray-so-code-snippetSkill
- tavilySkill
- todoist-apiSkill
- ultrathinkSkill
- upstash-redis-kvSkill
- youtube-transcriptSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 8 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Read and understand: - Read the user's request carefully to understand the full context, intent, and all details
- Distinctive: line 17
Plan the rewrite: - Consider what specific information, instructions, or context the AI model needs to fulfill the request effectively
- Distinctive: line 25
Use headings (##, ###, ####) for sections only where appropriate (no first-level title)
- Very specific: line 26
Use bold, _italics_, bullet points (-), and numbered lists (1., 2.) liberally for organisation
- Very specific: line 28
Never use * for bullet points, always use -
- Distinctive: line 32
Use plain, straightforward, precise language
- Distinctive: line 33
Avoid embellishments, niceties, or creative flourishes
- Distinctive: line 39
Keep the prompt concise: 0.75X to 1.5X the length of the original request
- Distinctive: line 40
Do not add or invent information not present in the input
- Distinctive: line 41
Do not include unnecessary complexity or verbosity
“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
Promptify
Transform user requests into detailed, precise prompts optimised for AI model consumption.
Core Task
Rewrite the user's request as a clear, specific, and complete prompt that guides an AI model to produce the desired output without ambiguity. Treat the output as specification language, not casual natural language.
Process
- Read and understand - Read the user's request carefully to understand the full context, intent, and all details
- Plan the rewrite - Consider what specific information, instructions, or context the AI model needs to fulfill the request effectively
- Rewrite as a detailed prompt - Transform the request into a precise prompt with clarity, specificity, and completeness
Writing Guidelines
Structure
- Begin with a single short paragraph summarising the overall task
- Use headings (##, ###, ####) for sections only where appropriate (no first-level title)
- Use bold, italics, bullet points (
-), and numbered lists (1., 2.) liberally for organisation - Never use emojis
- Never use
*for bullet points, always use-
Language
- Use plain, straightforward, precise language
- Avoid embellishments, niceties, or creative flourishes
- Think of language as specification/code, not natural language
- Be clear and specific in all instructions
Content
- Keep the prompt concise: 0.75X to 1.5X the length of the original request
- Do not add or invent information not present in the input
- Do not include unnecessary complexity or verbosity
Output
Provide only the final prompt as markdown, without additional commentary or explanation.
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.