Write conversion copy with ak:copywriting

Use ak:copywriting to turn a concrete audience, offer, channel, and brand-voice brief into persuasive copy. The Skill supplies formulas, headline and CTA patterns, channel structures, a copy-brief template, and a helper for extracting writing-style signals from project assets.

Choose ak:copywriting for persuasive copy

Use ak:copywriting when

• You need headlines, subject lines, email sequences, landing-page sections, product descriptions, social posts, CTAs, or A/B variants.
• You have an audience, offer, proof points, desired action, and constraints to turn into a reviewable draft.
• You want to analyze an approved writing sample and apply its observable style dimensions without copying its substance.

Choose another workflow when

• You need factual product or API documentation. Use ak:docs and treat persuasion as a secondary edit.
• You need a full interface implemented around the copy. Use ak:frontend-design or ak:frontend-development after the message is clear.
• You need market evidence, legal review, brand approval, or current platform-policy research. Obtain that evidence separately; this Skill's templates do not establish it.
• The source contains personal, confidential, licensed, or unpublished material that is not approved for model processing.

Prepare the brief and source material

Before you start:

• Complete Onboarding, and confirm Engineer Kit is installed for the current runtime and scope.
• Provide the audience, awareness level, pain points, goal, offer, primary CTA, format, length, tone, must-include items, must-avoid items, and success metric.
• Supply exact, supportable proof: product behavior, prices, dates, guarantees, customer quotes, study results, and legal qualifiers. Mark anything that is a placeholder rather than a verified claim.
• Identify the approved brand or writing samples and whether the runtime may read them or send them to an external processor.
• State the output location if you want files written. Otherwise, request copy in the response and keep the project unchanged.

The declared argument hint is [copy-type] [context], but the Skill does not define a parser, fixed copy-type list, or default output file. State the desired deliverable and boundaries in natural language.

Run the Skill with a complete brief

/ak:copywriting "Draft a landing-page hero and three headline variants for finance leads who already know the problem. Use only the supplied product facts and approved customer quote, keep the tone direct and professional, use one CTA to book a demo, and flag every missing proof point instead of inventing it. Return copy in chat; do not write files."

/ak:copywriting "Draft a landing-page hero and three headline variants for finance leads who already know the problem. Use only the supplied product facts and approved customer quote, keep the tone direct and professional, use one CTA to book a demo, and flag every missing proof point instead of inventing it. Return copy in chat; do not write files."

$ak:copywriting "Draft a landing-page hero and three headline variants for finance leads who already know the problem. Use only the supplied product facts and approved customer quote, keep the tone direct and professional, use one CTA to book a demo, and flag every missing proof point instead of inventing it. Return copy in chat; do not write files."

The bundled brief organizes project information, audience and awareness, deliverable details, key messages, proof, constraints, formula, and success metrics. You can provide the same information directly or ask the Skill to make missing decisions visible before drafting.

Select patterns without treating them as proof

The reference material contains historical conversion tips, platform limits, and example performance claims. Treat them as prompts to test, not current benchmarks or guarantees. Verify platform rules and campaign data at the time of use.

Extract a writing style deliberately

The packaged helper scans assets/writing-styles/ for approved text, documents, images, or video. Its user-facing modes are --list, --style <name>, --all, --json, and --verbose.

python scripts/extract-writing-styles.py --list
python scripts/extract-writing-styles.py --style founder-voice --json

Plain .md and .txt files are read locally. PDF, DOCX, XLSX, and PPTX inputs invoke Multix document conversion. Image and video inputs invoke Multix Gemini analysis. The helper can therefore download and execute @mrgoonie/multix@0.2.0, use the network, send source material to a model provider, and require GEMINI_API_KEY for those external paths.

For document conversion, the helper writes a hidden temporary Markdown file beside the source style asset and deletes it after a successful readable output. Failed or interrupted runs need an explicit directory check. The release's --all result does not match its text formatter's expected shape, so do not rely on that mode without fixing or independently verifying it; process named styles individually instead.

Observe the stages

1. The Skill confirms the copy contract. It identifies the reader, awareness level, offer, channel, objective, CTA, proof, voice, constraints, and output boundary.
2. It selects a structure. A formula and channel pattern organize the draft; they do not supply missing facts.
3. It studies approved style evidence. It uses stated dimensions or analyzes authorized samples, separating observed traits from the source's content.
4. It drafts and varies. The main copy and requested variants keep the same factual contract while testing a bounded message difference.
5. It checks the work. Claims, specificity, reader fit, CTA consistency, tone, prohibited language, and channel constraints are reviewed.
6. It returns evidence. The result names the chosen pattern, source facts, assumptions, unresolved proof gaps, variants, and any files or services used.

Keep claims, rights, and external effects controlled

• Get approval before sending source documents or media to an external provider, especially customer data, internal strategy, unpublished work, or licensed creative material.
• Style transfer should reproduce abstract traits such as pace and tone, not distinctive passages, personal likeness, or deceptive authorship.
• Do not create fake testimonials, logos, statistics, deadlines, stock levels, guarantees, security claims, or endorsements.
• The Skill may draft copy or write an explicitly requested artifact. It does not publish a page, send an email, post to a social network, start an A/B test, purchase media, or approve legal claims unless a separately authorized workflow performs that action.

Verify outputs and evidence

A useful result should include:

• The final copy in the requested format and length, plus clearly labeled variants when requested.
• Audience, awareness, offer, CTA, formula or structure, and style dimensions used to make the draft.
• A claim ledger that distinguishes supplied facts, cited proof, assumptions, placeholders, and statements still needing legal, brand, or subject-matter approval.
• Exact files read or written, temporary files checked, helper commands run, external provider use, and failures or skipped stages.
• A compact review against must-include, must-avoid, voice, accessibility, channel, and success-metric requirements.

The bundled writing-style guide presents six detailed preset definitions even though the Skill's reference table labels it as a 30-style quick reference. Do not report 30 ready-to-use styles. The pinned stable and beta releases contain the same Skill files, and no directly scoped automated tests were found for the copy workflow or extraction helper.

Troubleshoot and interpret limits

Use ak:docs for factual documentation or ak:frontend-design when the copy belongs inside an implemented interface.