Back to Skills

copy-editor

verified

Review and edit copy for grammar, style, and clarity. Works with project style guides or uses sensible defaults. Use when reviewing marketing copy, blog posts, documentation, emails, or any business writing that needs polish.

View on GitHub

Marketplace

majestic-marketplace

majesticlabs-dev/majestic-marketplace

Plugin

majestic-marketing

Repository

majesticlabs-dev/majestic-marketplace
19stars

plugins/majestic-marketing/skills/copy-editor/SKILL.md

Last Verified

January 24, 2026

Install Skill

Select agents to install to:

Scope:
npx add-skill https://github.com/majesticlabs-dev/majestic-marketplace/blob/main/plugins/majestic-marketing/skills/copy-editor/SKILL.md -a claude-code --skill copy-editor

Installation paths:

Claude
.claude/skills/copy-editor/
Powered by add-skill CLI

Instructions

# Copy Editor

A general-purpose copy editing skill that reviews and edits text for grammar, style, and clarity. Supports custom project style guides with a comprehensive default fallback.

## When to Use

- Reviewing marketing copy, landing pages, or ad text
- Editing blog posts, articles, or thought leadership pieces
- Polishing documentation or technical writing
- Improving email campaigns or newsletters
- Refining product descriptions or UI text
- Any business writing that needs professional polish

## Methodology

Follow these four phases sequentially for thorough copy review.

### Phase 1: Context Analysis

Before editing, understand the document:

1. **Document Type**: Marketing copy, blog post, documentation, email, etc.
2. **Target Audience**: Technical, general, executive, customer-facing
3. **Intended Tone**: Formal, conversational, persuasive, informative
4. **Purpose**: Inform, persuade, instruct, engage

Note these factors as they influence which style rules apply. Marketing copy allows more creative freedom than documentation.

### Phase 2: Style Guide Resolution

Locate the applicable style guide in this order:

1. **Project root**: Check for `STYLE_GUIDE.md`
2. **Claude directory**: Check for `.claude/style-guide.md`
3. **Docs folder**: Check for `docs/style-guide.md`
4. **Default fallback**: Use `references/DEFAULT_STYLE_GUIDE.md` from this skill

```bash
# Search for project style guide
glob "STYLE_GUIDE.md" || glob ".claude/style-guide.md" || glob "docs/style-guide.md"
```

If a project style guide exists, prioritize its rules. The default guide provides universal best practices for cases not covered.

### Phase 3: Line-by-Line Review

Systematically review the copy for:

**Grammar & Mechanics**
- Subject-verb agreement
- Punctuation (commas, semicolons, apostrophes)
- Capitalization consistency
- Number formatting
- Spelling and typos

**Voice & Clarity**
- Active vs. passive voice (prefer active)
- Sentence length and readability
- Jargon and u

Validation Details

Front Matter
Required Fields
Valid Name Format
Valid Description
Has Sections
Allowed Tools
Instruction Length:
5500 chars