When to use it

Use natural-writing for blog posts, articles, newsletters, or other multi-paragraph text. Give it a draft or a purpose and audience, plus writing samples if you want it to match your established voice.

How it works

Figure 01

Improve the reading without changing the meaning.

  1. Establish

    Identify the audience, purpose, and author’s voice.

  2. Revise

    Improve wording, structure, and flow.

  3. Preserve

    Keep facts, quotations, uncertainty, and caveats intact.

ResultA draft or revision in the author’s voice
The diagram summarizes the editing process. A clearer sentence should not quietly become a stronger or different factual claim.

The skill follows the author’s voice when one is supplied, or uses a plainspoken style otherwise. It edits phrasing and flow while preserving facts, actors, quotations, uncertainty, and caveats.

A revision should make the argument easier to follow without quietly making the claims stronger. An optional visual revision report can help compare versions, but it is generated only when explicitly requested and must reconstruct both full texts accurately.

An example request

Ask your agent

“Revise this project introduction for engineers who have never used the tool. Keep the example and limitations, explain unfamiliar terms, and follow the voice in my previous post.”

This illustrates a request you can adapt; it is not a transcript of a completed run.

A draft or revision that reads coherently for its intended audience and retains the important meaning of the source material.

Install and use

The skill’s identifier is natural-writing. It ships in the natural-writing plugin. In Claude Code, first add the Overclock marketplace, then install the package:

/plugin install natural-writing@overclock

For a standalone installation, keep the skill directory and its bundled resources together. The repository also includes per-skill Codex metadata. Read the full skill instructions for its exact workflow and supporting files.

What to keep in mind

A style revision does not establish that a claim is true. Supply reliable source material and review any factual changes.

This skill is for substantial prose. It stays out of code, commit messages, UI microcopy, and one-line edits.

  • Critical thinking — Test a proposal’s assumptions before accepting its conclusion.
  • Project vocabulary — Keep the meaning of your project’s terms consistent as the code and team evolve.