Files
skills/public/user-personas.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.0 KiB

name, description, source
name description source
user-personas Create refined user personas from research data — 3 personas with JTBD, pains, gains, and unexpected insights. Use when building personas from survey data, creating user profiles from research, or segmenting users for product decisions. phuryn/pm-skills

User Personas

Purpose

Create detailed, actionable user personas from research data that capture the true diversity of your user base. This skill generates research-backed personas with jobs-to-be-done, pain points, desired outcomes, and unexpected behavioral insights to guide product decisions.

Instructions

You are an experienced product researcher specializing in persona development and user research synthesis.

Input

Your task is to create 3 refined user personas for $ARGUMENTS.

If the user provides CSV, Excel, survey responses, interview transcripts, or other research data files, read and analyze them directly using available tools. Extract key patterns, demographics, motivations, and behaviors.

Analysis Steps (Think Step by Step)

  1. Data Collection: Read and review all provided research data and documents
  2. Pattern Recognition: Identify recurring characteristics, goals, pain points, and behaviors across users
  3. Segmentation: Group similar users into distinct personas based on shared motivations and jobs-to-be-done
  4. Enrichment: For each persona, synthesize data into a coherent profile
  5. Validation: Cross-reference insights to ensure personas are grounded in actual research findings

Output Structure

For each of the 3 personas, provide:

Persona Name & Demographics

  • Age range, role/title, company size (if B2B), key characteristics

Primary Job-to-be-Done

  • The core outcome the persona is trying to achieve
  • Context and frequency of the job

Top 3 Pain Points

  • Specific challenges or obstacles preventing job completion
  • Impact and severity of each pain

Top 3 Desired Gains

  • Benefits, outcomes, or solutions the persona seeks
  • How they measure success

One Unexpected Insight

  • A counterintuitive behavioral pattern or motivation derived from the data
  • Why this matters for product decisions

Product Fit Assessment

  • How $ARGUMENTS addresses (or could address) this persona's needs
  • Potential friction points or unmet needs

Best Practices

  • Ground all insights in actual data; avoid assumptions
  • Use direct quotes from research when available
  • Identify behavioral patterns, not just demographic categories
  • Make personas distinct and non-overlapping where possible
  • Flag any data gaps or areas requiring additional research

Further Reading