Claude Skills for Writing: Voice, Drafting, and Review

Claude writing skills are reusable instruction files that define how Claude approaches a drafting task — the voice, the structure, the review criteria and the things to avoid. A good writing skill turns a vague request like "write a blog post" into a specific, repeatable brief that produces consistent results across sessions.

The challenge is finding which skills suit your work and keeping the approved instructions in one place. Tools like fenbs hold your tested writing skills and example outputs so every AI app you connect reads the same voice brief, not just the assistant that was open when you last worked on it.

What writing skills are good for

Writing skills work best for tasks you repeat on a regular cadence: weekly newsletters, product release notes, client updates, interview summaries. For a one-off piece, writing the setup inline is often faster. For the tenth time you draft the same type of content, a skill saves setup time and reduces variation between drafts. The skill defines the standard; each draft adds the specific.

They are not a substitute for a brief on the specific piece. A skill defines the defaults; the task brief provides the subject, the key points and the call to action for this particular draft. Keep the two separate so the skill stays reusable.

For a broader comparison of what skills can and cannot replace, see claude projects vs skills vs artifacts. For finding community writing skill collections, see the claude skills marketplace.

The three kinds of writing skills worth having

Most writing workflows need three types of skill: a voice skill, a drafting skill and a review skill. Each addresses a different stage of the writing process.

How to write a voice skill

A voice skill is the most valuable writing skill to get right. It is also the hardest to write, because voice is easier to recognize than to describe. Start with examples rather than adjectives. A reader can tell from a single paragraph whether an example matches; an adjective like "warm" or "authoritative" means something different to every person who reads it.

Paste three paragraphs of your best writing into the skill file, label them as approved examples and describe what makes them work. Then add the rules that emerge: "sentences stay under 20 words where possible", "use active voice", "avoid corporate nouns like 'solution' and 'leverage'". An example paired with a rule is harder to misread than a rule alone.

# Voice
Match this writing style when drafting or editing.

Approved examples:
[Paste 2-3 short paragraphs here]

Rules:
- Short sentences. No sentence over 25 words unless the complexity demands it.
- Active voice. Passive only when the subject is genuinely unknown.
- Second person. "You" not "users" or "clients".
- Avoid: leverage, solution, utilize, robust, seamless.
- Numbers under 10 are written out. Numbers 10 and above are numerals.

Not for: legal documents, formal reports or academic writing.

How to write a drafting skill

A drafting skill defines structure: what sections to include, what belongs in the opening paragraph and how to close. A good newsletter skill might say "open with a one-sentence observation, then the main point in three paragraphs, then a single resource link and a closing question." That is specific enough to reproduce a recognizable format each time.

Keep the drafting skill separate from the voice skill. That way you can pair a client-update structure with the formal voice for one audience and the same structure with the conversational voice for another, without duplicating the content of either skill.

How to write a review skill

A review skill is a checklist. It does not rewrite the draft; it asks whether the draft passes a set of tests. Useful questions include: Does the opening answer the reader's most likely question first? Does the draft contain any claim that needs a source but has none? Does the closing say what the reader should do next?

A review skill is most useful after a draft is structurally complete. Running it too early, while sections are still missing, produces a list of gaps rather than a useful final check.

Testing writing skills before you rely on them

Test each skill against a piece of writing you produced without it. Ask Claude to apply the skill to the raw material and compare the result to your original. If the skill produces something better, update your rules to capture what it did right. If it produces something worse, identify the instruction that caused the problem and rewrite it.

Three test cases is usually enough to decide whether a skill is reliable. Pick diverse inputs: a short piece, a longer one and one whose subject is unusual for your typical work. A skill that passes all three is worth keeping.

How to adapt a writing skill when your style changes

Voice evolves. The approved examples you saved six months ago may no longer represent your best work. When you notice that the output from a writing skill feels dated, the fix is to update the examples and rules rather than add a corrective layer on top of the old skill. Piling instructions on instructions usually produces inconsistent output.

Set a reminder to review writing skills once or twice a year, or after a deliberate brand or style shift. The review does not need to be extensive: read the first approved example in the voice skill and compare it to a recent piece you are proud of. If they feel different, update the example.

Keep the old version before overwriting it. Seeing the previous instructions alongside the new ones helps you articulate what changed and why. That note — "switched from third person to second person because the newsletter audience prefers direct address" — is more useful than an updated file with no explanation.

Update the version in your shared library at the same time. If teammates are using the same voice skill, an unannounced change to one person's local copy creates two diverging versions of the same standard. Communicate the update, say what changed and let people choose when to adopt the new version.

Combining skills for a complete writing workflow

A voice skill, a drafting skill and a review skill can be used in sequence on the same piece of writing. Use the drafting skill first to produce a structure, then apply the voice skill to refine the language, then run the review skill to check completeness before you publish.

This workflow works best when the three skills are consistent with each other. A drafting skill that produces five-sentence paragraphs and a voice skill that requires short sentences will conflict. Review the skills together, not just individually, before relying on all three in sequence.

When writing skills are not the right fit

A writing skill is not useful when the most important thing about the piece is entirely specific to that piece. A eulogy, a first-person essay about a personal experience or an urgent response to a specific criticism all need a bespoke brief. A skill would add constraints that get in the way more than they help.

fenbs does not generate writing or apply skills automatically. You invoke a skill explicitly when you start a task, and the writing happens in your AI app. fenbs holds the approved skill content and the decisions made during the drafting process, such as the agreed closing argument or the voice example you chose as the reference.

How to do this with fenbs

1. Create a free account and add a project for the publication or client this writing supports.
2. Write your voice, drafting and review skills as local files and test them. Once you are satisfied, add each skill's text to Skills and prompts in fenbs with a short note about its purpose.
3. Add approved writing examples as context notes linked to the project. These give your AI app a reference point for the voice without requiring you to paste them each time.
4. When you make a decision that applies to all writing in this project — "always use US English", "never quote competitors by name" — record it as a standing rule in Decisions and rules.
5. Connect your AI app over MCP from Integrations. It reads your approved skills, examples and rules at the start of each session so you can start drafting rather than briefing.