Files
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

2.8 KiB

description, argument-hint, source
description argument-hint source
Generate realistic dummy datasets for testing — CSV, JSON, SQL inserts, or Python scripts <description of the data you need> phuryn/pm-skills

/generate-data -- Test Data Generator

Create realistic dummy datasets for development, testing, demos, or prototyping. Outputs as ready-to-use files in your preferred format.

Invocation

/generate-data 1000 users with names, emails, plan tier, signup date, and activity score
/generate-data E-commerce orders dataset: products, customers, timestamps, amounts
/generate-data Sample data matching this schema: [paste table definition]

Workflow

Step 1: Define the Dataset

Understand:

  • What entities? (users, orders, events, products, etc.)
  • What columns? (with data types and constraints)
  • How many rows?
  • Any relationships between tables?
  • Any specific distributions? (e.g., "80% should be on the free plan")
  • Any realistic constraints? (emails should be unique, dates should be chronological)

Step 2: Generate the Data

Apply the dummy-dataset skill:

  • Create a Python script that generates the dataset
  • Use realistic-looking data (not random strings): proper names, valid email formats, real-seeming dates
  • Respect constraints: unique IDs, foreign key relationships, chronological ordering
  • Apply specified distributions
  • Execute the script and produce the output file

Step 3: Deliver

Output in the requested format (or ask):

  • CSV: Most common, works everywhere
  • JSON: For API testing or frontend development
  • SQL INSERT: For populating test databases
  • Python script: For reproducible generation (user can tweak and re-run)
## Generated Dataset: [Description]

**Rows**: [count]
**Columns**: [list]
**Format**: [CSV / JSON / SQL / Python]

### Schema
| Column | Type | Constraints | Distribution |
|--------|------|-----------|-------------|

### Sample (first 5 rows)
[Preview of the data]

### Files
- [data file]
- [generator script, if applicable]

Save data file and generator script to the user's workspace.

Step 4: Offer Follow-ups

  • "Want me to add more columns or increase the dataset size?"
  • "Should I create related tables (e.g., orders for these users)?"
  • "Want me to write test scenarios that use this data?"
  • "Should I create SQL queries to analyze this dataset?"

Notes

  • Always provide the generator script so the user can regenerate with different parameters
  • For demo datasets, make the data tell a story (e.g., seasonal trends, a retention problem, a power user segment)
  • Respect realistic cardinality: 1000 users don't have 1000 unique cities
  • For financial data, use realistic price distributions — not uniform random
  • Never include real personal data — all names, emails, and identifiers must be fake