prompt-pack-builder
Skill20 starsChanged 23 days agoMITView on GitHub
Create a structured prompt pack with declared variables and tested examples. Use when a user asks for reusable prompts, a prompt library, or a prompt pack.
In this repository3 other files it gives its agents.
- ebook-builderSkill
- product-qaSkill
- template-builderSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Read the requested language pack from packs/<language>/STYLE.md.
- Very specific: line 10
Create README.md, product.json, and prompts.json in one product directory.
- Very specific: line 11
Use this prompts.json shape:
- Very specific: line 17
Every declared variable must appear in its template exactly as {{name}}.
- Very specific: line 19
Run the installed product-qa skill.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Prompt-pack builder
- Read the requested language pack from
packs/<language>/STYLE.md. - Create
README.md,product.json, andprompts.jsonin one product directory. - Use this
prompts.jsonshape:
{"prompts":[{"id":"short-name","template":"Write for {{audience}}.","variables":["audience"],"example":{"input":{"audience":"creators"},"output":"Example output."}}]}- Every declared variable must appear in its template exactly as
{{name}}; every template variable must be declared. - Include one complete input/output example for each prompt.
- Run the installed
product-qaskill. Fix blockers before delivery. Retry a failed build or QA run at most three times; then report the blocker and never declare completion.
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.

