[[{“value”:”

Hey AI Breakers πŸ‘‹

You have already built skills for your own business. Here is the part nobody tells you: a skill is a file that runs in 30+ different AI tools, which makes it a product, not just a shortcut.

Today, you’ll build an AI Skill Publisher that turns one workflow you already own into something you can actually list, price, and sell.

  • βœ… A scored shortlist of which of your workflows is genuinely sellable

  • βœ… A spec-compliant SKILL.md that installs cleanly everywhere

  • βœ… A named buyer, in their own words, with a before and after

  • βœ… Three price points with a defensible reason behind each

  • βœ… Listing copy that survives a 10-second skim

  • βœ… A distribution and update plan so version two writes itself

Let’s build it πŸ‘‡


🧠 Why a Skill Is a Product (and a Prompt Is Not)

Anthropic published Agent Skills as an open standard in December 2025. It is not locked to Claude.

As of March 2026, roughly 32 tools read the same format:

  • 🟣 Anthropic Claude Code and the Claude apps

  • 🟒 OpenAI Codex CLI and ChatGPT

  • πŸ”΅ Microsoft VS Code and GitHub Copilot

  • πŸ”΄ Google Gemini CLI

  • ⚫ Plus JetBrains, AWS, Sourcegraph, Databricks, Mistral and others

That is the whole business case. You write one file. It runs across most of the AI tooling your buyer already pays for.

The old way: sell a prompt pack, watch it get copy-pasted into a free Notion doc within a week.

The skill way: ship an installable asset that sits inside the buyer’s tool and fires automatically when it is relevant.

The pipeline: find the asset β†’ package it β†’ name the buyer β†’ price it β†’ write the listing β†’ distribute and version it.

Set aside 60 minutes. You will finish with a real file and a real plan.


πŸ”Ž Prompt #1 β†’ The Asset Finder (which workflow is actually worth selling)

Most people pick the wrong thing to sell. They pick the workflow they are proudest of, not the one someone else is stuck on.

The goal:

  • Inventory the processes you repeat

  • Score each on demand, defensibility, and how easy it is to package

  • Kill the ones that are really just a single clever prompt

βœ… Use this to pick one winner before you write a single line of the file.

Prompt:

You are a digital product strategist who specializes in turning
operator workflows into small, installable software products.

MY CONTEXT:
- What I do: [YOUR ROLE / BUSINESS]
- Who I serve: [YOUR CUSTOMERS OR AUDIENCE]
- Tools I use daily: [LIST YOUR TOOLS]

REPEATED PROCESSES I ALREADY OWN:
[List 5 to 10 things you do the same way every time. Be specific.
Example: "I rewrite client case studies into 3 LinkedIn posts using
a fixed structure" not "I do content."]

YOUR TASK:

1. For each process, score it 1 to 5 on:
   - PAIN: how badly does someone else feel this problem
   - FREQUENCY: how often do they hit it (weekly beats yearly)
   - PACKAGEABLE: can it be captured as written instructions plus
     a few reference files, with no custom software
   - DEFENSIBLE: does it encode judgment or taste that is hard to
     copy from a YouTube video
   - PROOF: do I have evidence it works (results, before and after,
     a track record)

2. Flag anything that is really just ONE clever prompt.
   Say so plainly. Those do not sell as skills.

3. Flag anything that needs live API access, a database, or
   custom code to work. Those are apps, not skills. Say so.

4. Rank the survivors and pick the TOP ONE.
   Explain in 3 sentences why it wins.

5. For the winner, write a one-line "job to be done" in the
   buyer's words, not mine. Start it with "Help me..."

Be blunt. If nothing here is sellable, say that and tell me what
is missing.

πŸ’‘ Tip: If the model tells you nothing is sellable yet, that is the most useful output on this page. The usual gap is PROOF, and the fix is running your own workflow publicly for a few weeks before you charge for it.


🧱 Prompt #2 β†’ The Skill Packager (your workflow becomes a real file)

Now we turn the winner into an actual SKILL.md. The format is strict in exactly two places and loose everywhere else.

The goal:

  • Frontmatter that passes validation in every tool

  • A description that makes the skill fire at the right moment

  • Body instructions detailed enough that a stranger gets your result

βœ… Use this to produce the file you will actually ship.

Prompt:


Read more

“}]] Read MoreΒ in Β The AI BreakΒ