MyClaude Docs
MyClaude Docs

Getting Started

QuickstartThe MyClaude MethodConcepts OverviewArchitecturePricing & RevenueGamificationRoadmapFAQGlossaryChangelogSystem Status

Buyers

Creators

CLI

API

Agent Integration

Developers

Security

Legal

Getting Started

Concepts Overview

MyClaude is the universal marketplace for the Claude Code ecosystem, supporting 9 product categories from simple prompts to complete agent squads.

Explanation

Every Claude Code project eventually builds something reusable — a skill, an agent config, a workflow. MyClaude is the marketplace that turns those artifacts into installable, searchable, monetizable products. One command to install, one command to publish, 92% of revenue goes to creators.

What is MyClaude?

MyClaude is the only marketplace purpose-built for the Claude Code ecosystem. It provides what free directories cannot: content security scanning (22 malicious pattern detectors), purchase-verified reviews, Stripe Connect payments, a dedicated CLI with 12 commands, and 11 machine-readable specs for AI agent integration. Creators publish reusable components — skills, agents, squads, workflows, and 5 more categories — that other developers install with myclaude install @creator/product. Creators receive 92% of each sale, the highest revenue share in any AI tool marketplace (Apple App Store takes 30%, most SaaS marketplaces take 20-40%).

The 9 product categories

Each category targets a different layer of the Claude Code ecosystem:

CategoryDefinitionExample
SkillsCallable prompt routines stored in .claude/skills/ that extend Claude Code with domain-specific capabilities./commit, /review-pr, /aegis
SquadsMulti-agent teams with coordinated workflows, enabling complex tasks through agent collaboration.Copy Squad (15 specialized agents)
AgentsSingle-purpose AI agents with specialized knowledge and defined tool access.Security Auditor, Code Reviewer
WorkflowsMulti-step automation pipelines that chain tools, agents, and skills into repeatable processes.CI/CD pipeline, deploy workflow
Design SystemsComplete token sets, component libraries, and design rules for consistent UI development.Terminal Dark DS, Brand Kit
PromptsReusable system prompts and templates optimized for specific tasks or domains.Legal contract analyzer
CLAUDE.mdProject configuration files with rules, context, and behavioral directives for Claude Code.Enterprise compliance config
ApplicationsFull applications built for/with Claude Code, ready to deploy.Dashboard generator, API scaffolder

How the marketplace works

The lifecycle of every MyClaude product follows 5 steps:

Create  →  Publish  →  Discover  →  Install  →  Use
  1. Create — Build a skill, agent, squad, or any product type using the Creator Engine or manually
  2. Publish — Define a vault.yaml manifest and run myclaude publish from the CLI
  3. Discover — Browse on myclaude.sh/explore, search with myclaude search, or find via AI engines
  4. Install — Run myclaude install @creator/product-name to add it to your environment
  5. Use — The product is active in your Claude Code session immediately

Key concepts

vault.yaml — Every product has a manifest file. It defines name, version, category, pricing, and configuration in 9-15 lines of YAML. Think of it as package.json for Claude Code products. Full specification.

CONDUIT — The publishing pipeline that connects Creator Engine to CLI to marketplace API. Handles validation, content scanning, and listing creation automatically.

MCS (MyClaude Certified Standard) — A quality badge for products that pass automated and manual review. MCS-certified products appear higher in search results and receive a verification badge.

For buyers vs. for creators

BuyersCreators
GoalFind and use quality toolsBuild and monetize tools
Start hereQuickstartCreator Onboarding
Key actionmyclaude install @creator/productmyclaude publish
RevenuePay per product or use free productsReceive 92% of each sale
Quality signalLook for MCS badgeEarn MCS certification

Related pages

  • Quickstart — install and start using MyClaude in 5 minutes
  • Product Types Explained — detailed category definitions
  • Glossary — all terms defined

The MyClaude Method

What MyClaude believes, why it exists, and the principles behind every decision — from agent-first architecture to 92% creator revenue share.

Architecture

How MyClaude is built: Next.js 16 with dual Firebase SDKs, Stripe Connect payments, Cloudflare R2 storage, and the CONDUIT publishing pipeline.

On this page

What is MyClaude?The 9 product categoriesHow the marketplace worksKey conceptsFor buyers vs. for creatorsRelated pages