copywriting

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

Quality

50%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

40%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 tidy catalog stub that honestly explains its role and how to reach the upstream material, but as a skill it provides almost no executable guidance: the install step has no command, the sole code block is a comment plus an 'open' URL, and all real copywriting content is deferred to an external repo. It reads as an advertisement rather than an operational skill file.

Suggestions

Replace the 'open' URL block with the actual install steps (e.g., a git clone or copy command plus the target skills-directory path) so the setup sequence is executable end-to-end.

Add a verification checkpoint after install, such as confirming the 'copywriting' skill is discoverable or invocable before telling the user to invoke it.

Trim the duplication: drop the verbatim 'What it does' restatement and the 'Source' section's repeat of the frontmatter upstream/category, keeping only the install-and-invoke instructions.

Dimension	Reasoning	Score
Conciseness	The body is short and free of concept over-explanation, but it pads with duplication: 'What it does' repeats the frontmatter description verbatim and 'Source' restates the upstream URL and category already in the frontmatter. It fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the lean anchor above.	3 / 5
Actionability	Concrete guidance is minimal: the only command is 'open https://github.com/coreyhaines31/marketingskills' plus the comment 'Inspect the upstream README for exact paths', and the key step — 'install the upstream bundle into your active agent's skills directory' — is given with no install command or steps. This matches 'minimal concrete guidance; high-level hints but missing the specific steps to execute' rather than anchor 3, because the actionable core is deferred rather than merely incomplete.	2 / 5
Workflow Clarity	A rough sequence exists (open upstream repo, install the bundle, invoke by name or trigger phrase), but the critical install step is undefined and there are no checkpoints or verification (e.g., confirming the skill is installed and invocable). This fits 'rough sequence present but many gaps; steps poorly defined' rather than anchor 3, where steps would at least all be listed.	2 / 5
Progressive Disclosure	No references/, scripts/, or assets/ directories exist in the bundle, and the body is a short, well-sectioned overview (What it does / Source / How to use) that clearly signals its single one-level-deep pointer to the upstream repo. It earns good structure with a minor gap — the actual workflow content lives entirely outside the skill at an external URL rather than in bundled files — keeping it below the clear-overview-with-local-references ideal.	4 / 5
	Total	11 / 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 delivers a clear, third-person statement of what the skill does with reasonably natural trigger vocabulary, but it omits any explicit 'Use when...' guidance, capping completeness at the midpoint. It is a serviceable description that would benefit most from an explicit trigger clause and a slightly broader action vocabulary.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to write or rewrite copy for a landing page, homepage, ad, or launch material.'

Broaden the action vocabulary beyond 'write and rewrite' to cover concrete deliverables users ask for (e.g., headline variants, hero sections, CTAs, A/B copy variations).

Include a few missing natural synonyms such as 'website copy', 'sales page copy', or 'product copy' in the description or triggers list.

Dimension	Reasoning	Score
Specificity	The description names the domain and two concrete actions — 'Write and rewrite marketing copy' — across three targets ('landing pages, homepages, and ads'), but the action set is not comprehensive (no drafting variations, testing, editing, or refinement steps). It fits the 'names domain and 1-2 concrete actions' anchor better than the 'several specific actions' anchor above.	3 / 5
Completeness	The 'what' is clear ('Write and rewrite marketing copy for landing pages, homepages, and ads') but there is no 'Use when...' clause or equivalent explicit trigger guidance; 'Useful as a copy chief partner during launches' only weakly implies when. Per the rubric, a missing 'Use when' clause caps completeness at 3, and the score cannot be 4 since the when is absent rather than merely under-specified.	3 / 5
Trigger Term Quality	Natural terms are present — 'marketing copy', 'landing pages', 'homepages', 'ads' in the description plus frontmatter triggers like 'landing copy', 'ad copy', 'homepage copy', 'rewrite copy' that users would genuinely say. A few common variations are missing (e.g., 'website copy', 'sales page copy', 'product copy'), keeping it below the comprehensive-coverage anchor.	4 / 5
Distinctiveness Conflict Risk	'Marketing copy for landing pages, homepages, and ads' carves out a mostly distinct niche, though it has minor overlap risk with general writing, editing, and brand-voice skills. It sits between the 'somewhat specific but could overlap' (3) and 'clear niche with minimal conflict' (5) anchors, noticeably above the midpoint.	4 / 5
	Total	14 / 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: 1b47e60

Reviewed: 3 days 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.