Natural Language Editor

Rewrite user-provided text so it reads more naturally, clearly, and smoothly without changing the original meaning or factual content.

Use this skill when text feels stiff, robotic, repetitive, unclear, or overwritten and needs a cleaner human-sounding rewrite.

Quick Start

clawhub install natural-language-editor
text
edit Make this text sound more natural.
edit --concise Rewrite this so it is shorter but keeps the same meaning.
edit --professional Rewrite this email in a more polished professional tone.
Best For
Polishing drafts

Removing AI-like phrasing

Improving readability

Shortening text without losing meaning

Making writing sound more professional

Cleaning up technical or business writing

Quick Reference
If you need...	Use...
A natural rewrite	edit [text]
A shorter version with the same meaning	edit --concise [text]
Easier-to-read wording	edit --clarity [text]
A polished professional tone	edit --professional [text]
Minimal editing only	edit --light [text]
Stronger restructuring	edit --deep [text]
Structured export	edit --json [text]
When to Use
Use this skill when the user asks to:

make text sound more natural

remove robotic or AI-like phrasing

improve readability

rewrite without changing meaning

polish writing

shorten a draft without losing key points

make writing sound more professional

Modes
text
edit [text]
edit --concise [text]
edit --clarity [text]
edit --professional [text]
edit --light [text]
edit --deep [text]
edit --json [text]
If the user provides only text, use natural mode by default.

Intake
text
Text:             |
Mode:             | (natural / concise / clarity / professional / light / deep)
Audience:         | (general / technical / business / academic)
Keep terminology: | (yes / no)
Output:           | (text / json)
If the user provides only text, default to a natural rewrite.

Core Rules
text
1. Preserve meaning.
2. Do not add new facts.
3. Do not remove essential claims.
4. Do not add opinions, emotions, or personal experience unless already present.
5. Do not shift perspective unless the user asks.
6. Prefer direct, specific wording over generic phrasing.
7. Keep technical terms accurate when they matter.
Mode Behavior
Natural

text
Default mode.
Improve flow, readability, and natural phrasing with minimal meaning change.
Concise

text
Shorten the text.
Remove filler, redundancy, and weak transitions.
Clarity

text
Make complex writing easier to understand.
Break long sentences and reduce abstraction.
Professional

text
Use a clear, neutral, polished tone.
Remove casual, exaggerated, or promotional phrasing.
Light

text
Keep the original structure as much as possible.
Make only minimal edits for flow and readability.
Deep

text
Rewrite more aggressively for naturalness and readability.
Preserve meaning, but allow stronger restructuring.
Workflow
Step 1 — Analyze

Identify:

text
- repetition
- filler
- generic transitions
- inflated language
- vague abstractions
- tone mismatch
- mechanical sentence rhythm
Step 2 — Choose Strategy

Apply the minimum necessary rewrite:

text
- light polish
- concise compression
- clarity rewrite
- professional neutralization
- deep restructuring
Step 3 — Rewrite

Preserve:

text
- facts
- core meaning
- intended claims
- relevant terminology
- original perspective unless told otherwise
Step 4 — Validate

Check that the rewrite:

text
- adds no new facts
- introduces no new subjectivity
- does not distort the argument
- improves readability
Rewrite Heuristics
Prefer:

text
- concrete wording over vague abstractions
- direct sentences over padded ones
- natural transitions over template phrases
- varied rhythm over repetitive cadence
- clear wording over impressive-sounding fluff
Example:

text
Before: "This solution plays a crucial role in modern society."
After:  "This solution is widely used today."
Output
Default

text
[Rewritten text only]
JSON

json
{
  "issues_found": [
    "repetitive phrasing",
    "inflated language",
    "generic transitions"
  ],
  "rewrite_strategy": "simplify language and remove filler",
  "rewritten_text": "",
  "introduced_subjectivity": false
}
If the user only asks for a rewrite, return the rewritten text directly.

Limits
Do not:

add new facts

change the argument

invent experiences or emotions

insert opinions not present in the source

shift perspective unless requested

make legal, medical, or technical claims stronger than the source

Tips
Use --light when the draft is already good and only needs polish.

Use --deep when the text feels stiff or obviously AI-generated.

Use --clarity for technical explanations and guides.

Use --concise when the draft is too long but mostly correct.

Use --professional for emails, reports, and formal writing.

Keep specialist terminology when precision matters more than style.

Preserve uncertainty if the source text is uncertain.

Return only the rewrite unless the user asks for analysis.

Author
Vassiliy Lakhonin