Files
skills/public/customer-journey-map.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

3.2 KiB

name, description, source
name description source
customer-journey-map Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Use when mapping the customer experience, identifying friction points, improving onboarding, or visualizing the user journey. phuryn/pm-skills

Customer Journey Map

Map the end-to-end customer experience from awareness through advocacy, identifying emotions, pain points, and improvement opportunities at each stage.

Context

You are creating a customer journey map for $ARGUMENTS.

If the user provides files (interview transcripts, survey data, analytics, support tickets, or existing journey maps), read them first. Use web search to understand the product if a URL is provided.

Instructions

  1. Define the persona: Who is traveling this journey? Use a specific persona with JTBD, not a generic user.

  2. Map the journey stages (adapt to the product):

    Stage Description
    Awareness How do they first learn about the product?
    Consideration What do they evaluate? What alternatives do they compare?
    Acquisition How do they sign up or purchase?
    Onboarding First experience with the product — time to value
    Engagement Regular usage — building habits
    Retention What keeps them coming back? What might cause churn?
    Advocacy When and why do they recommend the product to others?
  3. For each stage, document:

    • Touchpoints: Where the user interacts with the product, brand, or team (website, email, in-app, support, social media)
    • User actions: What they do at this stage
    • Thoughts & questions: What's on their mind ("Is this worth my time?" "How do I...?")
    • Emotions: How they feel (excited, confused, frustrated, delighted) — rate on a scale or use emoji indicators
    • Pain points: Friction, confusion, drop-off risks
    • Opportunities: How to improve the experience at this point
  4. Identify critical moments:

    • Aha moment: When the user first experiences core value
    • Moments of truth: Decision points where they commit or abandon
    • Churn triggers: Where users most commonly drop off
  5. Create the journey map table:

    Stage Touchpoint User Action Emotion Pain Point Opportunity
  6. Recommend prioritized improvements:

    • Which pain points have the highest impact on conversion or retention?
    • What quick wins can improve the experience immediately?
    • What requires deeper investment but has the biggest payoff?

Think step by step. Save as a markdown document. For visual journey maps, suggest the user create one in Miro or FigJam using this analysis as the foundation.


Further Reading