How to publish a Claude Skill

1. Nail the folder structure

A skill is a folder. That folder must contain at minimum:

my-skill/
├── SKILL.md         # required — instructions + frontmatter
├── README.md        # optional but recommended
├── scripts/         # optional — executables the skill can run
│   └── run.sh
└── references/      # optional — extra context files
    └── notes.md

SKILL.md must sit at the root of the folder. When you zip for distribution, zip the contents so SKILL.md lands at the root of the archive — not nested inside another folder.

2. Write a description that actually triggers

The description: field in your frontmatter is the single most important line in the whole skill. It's what the agent uses to decide when to load your skill. Vague descriptions never trigger.

Weak: "Helps with payments."

Strong: "Adds a Stripe Checkout flow with tax handling and success/cancel redirects. Triggers when the user asks to accept payments, build a paywall, add subscriptions, or wire up Stripe."

List the trigger phrases users actually say. Not what the skill does — what people ask for right before they need it.

3. Push to GitHub with the right topics

Public GitHub repo. Add these topics so search finds you:

• claude-skill and claude-skills
• lovable-skill if it targets Lovable specifically
• anthropic-skills for reach across the Claude Code community
• Domain-specific tags: stripe, auth, seo, testing…

A tight README with a one-line "what it does", a copy-paste install snippet, and an example prompt earns you 10× more installs than a wall of text.

4. Ship a release .zip

People install by dragging a .zip into their agent. Make one properly:

cd my-skill
zip -r ../my-skill.zip . -x "*.git*" "node_modules/*"

Attach that .zip to a GitHub Release. Bump the version in SKILL.md frontmatter each time so users know what changed.

5. Submit to the LovableSkills directory

Public directories multiply your reach — most users browse a catalog before they Google. Submit your GitHub URL to the LovableSkills directory and it will appear alongside the other 2,700+ curated skills. Free, no approval fee, and your GitHub repo stays the source of truth.

6. Version like software, not a blog

Skills evolve. Keep a short changelog in your README (or in CHANGELOG.md), use semver for the frontmatter version, and don't silently rewrite behaviour under an old version — you'll break every install downstream.

7. Support what you ship

Open an issues tab. Answer the first ten reports personally. That's where you'll learn what your description got wrong and which edge cases your skill silently misses. The skills that thrive are the ones with a maintainer who cares about the second install.