copywriting

Write and rewrite marketing copy for landing pages, homepages, and ads. Useful as a copy chief partner during launches.

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/copywriting/SKILL.md

Quality

Content

47%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 concise, well-structured catalogue entry that cleanly points to an upstream bundle, but it offers little executable guidance — the core install step is left to the reader with only a repo URL. Workflow steps are present in rough form but poorly specified.

Suggestions

Replace the vague "install the upstream bundle" with a concrete, runnable command (e.g. a git clone / symlink / copy into the skills directory) so the user can act without inspecting the README.

Spell out the workflow as numbered steps with an explicit verification checkpoint (e.g. confirm the skill appears in the agent's skill list before invoking).

Drop the verbatim repetition of the frontmatter description in "What it does" or replace it with detail not already in the description to earn its tokens.

Dimension	Reasoning	Score
Conciseness	The body is lean with clear sections and no padding of concepts Claude already knows; the only over-explanation is restating the frontmatter description verbatim in "What it does". Matches the efficient-with-minor-trims anchor; not a 5 because of that redundancy.	4 / 5
Actionability	The only concrete command is the trivial `open https://…` to view a repo; the real instruction ("install the upstream bundle into your active agent's skills directory") gives no executable command or path. Matches the high-level-hints-without-specific-steps anchor; not a 3 because no executable installation step is provided.	2 / 5
Workflow Clarity	A rough sequence exists (inspect README → install bundle → invoke by name/trigger) but the steps are poorly defined with no concrete commands and "inspect the upstream README for exact paths" punts the detail. Not a 3 because the install/verify steps are undefined rather than merely lacking checkpoints.	2 / 5
Progressive Disclosure	A clean, well-organized overview with clearly signaled one-level-deep external reference (the upstream GitHub repo); no local bundle files exist to misstructure. Not a 5 because the body restates frontmatter content and the external reference is the sole depth rather than a deliberate split of detail.	4 / 5
	Total	12 / 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 clearly states what the skill does across concrete marketing surfaces but only weakly implies when to use it, lacking an explicit "Use when…" trigger clause. Keywords are natural and reasonably comprehensive, and the niche is largely distinct.

Suggestions

Add an explicit "Use when…" clause naming concrete triggers, e.g. "Use when the user asks to write or rewrite landing page, homepage, or ad copy, or needs a copy chief during a launch."

Expand trigger coverage with synonyms users say naturally (sales copy, hero copy, CTAs, taglines, PPC ad copy).

Tighten the "when" beyond "during launches" to also cover everyday copywriting requests so the trigger fires reliably.

Dimension	Reasoning	Score
Specificity	Names the marketing-copy domain and several concrete actions/surfaces — "Write and rewrite marketing copy for landing pages, homepages, and ads" — matching the anchor for several specific actions with minor coverage gaps. Not a 5 because it omits concrete actions like headline/CTA variants or A/B testing.	4 / 5
Completeness	Clear "what" (write/rewrite marketing copy across surfaces) but the "when" is only weakly implied by "Useful as a copy chief partner during launches" with no explicit "Use when…" clause. Per the guideline, a missing explicit trigger clause caps completeness at 3; it is not a 4 because the when is vague rather than explicitly stated.	3 / 5
Trigger Term Quality	Includes natural terms a user would say ("marketing copy", "landing pages", "homepages", "ads", "launches") but misses common synonyms (sales copy, hero copy, PPC, taglines). Good coverage with a few natural terms missing, matching the score-4 anchor.	4 / 5
Distinctiveness Conflict Risk	The marketing-copywriting niche is mostly distinct with trigger surfaces (landing pages, homepages, ads) that limit overlap. Not a 5 because it could still overlap with general writing, brand, or content-design skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/copywriting/SKILL.md
Commit: 1a7a23d

Reviewed: about 5 hours ago

Table of Contents

Discovery Implementation Validation

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.