Raise a newsletter open rate to 43% with Claude Cowork edits

Our fuller version of the person's prompt. They didn't use this version, and we haven't tested it.

Before you start, ask me 1–3 short questions about the details below and wait for my answers. Once I've answered, confirm the plan in one line and run the whole task start to finish.

Goal: Edit my newsletter draft to match my voice, catch errors and improve packaging.

Questions to ask me first:
- Where is the draft (Docs link) and my style samples?
- Which subject-line history should you use?
- Any claims that must be fact-checked first?

Inputs (fill in or confirm):
- Draft: [GOOGLE DOC LINK]
- Style samples: [FILES]
- Performance history: [BEEHIIV / CSV]
- Connectors: [DRIVE / CHROME / OPTIONAL]

Rules:
- Preserve my voice; do not replace the piece with generic AI tone.
- Fact-check claims with sources.
- Suggest subject lines from what actually performed.
- Leave tracked suggestions; I accept or reject.

Checkpoint: Roast the ending and structure in a short note before rewriting.

If you get stuck: If a claim cannot be verified, flag it instead of inventing a source.

Verify before you finish: Every factual edit cites a check, and style notes reference my samples.

Output: Annotated draft, subject-line options, and meta title/description ideas.

Done when: I can publish a tighter issue without a multi-hour self-edit.

Before you start, ask me 1–3 short questions about the details below and wait for my answers. Once I've answered, confirm the plan in one line and run the whole task start to finish.

Goal: Edit my newsletter draft to match my voice, catch errors and improve packaging.

Questions to ask me first:
- Where is the draft (Docs link) and my style samples?
- Which subject-line history should you use?
- Any claims that must be fact-checked first?

Inputs (fill in or confirm):
- Draft: [GOOGLE DOC LINK]
- Style samples: [FILES]
- Performance history: [BEEHIIV / CSV]
- Connectors: [DRIVE / CHROME / OPTIONAL]

Rules:
- Preserve my voice; do not replace the piece with generic AI tone.
- Fact-check claims with sources.
- Suggest subject lines from what actually performed.
- Leave tracked suggestions; I accept or reject.

Checkpoint: Roast the ending and structure in a short note before rewriting.

If you get stuck: If a claim cannot be verified, flag it instead of inventing a source.

Verify before you finish: Every factual edit cites a check, and style notes reference my samples.

Output: Annotated draft, subject-line options, and meta title/description ideas.

Done when: I can publish a tighter issue without a multi-hour self-edit.

Help me create a skill that would (a) create a style guide tailored to me, (b) fact check every claim via web search, (c) review the flow and grammar of the piece, and (d) suggest SEO titles/descriptions. The output is a publish-ready version with suggestions as tracked changes.