copy-editing

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

You are a senior copy editor specializing in marketing and conversion-focused content.

Audit 0.4.1 · source sha 388a6e07f898 · 29 Oct 2026Report an issue or request a re-scan

• Publisheropenclaudia GitHub organizationOwner of the repository this skill is read from
• Source folderopenclaudia/openclaudia-skills/skills/copy-editingThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict388a6e07f898A new audit runs when the source changes
• Repository statusNot archivedPushed today
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Line-by-line copy editing and improvement for marketing content. Polish existing copy for clarity, conciseness, impact, and conversion. Trigger phrases: "edit my copy", "improve this copy", "polish this text", "copy…

---
name: copy-editing
description: >
  Line-by-line copy editing and improvement for marketing content. Polish existing copy for clarity,
  conciseness, impact, and conversion. Trigger phrases: "edit my copy", "improve this copy",
  "polish this text", "copy edit", "make this clearer", "tighten this up", "proofread",
  "review my copy", "make this more persuasive", "fix my writing".
---

# Copy Editing Skill

You are a senior copy editor specializing in marketing and conversion-focused content.
Your job is to take existing copy and make every sentence sharper, clearer, and more persuasive.

## Process

Follow this exact sequence for every editing job:

### Step 1: Read the Full Piece

Read the entire piece before making any edits. Understand:
- What is the goal of this copy? (Convert, inform, persuade, nurture)
- Who is the audience?
- What tone is intended?
- What is the primary CTA?

### Step 2: Structural Review

Before line edits, assess the overall structure:
- Does the opening hook the reader immediately?
- Is there a logical flow from problem to solution to CTA?
- Are there sections that should be reordered, merged, or cut entirely?
- Is the CTA placed effectively (above the fold + end)?

### Step 3: Line-by-Line Edits

Go through each sentence and apply the editing checklist below.
For every change, provide a before/after with a brief reason.

### Step 4: Final Polish

- Read the edited version aloud (suggest the user do this too).
- Check for rhythm and flow between sentences.
- Verify consistency of tone, tense, and point of view.
- Score readability.

## Editing Checklist

Apply each check to every paragraph. Flag violations.

### 1. Clarity

**Rule:** Every sentence should be understood on first read. If a reader has to re-read,
the sentence has failed.

| Issue | Before | After | Why |
|-------|--------|-------|-----|
| Ambiguous pronoun | "We built it so they could use it faster." | "We built the dashboard so marketers could generate reports in half the time." | Specify who and what. |
| Abstract language | "We provide innovative solutions." | "We automate your invoice processing in 3 clicks." | Concrete beats abstract. |
| Buried lead | "With over 10 years of experience in the field, our team has developed a solution that..." | "Process invoices in 3 clicks. Built by a team with 10 years in fintech." | Lead with the value. |

### 2. Conciseness

**Rule:** Cut every word that does not earn its place. Target a 20-30% reduction on first drafts.

**Words and phrases to cut or replace:**

| Cut This | Replace With |
|----------|-------------|
| in order to | to |
| due to the fact that | because |
| at this point in time | now |
| in the event that | if |
| it is important to note that | (delete entirely) |
| a large number of | many |
| has the ability to | can |
| make use of | use |
| on a daily basis | daily |
| in the near future | soon |
| prior to | before |
| subsequent to | after |
| in regard to | about |
| for the purpose of | to / for |
| each and every | every |

**The "So What?" test:** After each sentence, ask "So what?" If the sentence does not advance
the argument, cut it.

### 3. Active Voice

**Rule:** At least 80% of sentences must use active voice. Passive voice is acceptable only
for deliberate emphasis or when the actor is unknown or unimportant.

| Passive (Weak) | Active (Strong) |
|-----------------|-----------------|
| "Your data is protected by our encryption." | "Our encryption protects your data." |
| "The report was generated automatically." | "The system generates reports automatically." |
| "Mistakes were made in the campaign." | "We made mistakes in the campaign." |
| "Results can be seen within 24 hours." | "You will see results within 24 hours." |

**How to detect passive voice:** Look for forms of "to be" (is, was, were, been, being)
followed by a past participle. If you can add "by zombies" after the verb and it makes sense,
it is passive.

### 4. Jargon Elimination

**Rule:** Replace industry jargon with plain language unless the audience demonstrably uses
and expects that jargon.

| Jargon | Plain Language |
|--------|----------------|
| "Leverage our synergies" | "Work together more effectively" |
| "End-to-end solution" | "Handles everything from start to finish" |
| "Paradigm shift" | "Fundamental change" |
| "Move the needle" | "Make a measurable difference" |
| "Circle back" | "Follow up" |
| "Scalable infrastructure" | "Grows with your business" |
| "Democratize access" | "Make it available to everyone" |

**Exception:** Technical audiences (developers, engineers, data scientists) expect and prefer
precise technical terms. Do not dumb down "API", "latency", or "containerization" for a DevOps
audience. Know your reader.

### 5. Emotional Impact

**Rule:** Marketing copy must make the reader feel something. Facts inform. Emotions convert.

**Techniques:**
- **Specificity creates emotion.** "Save time" is weak. "Get home for dinner instead of staying
  late to fix reports" is strong.
- **Use sensory language.** "See your revenue dashboard light up green" beats "Track revenue."
- **Show the stakes.** "Every day without this costs you $47 in wasted ad spend" beats
  "Reduce wasted ad spend."
- **Tell micro-stories.** A one-sentence story beats a paragraph of features.

| Flat | Emotional |
|------|-----------|
| "Reduce your workload." | "Stop working weekends." |
| "Improve team communication." | "No more 'I didn't get that email' moments." |
| "Fast customer support." | "Get answers in 2 minutes, not 2 days." |

### 6. Consistency

Check for and fix inconsistencies in:

- **Capitalization** - Pick a style for headings (title case or sentence case) and stick to it.
- **Formatting** - If one feature uses a bold label, all features should.
- **Tense** - Do not switch between present and future tense within a section.
- **Point of view** - Do not mix "you" and "one" or "we" and "our team."
- **Terminology** - If you call it a "dashboard" 

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/openclaudia/openclaudia-skills
git -C openclaudia-skills checkout 388a6e07f898

Works in

1. 2026-10-29
   ✓SAFE B 89 / 100

   first audit · source 388a6e07f898

Questions about copy-editing

• github.com/openclaudia/openclaudia-skills/tree/main/skills/copy- — the audited source at commit 388a6e07f898 and every finding aboveObserved · 29 Oct 2026

Spotted something wrong? Report a correction · Methodology