subject-line-generator
Use when asked to write subject lines, improve open rates, or generate subject line options for an email sequence
How do I install this agent skill?
npx skills add https://github.com/victor-shulga/outbound-engine-skills --skill subject-line-generatorIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill is a prompt-based tool designed to help users generate and rank subject lines for cold outbound emails and LinkedIn messages. It provides a structured framework for creating variations based on specific patterns like 'signal reference' or 'unexpected angle' and suggests using external tools for better data integration. The analysis found no malicious code, credential theft, or exfiltration risks.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
What does this agent skill do?
Subject Line Generator
Generate 10+ subject line options for a given email, score each one, and return a ranked shortlist for testing.
Required tools
Install these before running the skill. None of them is strictly required, the skill also runs on pasted input, but without them the result gets noticeably worse: the signal-reference lines paraphrase the signal, and the top 3 never get tested against each other.
| Tool | Used for | Required? | Without it |
|---|---|---|---|
| Firecrawl (MCP) | read the signal source (job post, news item, company page) so signal-reference lines use its exact wording | Recommended | subject lines are built from your summary of the signal |
| Instantly (MCP) | set the top 3 as step variants and read reply rate per variant from past sends | Recommended | the shortlist is ranked on the 0-2 scores only, with no real results behind it |
Alternatives: Exa can stand in for Firecrawl; lemlist or Smartlead can stand in for Instantly.
Inputs to have ready:
- Email body (step 1 at minimum)
- ICP and persona context
- Signal the email is built around
- Channel: cold email or LinkedIn InMail
Principles
- Subject lines under 6 words perform best in cold outbound
- Never use the company name in the subject line — it reads as a template
- Curiosity beats clarity when it comes to cold email subject lines
- Questions outperform statements when the question is specific, not generic
- Personalization tokens work only when they're signal-derived, not just [First Name]
Subject line patterns to generate
Generate at least 2 from each pattern:
- Signal reference: directly references what just happened at their company ("new SDR team, new pipeline problem")
- Problem statement: names the specific pain without a solution ("pipeline that depends on one channel")
- Reframe: presents an assumption they hold and challenges it ("outbound isn't broken — the playbook is")
- Direct question: asks the exact question the email answers ("is your outbound tied to one channel?")
- Unexpected angle: something they wouldn't expect from a sales email ("your new CRO's first 90 days")
- Ultra short: 1–3 words, creates pattern interrupt ("quick thought", "SDR question")
Process
- Generate 2 subject lines from each of the 6 patterns above (12 total)
- Score each on: curiosity (0–2) + specificity (0–2) + length penalty if over 6 words (−1)
- Rank by score
- Flag top 3 for A/B testing
Terms and plain-language output
<!-- glossary:start terms=open-rate,buying-signal,ab-test,hook mode=copy -->Rules for every text a reader will see (post, email, message, page copy):
- No internal codes or letter scales (A/B/C, D L T E, scores without words, framework codes). Write the meaning.
- Use the plain form from the table below. English stays only for tool names and for copy that ships in English. A term the reader may not know gets explained in the same sentence or replaced.
- Any review, audit or report this skill produces for the team or the client follows the document rules: open it with «Словник цього документа» (terms used, at most 10), do not score what depends on unfinished work, and open each section with one concrete action.
| Internal term (this skill) | Write for the reader | What it means |
|---|---|---|
| open rate, opens | частка відкриттів | Скільки листів відкрили; число неточне, бо поштові сервіси самі відкривають листи, тож це лише підказка. |
| buying signal | ознака готовності купувати | факт про компанію, після якого розмова про вашу послугу доречна саме зараз. |
| A/B test, test ideas, hypotheses | A/B-тест | показуємо половині відвідувачів один варіант, половині інший і дивимось, який дає більше заявок. |
| hook, cold hook | гачок | перший рядок листа, через який людина читає далі |
Output format
Subject lines: [hypothesis / email step]
Email: [step number and first line]
RANKED OPTIONS
Score | Subject line | Pattern
[n] | [subject] | [pattern type]
...
TOP 3 FOR TESTING
A: [subject]
B: [subject]
C: [subject]
Recommended default: [A/B/C] — [one-line reason]
Notes
- Vary the top 3 by ANGLE, not by swapping synonyms — token-level randomisation changes nothing a filter reads and nothing a prospect notices. Different question, different fact, different frame.
- Test subject lines systematically — track open rate by subject line variant, not campaign overall
- If open rate is below 40%, subject line is the first thing to change before touching copy
- Avoid: "quick question", "following up", "[First Name]" as opener — overused and filtered mentally
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/victor-shulga/outbound-engine-skills/subject-line-generator">View subject-line-generator on skillZs</a>