Writing Claude 5 Prompts Agent Skill

Use when writing, rewriting, reviewing, shortening, or handing off prompts, system prompts, agent briefs, skills, CLAUDE.md files, or task…

Context cost
10.7k tokensestimated from the bundle, loaded when it triggers
Bundle
12 files · 44.4 kB1 script among them — read before you run
Licence
MITthe author’s own terms
Last change
—no release on file
Servers it uses
Noneruns standalone

What it does

Use when writing, rewriting, reviewing, shortening, or handing off prompts, system prompts, agent briefs, skills, CLAUDE.md files, or task specifications targeting Opus 5 or Fable 5 — including when a prompt was tuned for an older model, has grown repetitive or over-scaffolded, or is unclear about scope, autonomy, evidence, output length, or stopping. Not for prompts whose primary result is a visual artefact; writing-claude-design-prompts owns those.

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

agentproductivitywriting

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md8.0 kB · preview
--- name: writing-claude-5-prompts ---
6# Writing Claude 5 Prompts
7
8## Principle
9
10Write the smallest prompt that preserves the contract. These models infer intent and choose method well; specify the destination, the boundaries, the evidence, the output and the finish line, and prescribe the route only when the route itself is the requirement.
11
12The failure mode with this generation is not vagueness. It is accumulated scaffolding — rules written for weaker models that now fight the model's own judgement, and duplicated instructions across system prompt, project file and skill that cost reasoning to reconcile.
13
14**The keep/cut test for any rule:** does it correct a *measured default behaviour of this model*, or does it guard against a failure this model no longer has? Keep the first. Cut the second.
15
16## Method
17
18### 1. Fix the target
19
20Establish which model, which surface (API, Claude Code, skill, project file), and whether the prompt takes actions or only advises. If the target model isn't stated, ask — the two models pull in opposite directions on verbosity, verification and effort.
21
22If the prompt's primary result is a visual artefact — a design, frontend, redesign, prototype, design system or image-to-code implementation — hand composition to writing-claude-design-prompts. That skill writes a creative commission rather than the goal contract in step 3, and its framing supersedes this one. Steps 2, 4 and 5 here still apply: the deletion pass, the model levers and the effort knob are model-level and hold whatever the prompt is for.
23
24If the prompt touches offensive security or life sciences and the target is Fable 5, flag it in your response and recommend routing that work to Opus instead. Those domains hit Fable's safety classifiers and return stop_reason: "refusal" — even for benign work — and no prompt wording avoids that; the fix is configured fallback (to Opus 4.8), which is a harness change, not yours to write into the prompt.
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md1,246 words
Files12
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈130
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
10,520
on trigger
The instruction body and 11 supporting files, read only when the skill fires.
5.3%
of a 200k window
Ten skills this size would take about 53% of the window before you open a file.
050k100k150k200k context window

10.7k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

12 files, 44.4 kB on disk. Mostly text — the instructions the model reads — with 1 script in it that your client would run only if the instructions tell it to. 1 file of its source is not in the download — listed after these, with why.

  • SKILL.md8.0 kB
  • CONTRIBUTING.md0.6 kB
  • LICENSE1.1 kB
  • README.md5.5 kB
  • SECURITY.md0.4 kB
  • references/context-engineering.md5.6 kB
  • references/discovering-unknowns.md3.9 kB

Not in the download

Not carried is a type a skill download does not hold. Take it from its source.

  • .gitignorenot carried
What is not in it

A skill installs nothing and depends on nothing: it is a folder your client reads. This one carries 1 script beside the text, so the download is 12 files — not the whole of its source: 1 file is left out. It is listed under the files, with why. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Writing Claude 5 Prompts · 10.7k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/writing-claude-5-prompts/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/writing-claude-5-prompts" ] && { [ ! -e .claude/skills/writing-claude-5-prompts ] || { mv .claude/skills/writing-claude-5-prompts "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/writing-claude-5-prompts" .claude/skills/ && echo "Installed .claude/skills/writing-claude-5-prompts"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add codingcossack/writing-claude-5-prompts

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/writing-claude-5-prompts/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/writing-claude-5-prompts/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/writing-claude-5-prompts" ] && { [ ! -e ~/.claude/skills/writing-claude-5-prompts ] || { mv ~/.claude/skills/writing-claude-5-prompts "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/writing-claude-5-prompts" ~/.claude/skills/ && echo "Installed ~/.claude/skills/writing-claude-5-prompts" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/writing-claude-5-prompts/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. Not in this download: 1 file of its source (which one, and why). Take it from its source.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referencecodingcossack/writing-claude-5-prompts

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers0
Claim this skill