The Solopreneur Skill Stack
The Setup
I run two businesses (consulting + bakery), write a book, teach Claude, manage a household, post daily on social media, and maintain a portfolio of apps and tools. There is no team. There’s me, Claude, and a carefully built system that makes one person look like five.
The question I kept asking: what would a fully-staffed version of my business look like? If I had a content director, a financial advisor, a brand strategist, a social media manager, a proposal writer, a recipe consultant, and an editorial team — what would they each do?
Then I built all of them.
The Build
The skill stack is 21+ custom Claude Cowork skills, each designed for a specific function across my two businesses and personal brand. Together, they form an operating system for a solo operator.
For Hazel Q (consulting/teaching):
- Advisory Panel — 25-expert board for business decisions
- Content Lab — 22-agent content engine for blog posts and guides
- Creative Studio — 23-member team for brand direction, sales copy, and CRO
- Proposal Writer — call transcript to send-ready proposal
- Field Notes Rewriter — voice transplant for AI-generated drafts
- Playbook Builder — creates Claude playbooks for the site
For Ube MKE (bakery):
- Advisory Board — 33-expert business strategy board
- Kitchen Board — 26-expert baking and food ops
- Content Lab — weekly social content planning engine
- Creative Lab — 29-member merch and ideas room
- UI Review — 16-agent website audit
For daily operations:
- Threads Things — full Threads engagement workflow
- Add Event — Google Calendar integration for events
- Skill Creator — builds and improves new skills
The connective tissue: Every skill loads from the same dossier system — markdown files that contain my business context, brand voice, pricing, current projects, and decision filters. When the Advisory Panel considers a new project, it checks the same decision filter the Kitchen Board uses. When the Content Lab writes a blog post, it uses the same voice rules the Proposal Writer follows.
The skills don’t just work individually. They share context. They reference the same source of truth. That’s what makes it a system instead of a collection of tools.
The Mess
The biggest mess was building skills that worked in isolation but contradicted each other. The Advisory Panel would say “focus on the book” while the Content Lab was planning blog posts, and the Creative Studio was designing a new course offering. Each skill was doing its job. But nobody was coordinating.
The fix was the brain file — CLAUDE.md — which acts as the master context for every skill. It contains my current focus, active projects, parked projects, and the explicit rule: “Check Current Focus before suggesting new work.” Now every skill knows what quarter we’re in, what the priorities are, and what’s been intentionally parked.
The other mess: skill sprawl. I built too many skills too fast. Some overlapped. Some were too niche to justify their own skill. Some solved a problem I had once and never had again. I’ve consolidated and killed skills along the way. The current 21+ are the survivors — the ones that earn their spot through regular use.
The Result
On any given day, I might use 3-5 skills. The Advisory Panel before a big decision. The Content Lab for a blog post. The Threads workflow for daily engagement. The Kitchen Board for batch planning. The Proposal Writer after a discovery call.
The system handles the parts of running a business that are repetitive, context-heavy, or require multiple perspectives. I handle the parts that require taste, relationships, and judgment. The split isn’t 50/50 — it’s more like 30/70 in favor of things I still do myself. But that 30% the system handles is the 30% that used to drain my energy and eat my mornings.
For teaching, the skill stack is the ultimate artifact. When someone asks “what can you actually build with Claude?” I don’t give a demo. I show them the system that runs my life.
The Takeaway
One person with a well-built AI system doesn’t need a team. They need taste, judgment, and the willingness to build the machine instead of doing everything by hand.
How It’s Built
- Platform: Claude Cowork
- Skills: 21+ custom skills across two businesses + personal brand
- Context system: Dossier files (markdown) + CLAUDE.md brain file
- Maintenance: Skills get updated, consolidated, or retired quarterly
- Cost: Claude subscription
- Time to build: ~6 months of iterative development