CtrlK
BlogDocsLog inGet started
Tessl Logo

copy-editing

Improve existing copy for clarity, precision, tone, consistency, grammar, and conversion without changing its intended meaning.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./resources/bundled-skills/copy-editing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

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

The body is a well-structured, lean instruction skill with concrete tool routing, a clear sequenced workflow, and validation gates; its main weakness is the lack of illustrative edit examples and an explicit feedback loop.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence with no over-explanation of concepts, but the 'Purpose' section repeats the frontmatter description verbatim and the copyright line adds non-essential tokens, leaving minor trims below the lean-and-efficient anchor.

4 / 5

Actionability

Concrete, specific guidance for an instruction-only skill — a tool-routing table naming exact tools, rules like 'Make the lightest edit that solves each issue' and 'use the exact source hash' — with only minor gaps such as no before/after edit examples.

4 / 5

Workflow Clarity

The five-step workflow is clearly sequenced and the 'Completion gates' section provides validation checkpoints for the editing operation; it stops short of an explicit validate-fix-retry loop, so it is one notch below the full-checkpoint anchor.

4 / 5

Progressive Disclosure

At under 50 lines with no need for external references, the body is well-organized into clearly labeled sections (Tool routing, Workflow, Completion gates, Boundaries, Delivery), satisfying the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

61%Weight 40%Scale 1-5

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

The description is concise and specific about what the skill does, with strong natural trigger terms and a distinct niche, but it omits any explicit 'when to use' guidance, which caps completeness and limits its routing reliability.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when refining marketing copy, documentation, or UI text for clarity, tone, or conversion.'

Replace the single verb 'Improve' with two or three distinct actions (e.g. 'Revise, tighten, and proofread existing copy') to lift specificity above 3.

Include common user synonyms such as 'proofread', 'polish', or 'edit' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('existing copy') and enumerates concrete improvement dimensions (clarity, precision, tone, consistency, grammar, conversion), but relies on a single generic verb ('Improve') rather than multiple distinct actions, so it sits at the anchor for 'names domain and 1-2 concrete actions' rather than the level above.

3 / 5

Completeness

It clearly answers 'what' (improve copy across named dimensions) but contains no 'Use when...' clause or equivalent trigger guidance, which the rubric caps at 3 — the 'when' is only weakly implied.

3 / 5

Trigger Term Quality

Terms like 'copy', 'clarity', 'tone', 'grammar', 'consistency', and 'conversion' are natural phrases a user would say, giving good keyword coverage; common synonyms such as 'proofread', 'polish', or 'edit' are absent, keeping it just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

'Improve existing copy ... without changing its intended meaning' carves a clear copy-editing niche with mostly distinct triggers, with only minor overlap risk against general writing or proofreading skills.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
KunAgent/Kun
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.