Publishing Your First Product

Publish your first MyClaude product in under 5 minutes with myclaude init and myclaude publish. Creators keep 92% of every sale — the highest revenue share of any AI tool marketplace. Free products have zero fees.

MyClaude is the only Claude Code marketplace where you can sell skills, agents, squads, and workflows with real payments via Stripe Connect. Every product is security-scanned with 22 malicious pattern detectors before listing. This tutorial takes you from zero to a live product listing — scaffold, edit, publish.

Prerequisites

Before publishing you need:

• A MyClaude creator account — Create one here or follow Creator Onboarding
• The CLI installed and authenticated — npm install -g @myclaude-cli/cli then myclaude login
• A Stripe account connected if you want a paid product — free products skip this

Check you are authenticated:

$ myclaude whoami
# Logged in as @your-username

If you see an error, run myclaude login first.

Step 1 — Scaffold with myclaude init

Pick a directory name for your product. Convention is lowercase with hyphens.

$ myclaude init my-first-skill
$ cd my-first-skill

myclaude init creates this structure:

my-first-skill/
  SKILL.md       # Your product content
  vault.yaml     # Your product manifest

Two files. That is the entire structure for a Skill. Other categories add files — see Product Categories — but vault.yaml is always required.

Step 2 — Edit vault.yaml

Open vault.yaml. The scaffolded file looks like this:

name: my-first-skill
version: "1.0.0"
category: skill
description: "A short description of what this skill does."
author: your-username
license: MIT
price: 0

Edit the fields to describe your product accurately:

name: my-first-skill
version: "1.0.0"
category: skill
description: "Does X, enabling Y. Invoke with /my-first-skill."
author: your-username
license: MIT
price: 0
tags: [productivity, workflow]

Keep description under 160 characters — it appears in search results. See vault.yaml Specification for every available field.

Step 3 — Edit your product files

Open SKILL.md. This is the content file Claude Code receives when a buyer installs your product. Write it as if you are giving Claude a detailed briefing on a new capability.

A minimal SKILL.md has three sections:

## When to use this skill
[One sentence: what triggers this skill.]

## When NOT to use this skill
[One sentence: clear exclusion criteria.]

## Instructions
[The actual prompt logic, examples, and behavioral rules.]

See Writing Skills Guide for a full walkthrough of what makes a skill effective. For other product types, see Product Categories.

Step 4 — myclaude publish

From inside your product directory:

$ myclaude publish

The CLI runs a pre-publish checklist:

1. Validates vault.yaml structure and required fields
2. Scans content for policy violations
3. Checks you are authenticated
4. Uploads files to MyClaude storage
5. Creates the marketplace listing

A successful publish looks like:

Validating vault.yaml... OK
Scanning content... OK
Uploading files... OK
Creating listing... OK

Published: myclaude.sh/p/your-username-my-first-skill

If validation fails, the CLI prints the specific field or rule that failed. Fix it and re-run myclaude publish.

Step 5 — Verify on marketplace

Open the URL printed by the CLI. Your product page shows:

• Name, description, and category
• Price (free or paid)
• Install command for buyers
• Your creator profile link

Check that the description renders correctly, the category badge is right, and the price is what you intended. If anything looks wrong, edit vault.yaml locally and run myclaude publish again — publish is idempotent, it updates the existing listing.

What happens next

Your product is now discoverable at myclaude.sh/explore and via myclaude search. Buyers can install it immediately.

# What buyers run to install your product
$ myclaude install @your-username/my-first-skill

When a buyer installs your product, the files land in their .claude/skills/ directory (for skills) and are active in their next Claude Code session.

Common errors

Related pages

• vault.yaml Specification — every field, type, and default
• Writing Skills Guide — how to write effective SKILL.md content
• Product Categories — file structures for all 9 categories