How do I install the Copy Editor skill?

Run npx skillmds@latest add furkangonel/copy-editor in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Copy Editor skill do?

Polish any text — grammar, flow, and clarity — without breaking the author's original voice It is listed under Coding & Dev Tools on SkillMD.

Is Copy Editor safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Copy Editor?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Copy Editor free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Copy Editor?

furkangonel (@furkangonel) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Copy Editor by furkangonel — Agent Skill

Name: Copy Editor
Author: furkangonel

File contents

Copy Editor Skill

Goal

Transform rough or error-prone text into clean, fluent prose — fixing grammar, spelling, punctuation, and flow — while preserving the author's unique voice, terminology, and intent. Never rewrite so heavily that the result sounds like someone else.

Principles

Voice preservation: Match the author's register (formal/casual, Turkish/English, technical/plain). Don't homogenize.
Minimal intervention: Fix what's broken. Don't change what works. If a sentence is already good, leave it.
Explain changes: After the edit, briefly note the most significant corrections (grammar rule, clarity issue, etc.) so the user learns.
Preserve meaning: Never change meaning to improve style. Flag ambiguities instead of silently resolving them.

Steps

1. Assess the text

Read the full text before touching anything. Identify:

Language (Turkish, English, mixed)
Register (academic, casual, professional, technical)
Recurring patterns vs. one-off errors

Success criteria: You understand the author's intent and voice before editing.

2. Edit in passes

Make two passes:

Structural pass: Fix sentence fragments, run-ons, unclear pronoun references, paragraph flow
Surface pass: Spelling, punctuation, subject-verb agreement, tense consistency, word choice

Success criteria: Output reads naturally at first read-through.

3. Deliver with annotations

Return the edited version in a code block or quoted block, then add a Changes section:

List the 3–5 most important corrections with a one-line explanation each
If you changed nothing (text was already clean), say so explicitly

Success criteria: User understands why each major change was made.

4. Offer alternatives (optional)

If a sentence could be fixed multiple ways, offer 2 options: the conservative fix and a more fluent rewrite. Let the user choose.

Why/Failure Modes

[TODO: Explain the reasoning behind this skill's approach and common failure modes to avoid.]

Standalone vs Supercharged

[TODO: Describe how this skill works on its own vs when combined with other tools/context.]

Cross-References

[TODO: Link to other relevant skills or documentation.]

---name: copy-editordescription: Polish any text — grammar, flow, and clarity — without breaking the author's original voice---# Copy Editor Skill## GoalTransform rough or error-prone text into clean, fluent prose — fixing grammar, spelling, punctuation, and flow — while preserving the author's unique voice, terminology, and intent. Never rewrite so heavily that the result sounds like someone else.## Principles- **Voice preservation**: Match the author's register (formal/casual, Turkish/English, technical/plain). Don't homogenize.- **Minimal intervention**: Fix what's broken. Don't change what works. If a sentence is already good, leave it.- **Explain changes**: After the edit, briefly note the most significant corrections (grammar rule, clarity issue, etc.) so the user learns.- **Preserve meaning**: Never change meaning to improve style. Flag ambiguities instead of silently resolving them.## Steps### 1. Assess the textRead the full text before touching anything. Identify:- Language (Turkish, English, mixed)- Register (academic, casual, professional, technical)- Recurring patterns vs. one-off errors**Success criteria**: You understand the author's intent and voice before editing.### 2. Edit in passesMake two passes:1. **Structural pass**: Fix sentence fragments, run-ons, unclear pronoun references, paragraph flow2. **Surface pass**: Spelling, punctuation, subject-verb agreement, tense consistency, word choice**Success criteria**: Output reads naturally at first read-through.### 3. Deliver with annotationsReturn the edited version in a code block or quoted block, then add a **Changes** section:- List the 3–5 most important corrections with a one-line explanation each- If you changed nothing (text was already clean), say so explicitly**Success criteria**: User understands why each major change was made.### 4. Offer alternatives (optional)If a sentence could be fixed multiple ways, offer 2 options: the conservative fix and a more fluent rewrite. Let the user choose.## Why/Failure Modes[TODO: Explain the reasoning behind this skill's approach and common failure modes to avoid.]## Standalone vs Supercharged[TODO: Describe how this skill works on its own vs when combined with other tools/context.]## Cross-References[TODO: Link to other relevant skills or documentation.]

Frequently asked questions

Copy Editor