Claude Code skills for the business side of your startup.
You already have tools for code review, QA, and shipping. But who's doing the brand strategy? Who's running growth experiments? Who's prospecting domains and writing launch playbooks?
laborstack fills the gap. Two specialized skills that handle the work founders usually do at 2am between deploys — brand identity, positioning, growth strategy, SEO, domain research, launch planning. Each one writes real deliverables to your repo, not advice.
Who this is for:
- Solo founders — you're building the product AND the business. These skills handle the business side so you can stay in the terminal.
- Technical cofounders — your non-technical cofounder isn't here yet. laborstack fills the role.
- Side project builders — you built the thing. Now what? Growth Hacker gives you the launch playbook.
| Skill | Your specialist | What they do | Output |
|---|---|---|---|
/brand-manager |
Brand Strategist | Positioning, voice guidelines, messaging framework, content pillars, real content samples (tweets, landing page, cold emails) | BRAND.md |
/growth-hacker |
Growth Operator | Growth experiments, domain prospecting, SEO audit, channel analysis, launch playbooks, funnel optimization | GROWTH.md |
Install (30 seconds):
git clone https://github.com/OpenLabor/laborstack.git ~/.claude/skills/laborstackAdd to your project's .claude/settings.json:
{
"skills": ["~/.claude/skills/laborstack"]
}First run (5 minutes):
- Run
/brand-manager— it reads your README and codebase, asks one focused question, then builds your full brand identity - Run
/growth-hacker— it figures out your stage, proposes the highest-leverage growth move, and writes the playbook
That's it. Two commands, two strategy docs in your repo.
You: /brand-manager
Claude: I've read your README, package.json, and the tweets in brand/.
Here's what I understand: you're building an open-source platform
for AI employees...
Your current positioning — "AI employees" — sounds like every
other AI agent company. Let me push on that.
What's ACTUALLY different is the Markdown-native approach.
EMPLOYEE.md + SKILL.md is a genuinely new primitive.
RECOMMENDATION: Position around the format, not the category.
"The open standard for AI workers" > "AI employee platform"
[proposes full brand: personality, voice, messaging, content pillars]
[writes 5 real content pieces: launch thread, landing page, PH tagline]
[writes BRAND.md to repo]
You: /growth-hacker
Claude: You're pre-launch with an open-source project. Different playbook
than SaaS — community-first, not funnel-first.
Your ONE metric right now: GitHub stars → docs page visits → labor.so signups.
That's the funnel. Everything else is noise.
RECOMMENDATION: Ship a Show HN post this week. Here's the exact
playbook, hour by hour...
[proposes 3 growth experiments with hypotheses]
[checks domain availability for 20 candidates]
[writes GROWTH.md with launch checklist]
Each skill is a SKILL.md file with YAML frontmatter — the standard Claude Code skill format. Skills have opinionated personas (they recommend, they don't ask you to pick from a menu), phased workflows, and write concrete files to your repo.
Everything stays in version control. BRAND.md and GROWTH.md become source-of-truth files that future Claude sessions read before writing any marketing copy or proposing growth tactics.
laborstack is built by OpenLabor — the open-source framework for AI employees.
More skills coming soon. Star the repo to follow along.
MIT