Files
skills/public/gtm-strategy.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

4.0 KiB
Raw Permalink Blame History

name, description, source
name description source
gtm-strategy Create a go-to-market strategy covering marketing channels, messaging, success metrics, and launch timeline. Use when planning a product launch, creating a GTM plan from scratch, or defining a launch strategy for a new market. phuryn/pm-skills

GTM Strategy

Overview

Create a comprehensive go-to-market strategy for a product launch. This skill covers marketing channels, messaging development, success metrics definition, and launch planning.

When to Use

  • Planning a product launch
  • Creating a GTM plan from scratch
  • Defining a launch strategy for a new market
  • Developing product-to-market fit strategy
  • Preparing a product go-live roadmap

How It Works

Step 1: Gather Research Data

The system will help you load and analyze early research about your product and target market. Provide:

  • Product description and key features
  • Target market segment details
  • Market research or validation data
  • Competitive landscape information
  • Any available customer interviews or survey data

Step 2: Define Marketing Channels

Evaluate which channels best reach your target audience:

  • Digital marketing channels (paid search, social media, display)
  • Content and inbound channels (blog, SEO, thought leadership)
  • Sales and outbound channels (direct outreach, partnerships)
  • Community and grassroots channels
  • Product-led and viral channels

Step 3: Develop Messaging

Create audience-specific messaging that resonates:

  • Core value proposition for target segment
  • Key differentiators and competitive advantages
  • Pain point validation and solution mapping
  • Proof points and social proof strategies
  • Channel-specific messaging variations

Step 4: Define Success Metrics

Establish measurable KPIs to track launch success:

  • Awareness metrics (impressions, reach, brand recall)
  • Engagement metrics (CTR, cost per engagement, time on site)
  • Conversion metrics (signups, demos requested, trials started)
  • Revenue metrics (MRR, customer acquisition cost, lifetime value)
  • Market metrics (market share, segment penetration)

Step 5: Create Launch Plan

Build a phased launch timeline:

  • Pre-launch preparation (messaging, channels, timeline)
  • Launch day activities and announcements
  • Post-launch momentum (content, partnerships, communities)
  • Measurement and optimization cadence
  • Success criteria and go/no-go decision points

Input Format

Use $ARGUMENTS to pass:

  • Product name and description
  • Target market segment
  • Research data or file path
  • Launch timeline and constraints
  • Budget or resource limitations

Output

A structured GTM strategy document including:

  • Recommended marketing channels with justification
  • Channel-specific messaging and positioning
  • Launch timeline with key milestones
  • KPI targets and measurement framework
  • Risk mitigation strategies
  • 90-day execution roadmap

Framework

This skill applies Product Compass GTM strategy methodology, focusing on market selection, channel fit, and message-market fit for sustainable product growth.

Tips

  • Start with your most confident customer segment
  • Validate assumptions through customer interviews before full launch
  • Focus on a few channels excellently rather than many channels poorly
  • Establish baseline metrics before launch to measure impact
  • Plan for feedback loops and optimization

Further Reading