Improve Newsletter Draft
Requirements
Newsletter draft text
2
Analyze the draft for:
ENGAGEMENT
- Does the subject line compel opening?
- Does the opener hook the reader?
- Is there a clear value proposition?
STRUCTURE
- Easy to scan?
- Logical flow of topics?
- Appropriate length?
CLARITY
- Clear, concise writing?
- Jargon-free (unless audience expects it)?
- Each section has a point?
AUDIENCE MATCH
- Does content complexity match the stated or implied audience?
- Is jargon explained when used?
- Would a reader outside the target group understand key points?
- If technical content for broad audience: suggest simplification
ACTION
- Clear CTA?
- Links are compelling?
- Reader knows what to do next?
3
Provide specific feedback:
- What's working well
- What needs improvement
- Suggestions for stronger hooks or closers
- Opportunities to cut without losing value
4
Offer a revised version with key improvements.
Provide alternative subject lines if the original is weak.
To run this task you must have the following required information:
> Newsletter draft text
If you don't have all of this information, exit here and respond asking for any extra information you require, and instructions to run this task again with ALL required information.
---
You MUST use a todo list to complete these steps in order. Never move on to one step if you haven't completed the previous step. If you have multiple read steps in a row, read them all at once (in parallel).
Add all steps to your todo list now and begin executing.
## Steps
1. [Read Newsletter Writing Guide]: Read the documentation in: `./skills/sauna/[skill_id]/references/compose.newsletter.guide.md`
2. Analyze the draft for:
ENGAGEMENT
- Does the subject line compel opening?
- Does the opener hook the reader?
- Is there a clear value proposition?
STRUCTURE
- Easy to scan?
- Logical flow of topics?
- Appropriate length?
CLARITY
- Clear, concise writing?
- Jargon-free (unless audience expects it)?
- Each section has a point?
AUDIENCE MATCH
- Does content complexity match the stated or implied audience?
- Is jargon explained when used?
- Would a reader outside the target group understand key points?
- If technical content for broad audience: suggest simplification
ACTION
- Clear CTA?
- Links are compelling?
- Reader knows what to do next?
3. Provide specific feedback:
- What's working well
- What needs improvement
- Suggestions for stronger hooks or closers
- Opportunities to cut without losing value
4. Offer a revised version with key improvements.
Provide alternative subject lines if the original is weak.