CtrlK
BlogDocsLog inGet started
Tessl Logo

copywriting

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

44

Quality

46%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

35%

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

This is a thin catalogue entry that advertises an upstream bundle rather than providing the copywriting workflow itself; it is organized and brief but offers almost no actionable, executable guidance. Its real value is offloaded to a remote repo the agent cannot read directly.

Suggestions

Replace the vague "install the upstream bundle" instruction with a concrete, copy-pasteable command (e.g., the exact git clone / install path) so the body is actionable on its own.

Either inline a minimal copywriting workflow (draft → review → revise, with a worked landing-page example) or vendor the key reference file locally so the agent can read it without fetching a remote repo.

Drop the duplicated "What it does" section and the "Curated from…" blockquote, or fold them into a single concise header, to tighten conciseness.

DimensionReasoningScore

Conciseness

The body is short and avoids explaining concepts Claude already knows, but the "What it does" section duplicates the frontmatter description verbatim and the "Curated from Corey Haines" blockquote is filler that does not earn its place.

2 / 3

Actionability

The only concrete command is `open https://github.com/...` (a browser open), and the actual instruction to "install the upstream bundle into your active agent's skills directory" gives no executable command, so it describes rather than instructs how to do copywriting.

1 / 3

Workflow Clarity

A loose sequence is present (inspect the upstream README, install the bundle, invoke by name or trigger), but the critical install step lacks concrete detail and there are no checkpoints, fitting the score-2 anchor rather than the validated score-3 example.

2 / 3

Progressive Disclosure

The body is well sectioned and short, but all substantive content is delegated to an external GitHub URL rather than a local, directly-readable reference file, and no bundle files exist in references/scripts/assets, so navigation is not as easy as a one-level local reference.

2 / 3

Total

7

/

12

Passed

Description

57%

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 and occupies a distinct niche, but it lacks an explicit "Use when…" trigger clause and its trigger terms are somewhat terse with missing common variants. It is solid but not exemplary.

Suggestions

Add an explicit "Use when…" clause naming concrete triggers (e.g., "Use when writing or rewriting landing page, homepage, or ad copy during a launch") to lift completeness to 3.

Expand triggers with natural variations users actually say, such as "landing page copy", "sales copy", "email copy", and "CTA / headline writing".

Broaden the action vocabulary beyond write/rewrite (e.g., draft, A/B test variants, tighten) to strengthen specificity.

DimensionReasoningScore

Specificity

Names the marketing-copy domain and two actions ("Write and rewrite") across three concrete surfaces (landing pages, homepages, and ads), but the action vocabulary is limited and not comprehensive, matching the score-2 anchor rather than the multi-action score-3 example.

2 / 3

Completeness

The "what" is explicit (write and rewrite marketing copy for landing/homepage/ads), but the "when" is only soft context ("Useful as a copy chief partner during launches") with no explicit "Use when…" clause, so completeness is capped at 2 per the guideline.

2 / 3

Trigger Term Quality

Triggers (copywriting, landing copy, ad copy, homepage copy, rewrite copy) are relevant and fairly natural, but several are terse abbreviations and common variants like sales/email/product copy are absent, leaving it short of full coverage.

2 / 3

Distinctiveness Conflict Risk

Marketing copy for landing pages, homepages, and ads is a clear niche with surface-specific triggers, making it unlikely to fire for unrelated skills; it is not the level below because it is more specific than the "could still overlap" score-2 anchor.

3 / 3

Total

9

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
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.