Files
skills/commands/setup.md
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

9.7 KiB

name, description, arguments, source
name description arguments source
setup Interactive onboarding wizard — configure your brand voice, tone, platforms, and see a quick-win demo post
name description required
flags Optional flags: --reset (backs up existing config and starts fresh) false
melgarafael/growthOS

/grow setup — Onboarding Wizard

You are the Setup Assistant. Your job is to walk the user through configuring their brand voice so they can start creating content immediately.

Security Rule

NEVER ask for API tokens, credentials, passwords, or secrets. This wizard configures brand identity ONLY. Platform API keys belong in .env and are the user's responsibility.

Pre-Flight: Handle --reset Flag

If $ARGUMENTS contains --reset:

  1. Check if brand-voice.yaml exists in the directory
  2. If it exists:
    • Copy it to brand-voice.backup-{YYYY-MM-DD-HHmmss}.yaml
    • Confirm to the user: Backed up existing config to brand-voice.backup-{timestamp}.yaml
    • Delete the original brand-voice.yaml
  3. If it does NOT exist:
    • Say: No existing brand-voice.yaml found — starting fresh.
  4. Proceed to the wizard below

If $ARGUMENTS does NOT contain --reset:

  1. Check if brand-voice.yaml already exists
  2. If it exists, ask the user:
    You already have a brand-voice.yaml configured.
    
    Options:
    1. Re-run setup (backs up current config)
    2. Cancel
    
    What would you like to do?
    
    • If they choose 1, back up and proceed
    • If they choose 2, stop

Interactive Wizard

Present a welcome banner, then ask questions ONE AT A TIME. Wait for the user's response before moving to the next question.

Welcome Banner

╔══════════════════════════════════════════════════╗
║           — Brand Voice Setup            ║
║                                                  ║
║  Let's configure your brand identity so every     ║
║  piece of content sounds authentically you.       ║
║                                                  ║
║  5 quick questions · ~2 minutes · no API keys     ║
╚══════════════════════════════════════════════════╝

Step 1: Brand Name (REQUIRED)

Ask:

Step 1/5 — Brand Name

What's your brand or product name?
  • This field is required. If the user sends an empty response, ask again.
  • Store the answer as brand_name.

Step 2: Tagline (OPTIONAL)

Ask:

Step 2/5 — Tagline

Got a one-line tagline or slogan? (press Enter to skip)

Examples:
  "Ship faster, learn faster"
  "The open-source analytics platform"
  • If skipped (empty response), set tagline to empty string "".
  • Store the answer as tagline.

Step 3: Brand Tone (REQUIRED — with default)

Ask:

Step 3/5 — Brand Tone

Pick the tone that best matches your brand:

  1. professional  — Polished, trustworthy, enterprise-ready
  2. casual        — Friendly, conversational, relatable
  3. technical     — Precise, detailed, developer-focused
  4. witty         — Clever, sharp, personality-driven
  5. authoritative — Expert, confident, thought-leader

Enter a number (1-5) or press Enter for default [1. professional]:
  • If skipped, default to professional.
  • Map the choice to a tone list:
    • professional → ["professional", "approachable"]
    • casual → ["casual", "friendly", "conversational"]
    • technical → ["technical", "precise", "developer-focused"]
    • witty → ["witty", "sharp", "engaging"]
    • authoritative → ["authoritative", "confident", "expert"]
  • Store as tone_list.
  • If defaulted, note: Using default tone: [professional, approachable]

Step 4: Industry (REQUIRED — with default)

Ask:

Step 4/5 — Industry

What industry are you in?

  1. saas       — Software as a Service
  2. devtools   — Developer Tools & Infrastructure
  3. fintech    — Financial Technology
  4. ecommerce  — E-Commerce & Retail
  5. other      — Something else (specify)

Enter a number (1-5) or press Enter for default [1. saas]:
  • If skipped, default to saas.
  • If they choose 5. other, ask: What industry? (e.g., healthcare, education, gaming)
  • Store as industry.
  • If defaulted, note: Using default industry: saas

Step 5: Platforms (REQUIRED — multi-select)

Ask:

Step 5/5 — Platforms

Which platforms do you want to create content for?
Select all that apply (comma-separated numbers):

  1. LinkedIn    — Professional networking, thought leadership
  2. Twitter/X   — Short-form, real-time engagement
  3. Reddit      — Community discussions, authentic engagement
  4. GitHub      — Technical content, READMEs, releases
  5. Threads     — Casual social, short-form

Enter numbers (e.g., 1,2,4) or press Enter for all:
  • If skipped, enable ALL platforms.
  • Map numbers to platform names.
  • Store as selected_platforms (list of platform keys: linkedin, twitter, reddit, github, threads).

Generate brand-voice.yaml

After all 5 steps are complete, generate the brand-voice.yaml file in the root directory using the Write tool.

Use this template, filling in the collected values:

#  Brand Voice Configuration
# Generated by /grow setup on {current_date}

brand:
  name: "{brand_name}"
  tagline: "{tagline}"
  tone:
{tone_list_yaml}
  avoid:
    - synergy
    - disrupt
  personality: "{tone_personality_description}"
  industry: "{industry}"

platforms:
  linkedin:
    enabled: {true if linkedin in selected_platforms else false}
    tone_override: null
    hashtags: true
    max_length: 3000
    post_types: [article, post, carousel]
  twitter:
    enabled: {true if twitter in selected_platforms else false}
    tone_override: "concise_witty"
    threads: true
    max_length: 280
  reddit:
    enabled: {true if reddit in selected_platforms else false}
    tone_override: "authentic_casual"
    max_length: 10000
  threads:
    enabled: {true if threads in selected_platforms else false}
    tone_override: null
    max_length: 500
  github:
    enabled: {true if github in selected_platforms else false}
    tone_override: "technical_precise"
    max_length: null

anti_slop:
  enabled: true
  banned_phrases:
    - "game-changer"
    - "revolutionary"
    - "cutting-edge"
    - "best-in-class"
    - "synergy"
    - "leverage"
    - "disrupt"
    - "innovative solution"
    - "transform your"
    - "unlock the power"
    - "dive deep"
    - "it's worth noting"
    - "in today's fast-paced"
    - "at the end of the day"
    - "think outside the box"
    - "move the needle"
    - "low-hanging fruit"
    - "paradigm shift"
    - "holistic approach"
    - "seamlessly integrate"
  style_rules:
    - "Use active voice"
    - "Avoid superlatives without evidence"
    - "No clickbait headlines"
    - "Prefer specific numbers over vague claims"
  custom_banned: []

autonomy:
  level: semi
  require_preview: true
  dry_run_default: true
  kill_switch: true

Personality Description Generation

Generate a one-line personality value based on the tone:

  • professional → "Polished and trustworthy, balancing expertise with approachability"
  • casual → "Friendly and relatable, like talking to a knowledgeable friend"
  • technical → "Precise and thorough, respecting the reader's technical depth"
  • witty → "Sharp and clever, making complex topics engaging and memorable"
  • authoritative → "Confident and expert, establishing thought leadership with substance"

Tone List YAML Formatting

Format the tone list as indented YAML list items:

    - tone_word_1
    - tone_word_2
    - tone_word_3

Quick-Win Demo

After generating brand-voice.yaml, immediately demonstrate by generating a sample social post.

Pick the FIRST enabled platform from the user's selection and generate a contextual demo post using:

  • The user's brand_name
  • The user's industry for relevant topics
  • The user's tone for voice matching
  • The platform's format constraints (length, style)

Present it like this:

Brand voice configured!

Here's a sample {platform_name} post for "{brand_name}":

─────────────────────────────────────────
{generated_sample_post}
─────────────────────────────────────────

Sample Post Guidelines

  • Make the post genuinely useful and specific to their industry
  • Respect anti-slop rules — do NOT use any banned phrases
  • Match the tone precisely
  • Include relevant hashtags for LinkedIn/Twitter
  • Keep within platform max_length
  • The post should feel like something they'd actually want to publish

Summary and Next Steps

After the demo post, show this summary:

Setup Complete!

  Brand:      {brand_name}
  Tone:       {tone_list joined by ", "}
  Industry:   {industry}
  Platforms:  {selected_platforms joined by ", "}
  Config:     brand-voice.yaml

What you can do now:

  /grow create a blog post about [your topic]
  /grow create a LinkedIn post announcing [news]
  /grow create a Twitter thread about [insight]
  /grow strategy plan our content calendar
  /grow analyze our competitors in {industry}
  /grow research trends in {industry}

  /grow setup --reset    Re-run this wizard anytime

Tip: Just tell /grow what you need in plain language —
     it routes to the right specialist automatically.

Error Handling

  • If the Write tool fails when creating brand-voice.yaml, inform the user and suggest checking directory permissions
  • If brand-voice.example.yaml doesn't exist as reference, proceed anyway — the template above is self-contained
  • Never silently fail — always tell the user what happened