How to Publish a Lovable Skill

If you have built something reusable in a Lovable project — an auth flow, an admin panel, a Stripe integration — you can turn it into a Lovable Skill other builders can install with one command. Here's the full publishing workflow.

Prerequisites

• A working Lovable project containing the feature you want to extract.
• A GitHub account (skills are stored as repositories).
• 10 minutes.

1. Extract the feature into a skill folder

Create a new directory at the root of your project:

mkdir -p skills/my-skill/{migrations,routes,components,server}

Move (or copy) the relevant files in. Keep imports relative to the skill root — the install agent will rewrite them when applying the skill to a target project.

2. Write SKILL.md

This is the entry point. The Lovable agent reads it to decide what to do during install.

---
name: my-skill
description: One-sentence summary of what this skill adds and when to use it.
category: Auth | Payments | Design | ...
---

## What this skill ships
- Page: /settings
- Tables: settings, user_preferences
- Server fn: getSettings, updateSettings

## Install steps
1. Run the migration in migrations/0001_init.sql
2. Copy routes/, components/, server/ into the target project
3. Add the SETTINGS_SIGNING_KEY secret

## Required secrets
- SETTINGS_SIGNING_KEY (any 32+ char string)

Keep the description sharp — it's what shows on the catalog card and what search engines index.

3. Add a migration

Every schema change goes in migrations/. Number them sequentially and follow the GRANT-then-RLS pattern Lovable Cloud requires:

CREATE TABLE public.settings (...);
GRANT SELECT, INSERT, UPDATE, DELETE ON public.settings TO authenticated;
GRANT ALL ON public.settings TO service_role;
ALTER TABLE public.settings ENABLE ROW LEVEL SECURITY;
CREATE POLICY "Users manage own settings" ON public.settings
  FOR ALL USING (auth.uid() = user_id) WITH CHECK (auth.uid() = user_id);

4. Write the install command

The convention is lovable add <skill-slug>. The agent pulls your repo, runs the migration, copies the files and resolves imports against the target project's alias paths.

5. Submit it to the catalog

Push the skill repo to GitHub, then submit it at /submit. Include:

• Repo URL
• A 60-character tagline
• 3–8 tags (search relies on these)
• One screenshot of the installed feature

The catalog reviews submissions within 48 hours.

Tips for a skill that gets installed

• Keep it focused. One skill = one feature. Auth and billing should be two skills.
• Lean on Lovable Cloud. Skills that use Cloud install cleanly into any project.
• Document required secrets up front. Surprises during install kill the experience.
• Add a CHANGELOG. Builders trust skills that ship updates.

Next steps

• Read What are Lovable Skills for context.
• Browse the catalog to see how other authors structure their skills.
• See Best Claude Skills 2026 for high-quality references.