mirror of
https://github.com/hanzoai/skills.git
synced 2026-11-19 00:47:36 +00:00
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]>
4.2 KiB
4.2 KiB
description, argument-hint, source
| description | argument-hint | source |
|---|---|---|
| Comprehensive user research — build personas, segment users, and map the customer journey from research data | <research data, survey results, or product description> | phuryn/pm-skills |
/research-users -- User Research Synthesis
Turn raw research data into actionable user personas, behavioral segments, and customer journey maps. Accepts survey data, interview notes, feedback, analytics, or a product description for exploratory research.
Invocation
/research-users [upload survey results, interview notes, or feedback data]
/research-users B2B project management tool for agencies — help me understand our users
/research-users [paste user feedback or support ticket data]
Workflow
Step 1: Accept Research Inputs
Accept from any combination:
- Survey responses (CSV, spreadsheet, pasted)
- Interview notes or transcripts
- Support tickets or feature requests
- Product analytics / behavioral data
- NPS or satisfaction data
- Product description (for exploratory research without data)
Ask:
- What research do you have? What format?
- What do you want to understand? (who are our users, how do they differ, where's the friction)
- What decisions will this inform? (roadmap, positioning, pricing, onboarding)
Step 2: Build Personas
Apply the user-personas skill:
- Identify 3-4 distinct personas from the data
- For each persona: name, role, goals (JTBD), pains, gains, behavioral patterns
- Include unexpected insights — things that surprised you in the data
- Note persona prevalence (what % of your base each represents, if data allows)
Step 3: Segment Users
Apply the user-segmentation and market-segments skills:
- Create behavioral segments (not just demographics)
- For each segment: size, JTBD, product fit, willingness to pay, engagement level
- Identify the highest-value segment and the highest-growth segment
- Map segments to personas (how they overlap)
Step 4: Map the Customer Journey
Apply the customer-journey-map skill:
- Map the end-to-end journey: Awareness → Consideration → Onboarding → Active Use → Expansion → Advocacy
- For each stage: touchpoints, emotions, pain points, aha moments
- Identify the biggest drop-off points
- Highlight moments of delight worth amplifying
Step 5: Generate Research Report
## User Research Report: [Product]
**Date**: [today]
**Data sources**: [what was analyzed]
**Sample size**: [if applicable]
### Executive Summary
[3-5 sentences: key findings and implications]
### Personas
#### Persona 1: [Name] — "[Quote that captures them]"
- **Who**: [role, context, experience level]
- **Primary JTBD**: [When..., I want to..., so I can...]
- **Key pains**: [top 3]
- **Key gains**: [what delights them]
- **Behavioral pattern**: [how they use the product]
- **Prevalence**: [X% of user base]
[Repeat for each persona]
### User Segments
| Segment | Size | Primary JTBD | Product Fit | Value | Growth |
|---------|------|-------------|-------------|-------|--------|
### Customer Journey Map
| Stage | Touchpoints | Emotion | Pain Points | Opportunities |
|-------|------------|---------|-------------|---------------|
### Key Insights
1. [Insight with supporting evidence]
2. ...
### Recommendations
1. [Actionable recommendation tied to findings]
2. ...
### Open Questions
[What the data didn't answer — suggested follow-up research]
Save as markdown.
Step 6: Offer Next Steps
- "Want me to create interview scripts to go deeper on a specific persona?"
- "Should I analyze sentiment across these segments?"
- "Want me to build a value proposition for the top persona?"
- "Should I prioritize the journey map pain points as feature opportunities?"
Notes
- If data is thin, be transparent about confidence levels — 5 interviews → hypotheses, not conclusions
- Personas should be useful, not decorative — every persona should influence a product decision
- Behavioral segments are more actionable than demographic segments for product decisions
- The journey map should surface emotions, not just actions — where users feel frustrated vs. delighted drives prioritization
- If no data is provided, generate research-informed hypotheses and recommend how to validate them