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.9 KiB
4.9 KiB
name, description, source
| name | description | source |
|---|---|---|
| cohort-analysis | Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends. | phuryn/pm-skills |
Cohort Analysis & Retention Explorer
Purpose
Analyze user engagement and retention patterns by cohort to identify trends in user behavior, feature adoption, and long-term engagement. Combine quantitative insights with qualitative research recommendations.
How It Works
Step 1: Read and Validate Your Data
- Accept CSV, Excel, or JSON data files with user cohort information
- Verify data structure: cohort identifier, time periods, engagement metrics
- Check for missing values and data quality issues
- Summarize key statistics (cohort sizes, date ranges, metrics available)
Step 2: Generate Quantitative Analysis
- Calculate cohort retention rates and engagement trends
- Identify retention curves, drop-off patterns, and anomalies
- Compute feature adoption rates across cohorts
- Calculate month-over-month or period-over-period changes
- Generate Python analysis scripts using pandas and numpy if requested
Step 3: Create Visualizations
- Generate retention heatmaps (cohorts vs. time periods)
- Create line charts showing cohort progression
- Build comparison charts for feature adoption
- Visualize drop-off points and engagement trends
- Output as interactive charts or static images
Step 4: Identify Insights & Patterns
- Spot one or more significant patterns:
- Early churn in specific cohorts
- Late-stage engagement changes
- Feature adoption clusters
- Seasonal or temporal trends
- Highlight surprising findings and deviations
- Compare cohort performance to establish baselines
Step 5: Suggest Follow-Up Research
- Recommend qualitative research methods:
- Targeted user interviews with churning users
- Feature usage surveys with engaged cohorts
- Session replays of key interaction patterns
- Win/loss analysis for high vs. low retention cohorts
- Design follow-up quantitative studies
- Suggest A/B tests or feature experiments
Usage Examples
Example 1: Upload CSV Data
Upload cohort_engagement.csv with columns: cohort_month, weeks_active,
user_id, feature_x_usage, engagement_score
Request: "Analyze retention patterns and identify why Q4 2025 cohorts
underperform compared to Q3"
Example 2: Describe Data Format
"I have monthly user cohorts from Jan-Dec 2025. Each row shows:
cohort date, user ID, purchase frequency, and support tickets.
Analyze which cohorts show best long-term retention."
Example 3: Feature Adoption Analysis
Upload feature_usage.xlsx with cohort adoption data.
Request: "Compare adoption curves for our new feature across cohorts.
Which cohorts adopted fastest? Any patterns?"
Key Capabilities
- Data Reading: Import CSV, Excel, JSON, SQL query results
- Retention Analysis: Calculate and visualize retention rates over time
- Cohort Comparison: Compare metrics across cohort groups
- Anomaly Detection: Flag unusual patterns or drop-offs
- Python Scripts: Generate reusable analysis code for ongoing analysis
- Visualizations: Create heatmaps, charts, and interactive dashboards
- Research Design: Suggest targeted follow-up studies and interview approaches
- Statistical Summary: Provide quantitative metrics and correlation analysis
Tips for Best Results
- Include time dimension: Provide data across multiple time periods
- Define cohort clearly: Make cohort grouping explicit (signup month, feature launch date, etc.)
- Provide context: Explain product changes, launches, or events during the period
- Multiple metrics: Include retention, engagement, feature usage, revenue, etc.
- Sufficient data: At least 3-4 cohorts for meaningful pattern identification
- Request specific output: Ask for visualizations, Python scripts, or research recommendations
Output Format
You'll receive:
- Data Summary: Cohort overview and data quality assessment
- Quantitative Findings: Key metrics, retention rates, and trend analysis
- Visualizations: Charts showing retention curves, adoption patterns
- Pattern Identification: 2-3 significant insights from the data
- Research Recommendations: Specific qualitative and quantitative follow-ups
- Analysis Scripts (if requested): Python code for reproducible analysis
- Next Steps: Prioritized actions based on findings