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]>
3.9 KiB
3.9 KiB
name, description, source
| name | description | source |
|---|---|---|
| dummy-dataset | Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos. | phuryn/pm-skills |
Dummy Dataset Generation
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Creates executable scripts or direct data files for immediate use.
Use when: Creating test data, generating sample datasets, building realistic mock data for development, or populating test environments.
Arguments:
$PRODUCT: The product or system name$DATASET_TYPE: Type of data (e.g., customer feedback, transactions, user profiles)$ROWS: Number of rows to generate (default: 100)$COLUMNS: Specific columns or fields to include$FORMAT: Output format (CSV, JSON, SQL, Python script)$CONSTRAINTS: Additional constraints or business rules
Step-by-Step Process
- Identify dataset type - Understand the data domain
- Define column specifications - Names, data types, and value ranges
- Determine row count - How many sample records needed
- Select output format - CSV, JSON, SQL INSERT, or Python script
- Apply realistic patterns - Ensure data looks authentic and valid
- Add business constraints - Respect business logic and relationships
- Generate or script data - Create executable output
- Validate output - Ensure data quality and completeness
Template: Python Script Output
import csv
import json
from datetime import datetime, timedelta
import random
# Configuration
ROWS = $ROWS
FILENAME = "$DATASET_TYPE.csv"
# Column definitions with realistic value generators
columns = {
"id": "auto-increment",
"name": "first_last_name",
"email": "email",
"created_at": "timestamp",
# Add more columns...
}
def generate_dataset():
"""Generate realistic dummy dataset"""
data = []
for i in range(1, ROWS + 1):
record = {
"id": f"U{i:06d}",
# Generate values based on column definitions
}
data.append(record)
return data
def save_as_csv(data, filename):
"""Save dataset as CSV"""
with open(filename, 'w', newline='') as f:
writer = csv.DictWriter(f, fieldnames=data[0].keys())
writer.writeheader()
writer.writerows(data)
if __name__ == "__main__":
dataset = generate_dataset()
save_as_csv(dataset, FILENAME)
print(f"Generated {len(dataset)} records in {FILENAME}")
Example Dataset Specification
Dataset Type: Customer Feedback
Columns:
- feedback_id (auto-increment, U001, U002...)
- customer_name (realistic names)
- email (valid email format)
- feedback_date (dates last 90 days)
- rating (1-5 stars)
- category (Bug, Feature Request, Complaint, Praise)
- text (realistic feedback)
- product (electronics, clothing, home)
Constraints:
- Ratings skewed: 40% 5-star, 30% 4-star, 20% 3-star, 10% 1-2 star
- Bug category only with ratings 1-3
- Feature requests only with ratings 3-5
- Email domains realistic (gmail, yahoo, company.com)
Output Deliverables
- Ready-to-execute Python script OR direct data file
- CSV file with proper headers and formatting
- JSON file with valid structure and types
- SQL INSERT statements for database population
- Data validation and constraint compliance
- Realistic, business-appropriate values
- Documentation of data generation logic
- Quick-start instructions for using the dataset
Output Formats
CSV: Flat tabular format, easy to import into spreadsheets and databases
JSON: Nested structure, ideal for APIs and NoSQL databases
SQL: INSERT statements, directly executable on relational databases
Python Script: Executable generator for custom or large datasets