AC copywriting
Write persuasive, high-converting copy for any format — ads, landing pages, emails, sales pages, headlines, product descriptions, CTAs, and social posts. Applies professional copywriting SOPs including avatar/ICP development, Voice of Customer research, Eugene Schwartz's 5 Stages of Awareness, AIDA, PAS, BAB, FAB frameworks, the TIMER offer framework, readability rules (Grade 6, ≤14 words/sentence), psychological triggers (scarcity, social proof, loss aversion, reciprocity), and the 4 C's quality checklist. Use when a user asks to write, improve, rewrite, or review any marketing or sales copy.
As a process C 52/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
The same skill appears in 1 more place: ClawHub
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 52/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (copywriting) differs from the folder (copywriting-pro)
- 65Failures and branches. 3 branches
- 100Tools and files. No external tools needed
- 100Steps. 23 steps
- 100Execution cost. Instruction body is 1013 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 600: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 23 items
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.