Files
skills/public/subject-lines.md
zeekayandHanzo Dev 65c3b27843 160 marketing, growth and PM skills, on our own connectors
Four MIT collections ported — growthOS, openclaw-marketing-skills,
Marketing-Skills and pm-skills — as 160 skills, 12 agents and 45
commands, each naming its origin in its own frontmatter so the tree can
be checked against THIRD_PARTY_NOTICES rather than trusted. Sixteen names
appeared in more than one collection and none of the copies were
identical; the longest wins, which lands on the more developed text where
they genuinely diverge.

A fifth collection is deliberately absent. awesome-growth-hacking-skills
carries NO licence, which leaves its author every right by default — and
it is a list of links rather than a collection of skills, so there is
nothing in it to port and no permission to port it with. It is cited as a
directory to read.

THE CONNECTOR SKILLS ARE REWRITTEN, not ported. They arrived installing
vendor SDKs, running OAuth flows of their own, and ending with long-lived
credentials in JSON files under .agents/ and ~/.growthos/ at mode 600.
That is a secret on a disk with no rotation path, protected from other
users and not from the agent — and one auth implementation per skill.
Hanzo holds these connectors in Go, per user, sealed in KMS, so `connect`
is the one home for the flow and the platform skills defer to it by
provider id: google_ads, meta_ads, x. It is reachable as HTTP or as MCP
tools at api.hanzo.ai/v1/mcp — the same routes, typed once in Go, so a
tool and a curl cannot disagree.

Two had nothing real behind them and now say so. There is no
search_console provider, so that skill names what does answer the same
questions (google_analytics, google_bigquery) and states that the remedy
is a provider in hanzoai/cloud rather than a vendor SDK here. And
getxapi-connect was a wrapper around a paid reseller of X's public data
with the vendor's key in an env var; it is `listen` now, on our own x
connector — a skill named after a vendor makes the vendor the capability
and dies with it.

The skills referenced paths that only existed inside the source repo, so
the shared material they read is ported to reference/ and the paths
rewritten. Three skills need the growthOS APPLICATION rather than its
data; per the estate's own split an application belongs in hanzoai/ads,
social, email or sms as a cloud plugin, so those three say what they need
instead of carrying an import that resolves to nothing.

Third-party product names are out of our prose and kept in the notices,
which is where the licence requires them and the only place they belong.
A skill's persona names a role, not somebody else's product.


Co-authored-by: Hanzo Dev <[email protected]>
2026-09-15 01:27:26 -07:00

2.9 KiB
Raw Permalink Blame History

Subject Line Optimization

The subject line determines whether the email gets read. The data is counterintuitive: short, boring, internal-looking subject lines win decisively.

Length: 2–4 words

  • 2-word subject lines get 60% more opens than 5-word (Lavender).
  • Going from 2 to 4 words reduces replies by 17.5%.
  • 2–4 words yield 46% open rates vs 34% for 10 words (Belkins, 5.5M emails).
  • Mobile truncates at 30–35 characters — brevity is practical necessity.

Internal Camouflage Principle

Subject lines that look like they came from a colleague, not a vendor, double open rates (Gong). Buyers mentally categorize before opening — if it looks like sales, it's filtered.

High-performing examples: "reply rates" · "trial delays" · "hiring ops" · "employee turnover" · "Q2 forecast" · "new patients" · "personalization issue" · "second page"

Capitalization: lowercase wins

All-lowercase has highest open rates (Gong, 85M+ emails). Lowercase looks more personal/internal. For cold outreach specifically, lowercase beats title case.

Personalization: context over name

Personalized subject lines boost opens 26–50%, but type matters:

  • First name in subject line → 12% fewer replies. Signals automation.
  • Contextual personalization works: pain points, competitors, trigger events, industry challenges.
  • Use {{painPoint}}, {{competitor}}, {{commonGround}} — not {{firstName}}.

Questions: only when highly specific

Data conflicts: Belkins says questions perform well (46% open rate). Lavender says questions lower opens by 56%. Resolution: specific pain questions work ("Need help with {{challenge}}?"), generic questions fail ("Quick question?" / "Have 15 minutes?"). Default to statements.

What to Avoid

Anti-pattern Impact
Salesy language ("increase," "boost," "ROI") -17.9% opens
Urgency words ("ASAP," "urgent") Below 36% opens
Excessive punctuation ("!!!" or "??") -36% opens
Numbers and percentages -46% opens
Emojis Hurt B2B professionalism
Pitching product in subject -57% replies
Empty/no subject line +30% opens but -12% replies
Spam triggers ("free," "guarantee," "act now") Deliverability risk

C-Suite Subject Lines

Executives receive 300–400 emails daily, decide in seconds. They respond 23% more often than non-C-suite when emails pass their filter (6.4% reply rate).

What works: ultra-concise, human, understated. "{{companyInitiative}}" · "thank you" · "an update" · "a question" · reference to a specific project or trigger event.

Anything "salesy" is immediately rejected.