CtrlK
BlogDocsLog inGet started
Tessl Logo

copy-editing

When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' 'sharpen the messaging,' 'refresh this content,' 'update this page,' 'this content is outdated,' or 'content audit.' Use this when the user already has copy and wants it improved or refreshed rather than rewritten from scratch. For writing new copy, see copywriting.

69

Quality

62%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/copy-editing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong description with excellent trigger term coverage and clear completeness, explicitly addressing both what the skill does and when to use it. The cross-reference to the copywriting skill is a notable strength for distinctiveness. The main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., grammar correction, tone adjustment, structural tightening) rather than relying on general verbs like 'edit, review, or improve.'

Suggestions

Add more specific concrete actions to the opening clause, e.g., 'Edits, tightens, proofreads, and restructures existing marketing copy—fixing tone, grammar, clarity, and messaging—and refreshes outdated content.'

DimensionReasoningScore

Specificity

The description names the domain (marketing copy editing) and some actions like 'edit, review, or improve existing marketing copy' and 'refresh outdated content,' but doesn't list multiple specific concrete actions (e.g., tighten headlines, fix tone inconsistencies, restructure paragraphs, correct grammar).

2 / 3

Completeness

Clearly answers both 'what' (edit, review, improve, refresh existing marketing copy) and 'when' (explicit 'Use when' clause with extensive trigger phrases, plus a boundary condition distinguishing it from writing new copy).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would actually say, including 'edit this copy,' 'proofread,' 'polish this,' 'too wordy,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'sharpen the messaging,' 'content audit,' and many more variations.

3 / 3

Distinctiveness Conflict Risk

Clearly distinguishes itself from a copywriting/new copy skill with the explicit boundary 'Use this when the user already has copy and wants it improved or refreshed rather than rewritten from scratch. For writing new copy, see copywriting.' This cross-reference significantly reduces conflict risk.

3 / 3

Total

11

/

12

Passed

Implementation

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides a comprehensive copy editing framework with good structural ideas (Seven Sweeps, Expert Panel Scoring) and useful concrete examples (vague vs. specific tables, before/after copy). However, it is far too verbose for a skill file — it reads more like a training manual than an efficient instruction set for Claude. The content would benefit enormously from aggressive condensation, pushing detailed sweep instructions and checklists to reference files, and eliminating explanations of concepts Claude already understands.

Suggestions

Reduce the main file to ~100 lines by condensing each sweep to 2-3 lines of key checks and moving detailed sweep instructions, examples, and checklists to a reference file like references/seven-sweeps-detail.md

Remove explanations of basic concepts Claude already knows: what passive voice is, what adverbs are, what nominalizations are, basic paragraph structure rules, etc.

Move the Expert Panel Scoring section, Common Copy Problems, and Quick-Pass Editing Checks to separate reference files, keeping only brief summaries with links in the main skill

Cut the redundant checklist section entirely — it repeats the sweep content verbatim in checkbox format

DimensionReasoningScore

Conciseness

This skill is extremely verbose at ~400+ lines. It explains concepts Claude already knows (what passive voice is, what adverbs are, basic editing principles), includes extensive checklists that repeat the sweep content, and provides lengthy explanations of obvious concepts like 'Good copy editing isn't about rewriting—it's about enhancing.' The philosophy section, key principles, and much of the sweep detail could be dramatically condensed.

1 / 3

Actionability

The skill provides concrete examples (vague vs. specific tables, before/after copy examples) and structured processes, but it's fundamentally a set of editorial guidelines rather than executable commands or code. The guidance is specific enough to act on (e.g., the word replacement tables, the 'so what' test examples) but much of it is descriptive rather than directly instructive, and the expert panel scoring is more of a conceptual framework than a concrete procedure.

2 / 3

Workflow Clarity

The Seven Sweeps framework provides a clear sequence, and each sweep has a process section with numbered steps. However, the validation/feedback loop mechanism (returning to previous sweeps after each new one) creates an exponentially growing review process that isn't practical — by Sweep 7, you're supposedly re-running all 6 previous sweeps. The 'iterate until all personas score 7+' checkpoint in expert panel scoring is a good validation gate, but the overall workflow is more theoretical than practically executable.

2 / 3

Progressive Disclosure

The skill does reference external files (references/plain-english-alternatives.md, references/content-refresh.md) and related skills, which is good progressive disclosure. However, the main file itself is a monolithic wall of content that should have much more pushed to reference files — the full seven sweeps detail, the expert panel section, the quick-pass checks, and the common problems section could each be separate references, with the main skill providing a concise overview.

2 / 3

Total

7

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (509 lines); consider splitting into references/ and linking

Warning

Total

10

/

11

Passed

Repository
coreyhaines31/marketingskills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.