How to Create and Submit a Skill to CreatorSkills

You've got an AI workflow that saves you time every week. Maybe it's a prompt that turns a raw YouTube transcript into a full repurposing plan. Maybe it's a hook generator tuned to your niche. Maybe it's a brand voice system that keeps your ghostwriter on track.

If another creator would pay $9–$24 to skip the hours of iteration it took you to build that thing — you should list it.

This is the complete guide to building and submitting a skill to the CreatorSkills marketplace. It covers the file format, the quality bar, and how to go from idea to live listing.

---

What Is a Skill, Exactly?

A skill is a markdown file (or a set of markdown files) that turns a general-purpose AI like Claude or ChatGPT into a specialist. When a creator installs a skill, they're loading your instructions directly into their AI tool as a system prompt.

There are no APIs to maintain, no apps to host, no customer support tickets. You write the instructions once. Buyers load them and get results immediately.

Skills come in two formats:

• Single-file skills — one SKILL.md file with all instructions. Works for most use cases.
• Multi-file skills — a ZIP containing multiple .md modules. Better for complex, multi-step workflows that need separate reference files, templates, or examples.

---

The SKILL.md Format

Every skill starts with a SKILL.md file. This is the core system prompt — the instructions your AI follows.

There's no rigid template for the body content. Write the instructions however works best for the skill. What matters is that the instructions are complete, clear, and produce consistent results when a creator loads them into Claude or ChatGPT.

What good skill instructions include

A defined role. Tell the AI what it is and what it's supposed to do. Be specific.

## System Role

You are a YouTube script specialist who helps creators structure compelling
10-minute educational videos. Your job is to turn a topic and a few bullet
points into a full script with a hook, 3 core sections, and a CTA.

Input requirements. Tell the AI exactly what it needs from the creator to do its job well.

## What You Need From the Creator

Before generating the script:
- Video topic (required)
- Target audience (required — e.g. "beginner Python developers")
- Key points to cover (optional — if provided, use them; if not, suggest 3)
- Desired length: short (~5 min) or full (~10 min)

Step-by-step instructions. Break the workflow into explicit steps. Don't assume the AI will figure out the right order.

Output format. Tell the AI exactly what to produce and how to format it. If you want headers, specify headers. If you want code blocks, say so.

Examples. The more concrete your examples, the better the outputs. Good examples are the single biggest lever for skill quality.

Guardrails. Tell the AI what NOT to do. This matters more than most creators expect — guardrails are what makes a skill consistently good instead of occasionally good.

What reviewers look for in SKILL.md

• Does loading this into Claude or ChatGPT immediately make the AI noticeably better at the task?
• Are the instructions specific enough that a creator gets useful output on their first try, without needing to prompt-engineer further?
• Is the output format clear? Would two creators get structurally similar outputs from the same inputs?
• Does the skill avoid generic advice that any creator could write in 5 minutes?

---

metadata.json Schema

Every skill directory needs a metadata.json file. This drives your marketplace listing — the title, description, pricing, and categorization that buyers see.

Here's a fully annotated example:

{
  "name": "YouTube Script System",
  "slug": "youtube-script-system",
  "description": "Turn a topic into a full 10-minute YouTube script in one prompt.",
  "long_description": "Full marketplace listing copy. Lead with the outcome...",
  "category": "SCRIPTS_OUTLINES",
  "platforms": ["CLAUDE", "CHATGPT", "UNIVERSAL"],
  "price": 19,
  "currency": "USD",
  "tags": ["youtube", "scripts", "long-form", "education"],
  "complexity": "standard",
  "files_included": ["SKILL.md", "README.md", "EXAMPLE.md"],
  "external_costs": [],
  "author": "YourName",
  "version": "1.0.0"
}

Field reference

Valid category values

CONTENT_REPURPOSING    Turn long-form content into platform-specific posts, clips, newsletters
TITLES_THUMBNAILS      CTR optimization — titles, thumbnail concepts, A/B frameworks
SCRIPTS_OUTLINES       YouTube scripts, video outlines, shot lists, talking points
ANALYTICS_OPTIMIZATION Channel analytics interpretation, growth strategy, retention analysis
SPONSOR_BRAND_DEALS    Sponsorship research, pitch decks, rate cards, deliverable management
COMMUNITY_ENGAGEMENT   Comment responses, community posts, Discord/Slack management
COURSE_CREATION        Curriculum design, lesson scripts, quiz generation, student onboarding
FREELANCE_CLIENT       Proposals, client onboarding, project briefs, invoice copy, retainer pitches
OTHER                  Use only if none of the above fit

Writing long_description

This is your sales copy. It appears on the skill detail page and is the main thing buyers read before purchasing.

Structure it like this:

1. Lead with the outcome (2–3 sentences) — What does the creator get? Be specific about the result.
2. Key capabilities (bullet list) — 4–6 specific, measurable benefits. Not features — benefits.
3. Perfect for (1–2 sentences) — Name the target creator type.
4. Example — One concrete before/after showing the skill in action.

Example of a strong long_description:

Turn a raw transcript into five ready-to-post Twitter threads, a LinkedIn article,
three Instagram captions, and a newsletter section — in under 5 minutes.

Key capabilities:
- Adapts tone for each platform automatically (casual for Twitter, professional for LinkedIn)
- Preserves your voice from the original transcript
- Generates posting schedule suggestions based on content type
- Works on any transcript length, from 2-minute clips to 2-hour podcasts

Perfect for YouTubers and podcasters who want to maximize the reach of every piece
of content without spending hours on manual repurposing.

Example: Paste a 45-minute podcast transcript. Get back 12 Twitter posts, a 600-word
LinkedIn article, 4 Instagram captions, and a newsletter intro — all in your voice,
ready to schedule.

---

README.md

Every skill should include a README.md. This is the human-readable guide that explains how to install the skill and get the best results from it.

A good README includes:

• What the skill does — 2–3 sentences, outcome-first
• What's included — a simple table of files and their purposes
• How to install — step-by-step for Claude Projects and ChatGPT (cover both)
• First prompts to try — 3–4 copy-paste starter prompts
• Tips for best results — 3–5 practical tips that come from actually using the skill

The Viral Hook Generator README is a good reference for format and tone.

---

Multi-File Skills

Some workflows are too complex for a single instruction file. If your skill has multiple distinct modes, extensive reference material, or separate templates, a multi-file ZIP makes it easier to navigate.

Directory structure

skills/my-skill-name/
├── 01-core-instructions.md   # Main system prompt (loaded first)
├── 02-framework.md           # Reference framework the AI uses
├── 03-templates.md           # Output templates
├── 04-examples.md            # Worked examples
├── README.md                 # Setup guide
└── examples/
    └── worked-example.md     # Full worked example

Prefix module files with numbers to control load order. The AI reads files sequentially — put the most critical instructions first.

The first numbered file (01-core-instructions.md) functions as the primary system prompt. Additional modules are reference files the AI can draw from as needed.

Packaging a multi-file skill

Use the npm run skill:package command to bundle the directory into a ZIP for Supabase Storage:

npx tsx scripts/package-skill.ts content/skills/my-skill-name

This bundles all .md files, uploads the ZIP to Supabase Storage, and generates the fileManifest JSON you'll need for the database record.

In metadata.json, set:

{
  "files_included": ["01-core-instructions.md", "02-framework.md", "README.md", "examples/worked-example.md"]
}

---

Quality Standards

The review bar exists to protect buyers. A rejected skill isn't a failure — it's feedback. Here's what gets approved and what doesn't.

What gets approved

Clear, specific instructions. The AI knows exactly what to do, in what order, with what output format. No ambiguity.

Consistent output. Two different creators using the same inputs should get structurally similar, high-quality results.

Genuine creator value. The skill saves meaningful time or produces results that would take a creator real effort to achieve manually.

Honest positioning. The description matches what the skill actually does. If you say "turn a video into 10 posts," the skill must reliably produce 10 posts — not sometimes 3.

Works without customization. A buyer should be able to load the skill and get value immediately, without needing to heavily adapt the prompts.

What gets rejected

Too vague. "Help me write better content" is not a skill — it's a wish. Every skill needs to do a specific, defined thing.

Generic prompts. If a creator could write this prompt in 5 minutes themselves, it's not worth $9–$24. The value is in the depth, the iteration, and the craft that went into making it work reliably.

Misleading descriptions. If your metadata says the skill produces 15 social posts but it reliably produces 5, it gets rejected.

Untested output. Skills that haven't been tested across multiple inputs are easy to spot. Include real worked examples that show you've actually used it.

Duplicate coverage. We won't list a second YouTube script generator if we already have one that's better. Check the marketplace before building — fill gaps, don't duplicate.

Pre-submission checklist

Before you submit, verify:

• Loaded the skill into Claude or ChatGPT and tested it with 3+ different inputs
• Output is consistent and high-quality across all test cases
• metadata.json matches what the skill actually does
• long_description leads with the outcome, includes specific benefits, and has a real example
• README.md covers installation for both Claude and ChatGPT
• EXAMPLE.md shows at least one fully worked input → output
• Price is appropriate for the value delivered ($9–$24 for most skills)
• No duplicate coverage — checked the marketplace for similar skills

---

Submission Process

Right now, skill submission is via direct outreach. Full self-serve submission is coming.

Step 1 — Check the marketplace. Browse creatorskills.co/skills to confirm you're not duplicating something we already have. If you see a gap in a category, that's your signal.

Step 2 — Build and test your skill. Create the directory structure, write your SKILL.md, metadata.json, README.md, and at least one EXAMPLE.md. Test it with 5+ real inputs. Fix anything that doesn't work consistently.

Step 3 — Review against the checklist above. Honest self-assessment before submission saves everyone time.

Step 4 — Submit. Email skills@creatorskills.co with the subject line "Skill Submission: [Your Skill Name]" and attach or link your skill files.

What to include in your submission email:

• Your skill directory (ZIP or GitHub link)
• 3 test cases showing inputs you used and the outputs you got
• Which category you're targeting and why
• Your requested price

Step 5 — Review. We review submissions within 5 business days. You'll hear back with approval, revision requests, or a pass with specific feedback.

Step 6 — Live. Approved skills are added to the database, priced, and go live within 48 hours of approval.

---

Revenue Sharing

Revenue sharing terms are being finalized. If you're building a skill specifically to list on the marketplace, reach out before you build — we can align on the opportunity and give you advance clarity on terms.

Email skills@creatorskills.co to start the conversation.

---

Frequently Asked Questions

Can I sell the same skill elsewhere? Yes. You retain ownership of your skill content. A CreatorSkills listing is non-exclusive.

What if my skill needs updates? Email us with the updated files and a version bump in metadata.json. We'll push the update within 48 hours.

Can I submit a skill that uses the OpenAI API or other paid services? Yes, but you must disclose external costs in metadata.json under external_costs. Hidden costs are grounds for rejection.

What AI platforms should I target? If your skill works on both Claude and ChatGPT, use UNIVERSAL. If it relies on a feature specific to one platform (like Claude's Projects memory or ChatGPT's browsing), target that platform specifically.

Can I submit a multi-file skill now? Multi-file packaging is supported technically, but the submission process for ZIP-based skills has additional steps. Email us before building multi-file — we'll walk you through the current process.

---

Browse the current catalog at creatorskills.co/skills to see what's already live and where the gaps are. The best skills fill a gap a lot of creators feel.