agentleFS
Sign inStart free
hmbseaotterhmbseaotter/meta-prompt-toolkit/SKILL.md

meta-prompt

Skill0 starsChanged 4 months agoMITView on GitHub

Use when the user wants help writing, generating, or improving a prompt for an LLM - e.g. "write me a prompt for...", "turn this into a prompt", "help me prompt for...", "improve this prompt", or when they hand over a use case and want a polished, reusable prompt back. Produces a finished, copy-ready prompt (not advice about prompting). Also applies when the user references the CoSTAR framework or asks for a prompt built to a named structure.

5 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. Mindrally/skills★ 275same name
    2. Haochenhust/ch-skills★ 9same name
    3. naticorrea-03/claude-code-skills★ 4same name
    4. GlamgarOnDiscord/claude-saas-blueprint★ 2same name
    5. mizukaizen/hive-doctrine-skills★ 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.

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read core/meta-prompt-core.md and follow its steps - it is the engine and it governs.

    line 13
  2. Very specific:

    If unsure what the finished output should look like, read examples/worked-example.md.

    line 21
  3. Very specific:

    If the user is building a multi-step working session, agent, or skill - not just a one-shot prompt - also offer the rules in …

    line 23
  4. Distinctive:

    Never guess silently: Ask up to 3 focused questions, or state a labeled "Assumption:".

    line 28
  5. Distinctive:

    When a decision is needed, present it as a short list, recommended option first with a one-line reason and trade-offs, and leave room for …

    line 37

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Meta-Prompt Skill

Turn a USE CASE into ONE finished, copy-ready prompt, or improve an existing prompt. Deliver an actual prompt, not general advice.

How to run

  1. Read core/meta-prompt-core.md and follow its steps - it is the engine and it governs.
  2. Apply the branch file for the model the user will RUN the prompt on - not the model you are:
    • Claude (the default here) -> branches/anthropic.md
    • Gemini -> branches/gemini.md
    • ChatGPT / GPT -> branches/chatgpt.md Branches override the core where they conflict; they exist because the vendors genuinely disagree (on roles, sampling parameters, repetition, and chain-of-thought). If the user hasn't said which model, ask - it changes the output.
  3. If unsure what the finished output should look like, read examples/worked-example.md. It shows one full USE CASE pass and one IMPROVE pass.
  4. If the user is building a multi-step working session, agent, or skill - not just a one-shot prompt - also offer the rules in guardrails/collaboration-rules.md.

The two non-negotiables

  • Never guess silently. Ask up to 3 focused questions, or state a labeled "Assumption:".
  • Deliver a prompt, not advice. THE PROMPT in one code block, then WHY IT WORKS, SETTINGS, HOW TO IMPROVE.

Everything else - the four essentials, technique selection, the optional blocks - lives in the core file. Follow it there rather than from memory.

Presenting choices to the user

When a decision is needed, present it as a short list, recommended option first with a one-line reason and trade-offs, and leave room for the user to choose otherwise. Don't bury questions in prose.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free