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]>
5.3 KiB
Cold Email Copywriting Frameworks
Frameworks beat templates — they teach thinking patterns, not copy-paste shortcuts.
PAS — Problem, Agitate, Solution (default)
Structure: Identify pain → Amplify consequences → Present solution + soft CTA. Best for: Problem-aware but not solution-aware prospects. The workhorse framework.
Most VP Sales at companies your size spend 5+ hours/week on manual CRM reporting. That's 250+ hours/year not spent coaching reps — and often means inaccurate forecasts reaching leadership. We built a tool that auto-generates CRM reports in real time. Teams like Datadog reduced reporting time by 80%. Would it make sense to see how?
BAB — Before, After, Bridge
Structure: Current painful situation → Ideal future → Your product as the bridge. Best for: Transformation-driven offers with clear before/after. Emotional decision-makers.
Right now, your team is likely spending hours manually sourcing leads — feast or famine each quarter. Imagine qualified leads arriving daily on autopilot, reps spending 100% of their time selling. That's what our platform does. Companies like HubSpot saw a 40% pipeline increase within 90 days. Can I show you how?
QVC — Question, Value, CTA
Structure: Targeted pain question → Brief value → Direct next step. Best for: C-suite prospects who prefer brevity. Qualify interest immediately.
Are your SDRs spending more time researching than selling? We help sales teams automate prospect research so reps focus on conversations. Clients see 3x more meetings per rep per week. Worth a 10-minute demo?
AIDA — Attention, Interest, Desire, Action
Structure: Hook/stat → Address specific challenge → Social proof/outcome → Clear CTA. Best for: Data-driven prospects, high-ticket pitches with strong stats.
Companies in pharma lose 30% of leads due to manual outreach. Given {{Company}}'s growth this quarter, pipeline velocity is likely top of mind. Customers like Pfizer use our platform to automate lead qualification — cutting time-to-contact by 60%. Worth a 15-minute call?
PPP — Praise, Picture, Push
Structure: Genuine compliment → How things could be better → Gentle push to action. Best for: Senior prospects who respond to relationship-building. Requires genuine trigger.
Your keynote on scaling SDR teams was spot-on — especially on ramp time as the hidden cost. What if you could cut that in half? Our in-inbox coach helps new reps write effective emails from day one with real-time scoring. Open to a quick chat about how this could support your growth?
Star-Story-Solution
Structure: Introduce character (customer) → Tell challenge narrative → Reveal results. Best for: Strong customer success stories. Humanizes the pitch.
Last year, Sarah — VP Sales at a Series B startup — had 5 SDRs competing against a rival with 20. Her team was getting crushed on volume. They adopted our AI prospecting tool and sent hyper-personalized emails at 3x pace without losing quality. Within 90 days, they booked more meetings than their competitor's entire team. Happy to share how this could work for {{Company}}.
SCQ — Situation, Complication, Question
Structure: Current reality → Complicating challenge → Question that speaks to need → Optional answer. Best for: Consultative selling. Mirrors how professionals present to leadership.
Your team doubled this year. That usually means onboarding is eating into selling time. How are you handling ramp for new hires?
ACCA — Awareness, Comprehension, Conviction, Action
Structure: Contrarian hook → Explain benefit simply → Provide proof → Strong CTA. Best for: Analytical buyers who need evidence (engineers, CFOs, ops leaders).
Most sales teams measure rep activity. The top 5% measure rep efficiency instead. When Acme switched, they booked 40% more meetings with fewer emails. Worth seeing how?
3C's (Alex Berman)
Structure: Compliment → Case Study → CTA. Best for: Agency/services cold outreach. Case study does the heavy lifting.
Big fan of [Company]. We just built an app for [Competitor] that does XYZ. I have a few more ideas. Interested?
Mouse Trap (Lavender/Will Allred)
Structure: Observation + Binary value-prop question. 1–2 sentences total. Best for: Maximum brevity. Impulsive reply based on curiosity.
Looks like you're hiring reps. Would it be helpful to get a more granular look at how they're ramping on email?
Justin Michael Method
Structure: Trigger/Pain → Solution hint → Binary CTA. 1–3 sentences, no intro. Best for: High-velocity SDR teams. Mobile-optimized. Deliberately polarizing.
Spend max 1 minute on personalization. Use industry/persona-level signals. For top-tier prospects, quote their own words from interviews — they almost always respond.
Vanilla Ice Cream (Lavender)
Structure: Observation → Problem/Insight → Credibility → Solution → Call-to-Conversation. Best for: Universal "base" framework that works everywhere. Five parts.
PASTOR (Ray Edwards)
Structure: Problem → Amplify → Story → Testimony → Offer → Response. Best for: Longer-form or multi-email sequences. Consulting, education, complex B2B services. Each element can be developed across separate touches.