agentleFS
SNIKOSNIKO/agent-skills/skills/prompt-writer/SKILL.md

prompt-writer

Skill2 starsChanged 6 months agoMITView on GitHub

Use when creating, reviewing, or revising prompts, system prompts, developer instructions, agent policies, prompt templates, eval prompts, or skill files consumed by LLMs and AI agents. Routes to OpenAI, Anthropic/Claude, or generic prompt-writing guidance based on the target model/provider.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 5

    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
  1. Distinctive:

    Use this skill as a router.

    line 8
  2. Distinctive:

    Unknown, provider-neutral, mixed, or generic prompts: read references/generic.md.

    line 16
  3. Distinctive:

    If more than one provider applies, read each relevant provider reference and resolve conflicts in favor of the user's stated target.

    line 18
  4. Distinctive:

    Follow the selected reference's structure, rules, examples, output rules, and quality check.

    line 23
  5. Distinctive:

    Keep the user's intended behavior unless it conflicts with the user's current request or the selected reference.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 5 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

Prompt Writer

Use this skill as a router. Do not rely on this file for detailed prompting rules; load the appropriate reference before writing, reviewing, or revising the prompt.

Provider Selection

Infer the target provider from the user request, model names, product names, surrounding prompt context, or prompt target:

  • OpenAI: GPT, GPT-5.x, OpenAI, ChatGPT, Codex. Read references/openai.md.
  • Anthropic/Claude: Claude, Anthropic, Opus, Sonnet, Haiku. Read references/anthropic.md.
  • Unknown, provider-neutral, mixed, or generic prompts: read references/generic.md.

If more than one provider applies, read each relevant provider reference and resolve conflicts in favor of the user's stated target. If no target is stated, use the generic reference.

Required Workflow

  1. Select and read the proper reference file before producing the prompt artifact.
  2. Follow the selected reference's structure, rules, examples, output rules, and quality check.
  3. Keep the user's intended behavior unless it conflicts with the user's current request or the selected reference.
  4. Return the finished prompt first, with a short note only when it helps explain an important structure choice.

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.