---
name: email-subject-line-optimizer
description: "Produces five subject line candidates for an email and scores each one for predicted open rate, returned as JSON so the top two can go straight into an A/B test. Use when subject line options need a predicted open-rate score and a ranking in JSON, so the top candidates can be picked for an A/B test or loaded into a tool. Do not use for writing the email itself, or subject lines without a score such as a plain list for a copy review. Related topics: marketing, business, email."
---

# Email Subject Line Optimizer

Produces five subject line candidates for an email and scores each one for predicted open rate, returned as JSON so the top two can go straight into an A/B test.

## When to use

Use this skill when subject line options need a predicted open-rate score and a ranking in JSON, so the top candidates can be picked for an A/B test or loaded into a tool. Do not use it for writing the email itself, or subject lines without a score such as a plain list for a copy review.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Write five candidates on five different levers: clarity, specificity, curiosity, true urgency, and personal relevance, each inside the word count and a selected tone.
3. Apply the emoji rule, allowing at most one at the start or end when the toggle permits it.
4. Score each candidate as the weighted sum of clarity (30), relevance (25), purpose fit (20), spam safety (15), and novelty (10).
5. Write a one-sentence reason per candidate naming its weakest factor, so the score can be challenged.
6. Sort the array by score descending and output valid JSON with no text outside the object.

## Inputs

- **Target audience** (free text, e.g. "busy professionals")
- **Email purpose** (choose one: Promotion, Newsletter, Survey, Announcement, Event invitation)
- **Desired tone** (choose any: Friendly, Urgent, Professional, Playful, Formal)
- **Main benefit or offer** (longer free text)
- **Subject line length in words** (number from 5 to 10)
- **Include emoji** (choose one: Yes, No)

## Output

A JSON object with a "subjectLines" array of five entries, each with text, score (integer 1 to 100), and reason, sorted by score descending, and nothing outside the object.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Scored Subject Line Options

Generate subject line candidates for the email below and score each one, so the strongest two can be chosen for an A/B test without guesswork.

### Details
- Target audience: {{Target audience}}
- Email purpose: {{Email purpose}}
- Desired tone: {{Desired tone}}
- Main benefit or offer: {{Main benefit or offer}}
- Subject line length in words: {{Subject line length in words}}
- Include emoji: {{Include emoji}}

Write five candidates that each use a different lever: clarity of the benefit, specificity (a number or a name), curiosity, urgency that is true for this email, and personal relevance to the audience. Keep every line within the word count and in one of the selected tones; when emoji are allowed, use at most one, at the start or end only. Then score each candidate from 1 to 100 for predicted open rate using these factors with the weights shown: clarity of what the reader gets (30), relevance to the stated audience (25), fit to the email purpose (20), spam-filter and preview safety (15), and novelty against what an inbox normally shows (10). Write the score as the weighted sum, and give a one-sentence reason per candidate that names the weakest factor. Sort by score, highest first.

### Output
A JSON object with the key "subjectLines" holding an array of five objects, each with "text" (the subject line), "score" (an integer from 1 to 100), and "reason" (one sentence naming the weakest factor), sorted by score descending, with nothing outside the object.

## Pitfalls

- Scoring every line between 70 and 80, which gives the marketer no basis to pick a test pair.
- Rewarding urgency that the email cannot honour, which lifts opens once and trains readers to ignore the sender.
- Wrapping the JSON in prose or code fences when the output will be parsed by a script.
