Skill detail
content-writing
Comprehensive workflow for creating and improving many forms of copy and content.
Inspect before use
Automated review checks relevance, not safety or endorsement. Read the source instructions before using this skill.
SKILL.md
The saved excerpt is a snapshot from review. The external source remains the complete and most current version.
---
name: content-writing
description: Write new copy or diagnose and improve existing copy. Covers any kind of writing — landing pages, ads, emails, social posts, sales decks, proposals, internal docs, reports, press releases, blog articles, case studies, headlines, taglines, product descriptions. Use this skill whenever the user mentions writing, copy, copywriting, drafting, editing, headlines, taglines, body copy, ad copy, email copy, social posts, landing page copy, press releases, blog posts, case studies, slide copy, or asks to make existing text "better," "tighter," "punchier," or "more persuasive."
---
# Content Writing
Produce the most effective copy for the goal at hand, or diagnose and rewrite copy that already exists. The user supplies the purpose, audience, goal, and source material. If anything important is missing, ask for it or research it before writing.
## First principles
**Writing comes down to two things: deciding what information to include, and deciding how to express it.** That holds whether you are writing a one-line headline or a thirty-page report.
0. **Define the change you want to cause** — Be explicit about the state the reader should be in after they finish. If this is fuzzy, every later judgment will drift.
- **Action** — purchase, signup, inquiry, download, reply.
- **Conviction** — they trust the argument and conclude "this is right for me."
- **Interest** — they want to read more, learn more, click through.
- **Sustained reading** — they stay engaged to the end without bouncing.
- **Removed objections** — common blockers ("too expensive," "doesn't actually work," "not the right time," "not for someone like me") are addressed before the reader has to raise them.
- **Understanding** — they leave with an accurate, complete mental model of the topic.
1. **Gather** — Pull together everything useful about the subject, the audience, and the context. If the source material is thin, ask or research before you write.
2. **Select** — From what you gathered, keep only what serves the change you want to cause. Trying to say everything is the same as saying nothing. Filter against the reader's interests, problems, and decision criteria.
3. **Express** — Put the selected information into the words, order, and structure that will land hardest with this reader. The same facts in different shapes produce different results.
4. **Use placeholders, never fabricate** — When you don't have a specific number, customer name, quote, result, or detail, don't paper over the gap with plausible-sounding invention or vague hand-waving. Drop in a labeled placeholder (`[X% improvement]`, `[Customer name]`, `[Specific feature]`, `[Date]`) and ask the user for the real data. One fabricated detail does more damage to credibility than ten visible gaps. A placeholder is honest; "significant gains" in place of an unknown number is not.
Most weak writing fails at step 1 or step 2 — not enough source material, or no editorial discipline about what to leave out. Surface-level wordcraft cannot rescue a piece that is unfocused at the foundation.
---
## Workflow: writing something new
### 1. Lock in the goal and the brief
Get clear on what you are actually writing before drafting anything.
**First, narrow down the deliverable from the top:**
- **Mode** — Persuasive (change behavior or belief) or informational (deliver knowledge)? A piece can mix modes at the section level, but the dominant mode shapes every later choice.
- **Piece type** — Landing page, ad, email, social post, blog article, proposal, press release, case study, internal doc, report, etc.
- **Format constraints** — Length, channel, language, any rigid structural requirements (subject-line character limits, slide count, word count for a brief).
**Then confirm the brief. At minimum:**
- **Reader** — Their role, the problem on their mind, what they already know, what they are skeptical about. The narrower you can name them, the harder the piecRead the full source on GitHub (opens external page)