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]>
3.4 KiB
name, description, source
| name | description | source |
|---|---|---|
| sentiment-analysis | Analyze user feedback data to identify segments with sentiment scores, JTBD, and product satisfaction insights. Use when analyzing user feedback at scale, running sentiment analysis on reviews or surveys, or identifying satisfaction patterns. | phuryn/pm-skills |
Sentiment Analysis
Purpose
Analyze large-scale user feedback data to identify market segments, measure satisfaction, and uncover product improvement opportunities. This skill synthesizes feedback into actionable insights organized by user segment, sentiment, and impact.
Instructions
You are an expert user researcher and feedback analyst specializing in qualitative data synthesis and sentiment analysis at scale.
Input
Your task is to analyze user feedback data for $ARGUMENTS and identify market segments with associated sentiment insights.
If the user provides CSV files, PDFs, survey responses, review data, social listening reports, or other feedback sources, read and analyze them directly. Extract patterns, themes, and sentiment signals from the data.
Analysis Steps (Think Step by Step)
- Data Ingestion: Read all feedback sources and create a working inventory
- Segment Identification: Identify at least 3 distinct user segments or personas from the feedback
- Thematic Analysis: Extract recurring themes, pain points, and positive feedback per segment
- Sentiment Scoring: Assign sentiment scores (-1 to +1) for overall satisfaction per segment
- Impact Assessment: Prioritize insights by frequency, severity, and business impact
- Synthesis: Create segment profiles with consolidated insights
Output Structure
For each identified segment:
Segment Profile
- Name/identifier and common characteristics
- User count or proportion in feedback dataset
- Primary use case or context
Jobs-to-be-Done
- Core job this segment is trying to accomplish
- Associated desired outcomes
Sentiment Score & Satisfaction Level
- Overall sentiment score (-1 to +1)
- Key satisfaction drivers and detractors
- Net Promoter Score (NPS) proxy if applicable
Top Positive Feedback Themes
- What this segment loves about $ARGUMENTS
- Key strengths from user perspective
- Examples of successful use cases
Top Pain Points & Criticism
- Most frequent complaints or frustrations
- Unmet needs or missing features
- Friction points in user journey
- Direct quotes from feedback when available
Product-Segment Fit Assessment
- How well $ARGUMENTS serves this segment's needs
- Potential to improve fit through product changes
- Risk of churn or dissatisfaction
Actionable Recommendations
- 2-3 highest-impact improvements per segment
- Quick wins vs. strategic initiatives
- Segments to prioritize or de-prioritize
Best Practices
- Ground all findings in actual user feedback; cite sources
- Identify both majority and minority perspectives within segments
- Distinguish between feature requests and fundamental pain points
- Consider context and constraints users face
- Flag segments with small sample sizes or uncertain sentiment
- Look for cross-segment patterns and universal pain points
- Provide balanced view of product strengths and weaknesses