CtrlK
BlogDocsLog inGet started
Tessl Logo

copy-editing

When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' This skill provides a systematic approach to editing marketing copy through multiple focused passes.

56

Quality

64%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

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

Quality

Discovery

82%

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 solid description with excellent trigger term coverage and clear completeness, explicitly stating both what the skill does and when to use it. Its main weaknesses are the somewhat vague capability description (lacks specific concrete editing actions) and moderate conflict risk with general editing/proofreading skills due to some generic trigger terms.

Suggestions

Add more specific concrete actions to improve specificity, e.g., 'Checks tone consistency, tightens headlines, strengthens CTAs, eliminates jargon, and ensures brand voice alignment.'

Consider narrowing some generic triggers like 'make this better' or 'proofread' by qualifying them with 'marketing' context to reduce conflict risk with general writing/editing skills.

DimensionReasoningScore

Specificity

The description mentions 'editing marketing copy through multiple focused passes' and lists actions like 'edit, review, or improve,' but doesn't specify concrete actions like 'fix grammar, tighten headlines, improve CTAs, check brand voice consistency.' The actions remain somewhat general.

2 / 3

Completeness

Clearly answers both 'what' (systematic approach to editing marketing copy through multiple focused passes) and 'when' (explicit 'Use when' clause with multiple trigger phrases and scenarios).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would actually say: 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep.' These are highly natural phrases a user would use.

3 / 3

Distinctiveness Conflict Risk

The focus on 'marketing copy editing' is fairly specific, but terms like 'proofread,' 'make this better,' and 'polish this' are generic enough to potentially conflict with general writing/editing skills. The 'marketing copy' qualifier helps but doesn't fully prevent overlap.

2 / 3

Total

10

/

12

Passed

Implementation

47%

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

This skill has a well-designed workflow structure (the Seven Sweeps Framework) with clear sequencing and built-in feedback loops, and includes useful concrete examples like the vague-to-specific tables. However, it is far too verbose—much of the content explains concepts Claude already understands, and there is significant duplication between the sweeps, checklist, and common problems sections. The content would benefit greatly from aggressive condensation and splitting detailed reference material into separate files.

Suggestions

Condense each sweep to 3-5 lines max: the focus question, a few bullet points of what to check, and one concrete example—move detailed explanations to a separate SWEEPS-DETAIL.md file.

Remove the checklist section entirely as it duplicates the sweeps content, or replace the sweeps detail with just the checklist.

Cut explanatory text that describes concepts Claude already knows (e.g., what clarity means, what voice consistency is, what emotional writing looks like) and focus only on the specific editorial standards and examples unique to this framework.

Move the 'Common Copy Problems & Fixes' and 'Quick-Pass Editing Checks' sections to separate referenced files to reduce the main skill to a concise overview with clear navigation.

DimensionReasoningScore

Conciseness

This skill is extremely verbose at ~350+ lines. It over-explains concepts Claude already understands (what clarity means, what voice consistency is, what emotion in copy looks like). The seven sweeps framework, while structured, repeats patterns extensively (each sweep has nearly identical process steps and 'return to previous sweeps' instructions). The checklist section largely duplicates the sweeps content. Much of this could be condensed to 30-40% of its current length.

1 / 3

Actionability

The skill provides concrete examples (vague vs. specific tables, before/after copy examples, word replacement lists) which are genuinely useful. However, it's an instruction-only skill with no executable code, and many directives remain somewhat abstract ('read aloud to hear inconsistencies,' 'paint the before state vividly'). The checklist and common problems sections add actionable guidance but could be more specific.

2 / 3

Workflow Clarity

The seven sweeps framework provides a clear sequential workflow with explicit ordering, and each sweep includes a process section with numbered steps. The feedback loop requirement (return to previous sweeps after each new sweep) is explicitly stated and reinforced. The collaborative editing section adds a clear iterative process. Validation is built into the framework through the re-checking mechanism.

3 / 3

Progressive Disclosure

The skill references one external file (references/plain-english-alternatives.md) and links to related skills, which is good structure. However, the massive amount of inline content (all seven sweeps fully detailed, plus quick-pass checks, plus checklist, plus common problems) should be split into separate files. The checklist and common problems sections could easily be referenced rather than inlined, significantly reducing the main file's length.

2 / 3

Total

8

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
freekmurze/dotfiles
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.