CtrlK
BlogDocsLog inGet started
Tessl Logo

copywriting

Write original product, landing-page, email, announcement, and campaign copy from a verified brief.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

86%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 tight, well-organized instruction skill with a concrete brief checklist and explicit completion gates; its main gap is that some workflow steps remain directional rather than fully actionable and there is no feedback loop from a failed gate.

DimensionReasoningScore

Conciseness

The body is lean and sectioned (Purpose, Tool routing, Workflow, Completion gates, Boundaries, Delivery) with no padding or explanation of concepts Claude already knows; every section earns its place.

5 / 5

Actionability

The workflow gives a concrete brief checklist (audience, problem, promise, proof, objection, action, channel, constraints) and named tools, but steps like "Draft the structural hierarchy before polishing lines" stay high-level rather than fully executable.

4 / 5

Workflow Clarity

The numbered 1-5 workflow is clearly sequenced and the Completion gates provide explicit verification checkpoints, but there is no error-recovery/feedback loop tying a failed gate back to a re-draft step.

4 / 5

Progressive Disclosure

At ~33 lines with no bundle files and no need for external references, the well-organized section structure satisfies the simple-skill exception for a top progressive-disclosure score.

5 / 5

Total

18

/

20

Passed

Description

66%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 third-person, concrete, and covers a broad range of copy deliverables, but it omits any explicit "Use when..." trigger guidance, which caps its completeness and limits how reliably Claude will select it.

Suggestions

Add a "Use when..." clause naming the natural trigger phrases users would say (e.g., write landing-page copy, draft a launch email, campaign copy from a brief).

Include a few common synonyms (ad copy, sales copy, marketing copy) to broaden trigger-term coverage.

Tie the trigger to the "verified brief" precondition so the skill is selected only when a brief exists or is being built.

DimensionReasoningScore

Specificity

"Write original product, landing-page, email, announcement, and campaign copy from a verified brief" names five concrete deliverable types plus a concrete source (a verified brief); not a 5 because the action is a single verb rather than multiple distinct operations.

4 / 5

Completeness

The what is clear (write original copy from a verified brief) but there is no "Use when..." or equivalent trigger clause, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Natural user terms are present (product copy, landing-page, email, announcement, campaign, brief), but common synonyms like ad copy, sales copy, marketing copy, or tagline are missing.

4 / 5

Distinctiveness Conflict Risk

The copywriting-from-a-verified-brief niche is mostly distinct with clear triggers; minor overlap risk with general writing or marketing-adjacent skills keeps it below 5.

4 / 5

Total

15

/

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.