Building Bundles

Curate multi-product collections that deliver more together than apart. Package your skills, minds, and workflows into a single install — the complete toolkit buyers actually need.

Bundles are the highest-converting products on MyClaude. The reason is simple: buyers face friction. They browse categories, read descriptions, compare options, decide item by item. A Bundle eliminates that friction. You've already made the curation decisions. Buyers get a coherent toolkit — everything they need for a specific job, assembled by someone who understands the domain.

If you've published multiple products that work well together, a Bundle is the natural next step. If you're building a practice as a consultant or educator, a Bundle is how you package your complete methodology.

What is a Bundle?

A Bundle is a vault.yaml manifest that references other products by their slugs. When a buyer installs your Bundle, they get all included products in a single command. There's no separate content to write — the Bundle is the curation.

The difference between a Bundle and a product listing: a listing is one thing. A Bundle is a curated experience. The value is in the combination, the sequencing, the decision that these specific products belong together.

Who creates Bundles?

You don't need to be a developer. You need to understand what practitioners in your domain actually need.

• Consultants — package a complete client engagement toolkit: project setup, analysis frameworks, reporting templates
• Educators — bundle a course's full toolset: thinking frameworks, exercise prompts, evaluation rubrics
• Agency owners — create starter packs for each service line: SEO bundle, content bundle, growth bundle
• Community builders — curate the best tools from their ecosystem for newcomers
• Power users — assemble the combination they personally use every day and wish existed sooner
• Domain experts — package everything a professional in their field needs to get started fast

If you can answer "if I were starting this work today, here's exactly what I'd install" — you can build a Bundle.

Create your first Bundle

Let's build a content creator toolkit Bundle. Concrete, complete, immediately valuable.

Prerequisite: publish your constituent products

A Bundle references products that already exist on MyClaude. Before building the Bundle, your individual skills, minds, and workflows need to be live. If you're starting fresh, build those first — then come back to bundle them.

If you want to include products from other creators, you can reference any public product slug (check licensing terms on the product page first).

Scaffold the Bundle

$ myclaude init content-creator-kit --type bundle
$ cd content-creator-kit

A Bundle scaffold contains just vault.yaml — there's no SKILLS.md or MINDS.md to write. The value is in the manifest.

Wire vault.yaml with bundle.includes

This is the heart of a Bundle — the bundle.includes list:

name: content-creator-kit
version: 1.0.0
type: bundle
title: "Content Creator Kit — Complete Toolkit for AI-Assisted Creation"
description: "Everything a content creator needs in one install. Research frameworks, editorial mind, SEO workflow, repurposing skills, and a content calendar template — assembled and tested as a complete system."
price: 49.99
tags:
  - content
  - marketing
  - writing
  - seo
  - workflow

bundle:
  includes:
    - content-research-skill
    - editorial-mind
    - seo-audit-workflow
    - thread-repurpose-skill
    - newsletter-skill
    - content-calendar-template
  recommended_order:
    - editorial-mind
    - content-research-skill
    - content-calendar-template
    - seo-audit-workflow
    - thread-repurpose-skill
    - newsletter-skill

The recommended_order field helps buyers understand the sequence — which product to install and engage with first.

Write the Bundle README

Unlike other product types, Bundles benefit enormously from a README.md that explains the collection strategy:

# Content Creator Kit

## What's included and why

**Editorial Mind** — Install this first. It shapes how Claude thinks about
content: what makes a story worth telling, how to find the angle, when to
kill a piece that isn't working.

**Content Research Skill** — Deep research on any topic. Synthesizes sources,
identifies gaps, generates interview questions. Used at the start of every piece.

**Content Calendar Template** — The operational layer. Plan months of content,
track production status, balance content types.

**SEO Audit Workflow** — After drafting, run every piece through this. Keyword
opportunities, internal linking, meta descriptions.

**Thread Repurpose Skill** — Transform long-form pieces into Twitter/X threads,
LinkedIn posts, newsletter sections. One piece, five formats.

**Newsletter Skill** — End-to-end newsletter production: curation, writing,
subject line testing, send optimization.

## The complete workflow

1. Plan: Content Calendar → what are we making this month?
2. Research: Content Research Skill → what do we actually know?
3. Write: Editorial Mind active → Claude thinks like an editor
4. Optimize: SEO Audit Workflow → is this findable?
5. Distribute: Thread Repurpose + Newsletter Skill → everywhere it belongs

## Who this is for

Creators publishing 4+ pieces per month who want Claude Code as a genuine
editorial partner, not just a writing assistant.

Test locally

Install your own Bundle and go through the complete workflow:

$ myclaude validate
# Check that all referenced slugs exist and are accessible

$ mkdir -p .claude/skills/
# Install each constituent product manually to test the combined experience

Work through a real task using all the products together. The test is: does the combination feel greater than the sum of its parts? If products feel redundant or create friction together, reconsider the curation.

Publish

$ myclaude validate
$ myclaude publish

Your Bundle is now live on MyClaude.

What makes a great Bundle

The difference between a bundle that converts and one that sits unsold:

Great Bundles tell a story. The story is: here's a job that's hard to do well, here's the complete system for doing it, and here's why this combination works. A buyer should read your Bundle description and think "this person understands exactly what I'm trying to do."

Pricing your Bundle

The standard approach:

• Sum individual prices: Add up what each constituent product costs separately
• Apply a discount: 20-35% off the sum is the range where Bundles convert well
• Price for the outcome, not the contents: A Bundle that saves 10 hours per month is worth more than the sum of its parts

Example: five products at $9.99 each = $49.95 individually. Bundle at $34.99 (30% off). The buyer saves $15, you get a larger single transaction, and the outcome is framed as a complete system.

Advanced: Bundles across creators

You can reference products from other creators in your Bundle. This enables:

• Ecosystem packs: "The best tools for [framework] development, curated"
• Partner bundles: Collaborative collections with complementary creators
• Starter packs: Onboarding collections for communities or teams

When including others' products, you earn commission on your Bundle sale but the constituent products are fulfilled at their original prices. Check each product's licensing before including it — most public products allow bundling, but confirm.

Common questions

Do I need to own all products in a Bundle?

No. You can include any public product on MyClaude. When a buyer purchases your Bundle, they get access to all included products. You receive the Bundle sale. The original creators receive their product's value as part of the Bundle economics.

Can I update a Bundle after publishing?

Yes. Publish an update to your vault.yaml with version: 1.1.0 and an updated bundle.includes list. Buyers who installed the previous version will be notified of the update.

What if a constituent product gets removed from MyClaude?

If a product you reference is taken down, myclaude validate will flag the broken reference. Update your Bundle to replace or remove the missing product before publishing the next version.

Should I bundle free products with paid ones?

Yes, if they add value to the collection. Free products in a Bundle don't reduce the Bundle's value — they increase it. Buyers appreciate a complete toolkit that includes the best tools regardless of price.

Related pages

• Writing Skills — build the constituent skills for your bundle
• Building Minds — build the minds that power your collection
• Building Workflows — workflows are natural bundle components
• Monetization — pricing strategies for bundles and collections
• Publishing Guide — the basics of getting any product live