Files
skills/public/copy-guidelines.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.3 KiB

Email Copy Guidelines

Contents

  • Structure
  • Formatting
  • Tone
  • Length
  • CTA Buttons vs. Links
  • Personalization (merge fields, dynamic content, triggered emails)
  • Segmentation Strategies (by behavior, by stage, by profile)
  • Testing and Optimization (what to test, how to test, metrics to track)

Structure

  1. Hook: First line grabs attention
  2. Context: Why this matters to them
  3. Value: The useful content
  4. CTA: What to do next
  5. Sign-off: Human, warm close

Formatting

  • Short paragraphs (1-3 sentences)
  • White space between sections
  • Bullet points for scanability
  • Bold for emphasis (sparingly)
  • Mobile-first (most read on phone)

Tone

  • Conversational, not formal
  • First-person (I/we) and second-person (you)
  • Active voice
  • Match your brand but lean friendly
  • Read it out loud—does it sound human?

Length

  • Shorter is usually better
  • 50-125 words for transactional
  • 150-300 words for educational
  • 300-500 words for story-driven
  • If it's long, it better be good
  • Buttons: Primary actions, high-visibility
  • Links: Secondary actions, in-text
  • One clear primary CTA per email
  • Button text: Action + outcome

Personalization

Merge Fields

  • First name (fallback to "there" or "friend")
  • Company name (B2B)
  • Relevant data (usage, plan, etc.)

Dynamic Content

  • Based on segment
  • Based on behavior
  • Based on stage

Triggered Emails

  • Action-based sends
  • More relevant than time-based
  • Examples: Feature used, milestone hit, inactivity

Segmentation Strategies

By Behavior

  • Openers vs. non-openers
  • Clickers vs. non-clickers
  • Active vs. inactive

By Stage

  • Trial vs. paid
  • New vs. long-term
  • Engaged vs. at-risk

By Profile

  • Industry/role (B2B)
  • Use case / goal
  • Company size

Testing and Optimization

What to Test

  • Subject lines (highest impact)
  • Send times
  • Email length
  • CTA placement and copy
  • Personalization level
  • Sequence timing

How to Test

  • A/B test one variable at a time
  • Sufficient sample size
  • Statistical significance
  • Document learnings

Metrics to Track

  • Open rate (benchmark: 20-40%)
  • Click rate (benchmark: 2-5%)
  • Unsubscribe rate (keep under 0.5%)
  • Conversion rate (specific to sequence goal)
  • Revenue per email (if applicable)