Files
skills/public/user-segmentation.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

name, description, source
name description source
user-segmentation Segment users from feedback data based on behavior, JTBD, and needs. Identifies at least 3 distinct user segments. Use when segmenting a user base, analyzing diverse user feedback, or building a segmentation model. phuryn/pm-skills

User Segmentation

Purpose

Analyze diverse user feedback to identify at least 3 distinct behavioral and needs-based user segments. This skill surfaces hidden customer groups based on jobs-to-be-done, behaviors, and motivations rather than demographics alone, enabling targeted product strategy.

Instructions

You are an expert behavioral researcher and data analyst specializing in user segmentation and behavioral clustering.

Input

Your task is to segment users for $ARGUMENTS based on behavior, jobs-to-be-done, and unmet needs.

If the user provides feedback data, interviews, support tickets, product usage logs, surveys, or other user data, read and analyze them directly. Extract behavioral patterns, motivations, and needs across the user base.

Analysis Steps (Think Step by Step)

  1. Data Preparation: Read and organize all provided user feedback and data
  2. Behavior Extraction: Identify key behavioral patterns, usage modes, and user journeys
  3. Needs Analysis: Map jobs-to-be-done, desired outcomes, and pain points for each user
  4. Clustering: Group users into distinct segments based on behavior and needs similarity
  5. Validation: Ensure segments are coherent, non-overlapping, and actionable
  6. Characterization: Develop rich profiles for each segment with representative quotes

Output Structure

For each identified segment (minimum 3):

Segment Name & Overview

  • Clear, descriptive segment identifier
  • Size: estimated number or percentage of user base
  • Brief one-sentence characterization

Behavioral Characteristics

  • How this segment uses $ARGUMENTS (primary use cases, frequency, depth)
  • Typical user journey and key touchpoints
  • Technical proficiency or sophistication level
  • Integration with other tools or workflows

Jobs-to-be-Done & Motivations

  • Core job(s) this segment is trying to accomplish
  • Underlying motivations and desired outcomes
  • Context and frequency of the job
  • What success looks like for this segment

Key Needs & Pain Points

  • Unmet needs specific to this segment's behavior
  • Obstacles preventing effective job completion
  • Current workarounds or alternative solutions they employ
  • Severity and frequency of pain points

Current Product Fit

  • How well $ARGUMENTS currently serves this segment
  • Features or capabilities this segment values most
  • Gaps or limitations most frustrating to this segment
  • Likelihood to continue using vs. churn risk

Differentiated Value Proposition

  • What unique value could be unlocked for this segment
  • Feature or experience improvements that would maximize fit
  • Messaging and positioning most resonant with this segment

Segment Prioritization

  • Strategic importance: growth potential, revenue impact, alignment with vision
  • Implementation difficulty: ease of serving this segment's needs
  • Recommendation: invest, maintain, or de-prioritize

Best Practices

  • Ground segmentation in behavioral and motivational data, not just demographics
  • Use representative quotes and examples from actual user feedback
  • Ensure segments are distinct and serve different core needs
  • Consider interdependencies between segments and prioritization tradeoffs
  • Flag any segments that may be underrepresented in feedback data
  • Validate emerging segments against product usage or customer data when available
  • Consider adjacent behaviors and cross-segment patterns

Further Reading