Define reusable instructions with skills - Lovable Documentation
Documentation Index Fetch the complete documentation index at: /llms.txt Use this file to discover all available pages before exploring further. Skip to main content Assistant Responses are generated using AI and may contain mistakes. Skills let you teach Lovable how to handle recurring tasks. Define a skill once at the workspace level, and Lovable can use it across every project in that workspace. Each skill is a short, named playbook with: a name, a description that tells Lovable when to use it, and markdown instructions that Lovable follows when the skill applies.
You can invoke the skill as a / command paired with your prompt, or let Lovable apply it automatically when the task matches. Skills are portable markdown-based files, so you can inspect exactly what Lovable is being told, share them with teammates, import them from GitHub or ZIP, and improve them over time. Skills vs. instructions Skills and instructions complement each other. Instructions are always included in context.
Use them for rules and conventions that apply to everything Lovable does, such as coding standards, brand guidelines, or your project’s domain terminology. Skills are loaded on demand when the request matches. Use them for instructions that only matter for specific kinds of tasks, such as running a release checklist, drafting a customer reply, or producing a particular kind of content. If an instruction is relevant on every message, put it in workspace instructions.
If it is only relevant when a specific topic comes up, make it a skill. Skills are loaded only when relevant, so you can maintain many focused skills without loading them all into every conversation. Types of skills Skills come in three types. They differ in who manages them and who can use them. Skill type Managed by Who can use it Custom workspace skills Workspace owners and admins, in Workspace settings → Skills Workspace owner, admin, or editor Skills built by Lovable Lovable, nothing for you to set up Workspace owner, admin, or editor Personal skills You, in Account settings → Personal skills Only you, in the workspace you add them to Custom workspace skills are the skills your team adds, shared with every project in the workspace.
Skills you build in the project chat, write yourself, import from GitHub, or upload as a ZIP appear here. Skills built by Lovable are the built-in workspace skills, which every workspace has from the start. They cover common tasks, such as accessibility checks, redesigns, SEO reviews, skill creation, and video creation. Goal , which sets a message as a goal , is listed here too. You can use them when relevant, but you cannot edit, delete, or download them.
Personal skills are your own, private to you in one workspace. You add them yourself, with no admin involved, and no one else can see or use them. Custom workspace skills and skills built by Lovable follow the same permission rules , and Workspace settings → Skills shows them in one list. The list opens on Workspace , which shows the custom ones, and the filter beside the search box switches it to Built-in or All skills .
Personal skills are not in that list, not even under All skills . Custom workspace skills and your own personal skills appear in the Skills list when you type / in a project chat. Lovable can also apply one automatically when your request matches it. What skills are for Skills work best for repeatable, task-specific workflows. Use them when you want Lovable to handle the same kind of task the same way each time. Common examples include: Launch checks : pre-ship checklists, release readiness reviews, and go/no-go reviews Recurring content : release notes, changelog entries, support replies, and marketing copy Review playbooks : landing-page reviews, copy reviews, accessibility passes, and search engine optimization reviews Internal processes : onboarding flow reviews, quality assurance passes, billing setup, and partner handoff steps Task-specific style guides : tone of voice, brand persona, or formatting rules for a particular kind of content Reusable team workflows : research routines, document templates, partner integrations, or other repeated team processes Because skills are shared across the workspace, they are especially useful when you want every project to follow the same process.
Role-based access for skills Access to the skills your workspace shares, both the ones your team adds and the ones built by Lovable, follows your workspace role. Personal skills are the exception: you add your own, with no admin involved. Role Allowed action Workspace owner and admin only Create, edit, delete, and import custom workspace skills (from Skills page, chat, GitHub, or ZIP archive) Enable or disable automatic use for a custom workspace skill across the workspace Workspace owner, admin, or editor View and invoke all skills available to the workspace Download custom workspace skills On Enterprise plans, custom workspace skill changes are recorded in your workspace audit log.
Add a custom workspace skill Workspace owners and admins can add custom workspace skills in five ways. Four options are available from Workspace settings → Skills → Add , and one starts from a project chat after Lovable does something you want to reuse. Build with Lovable Choose Add → Build with Lovable to start a guided skill-building conversation. Lovable opens the dashboard with a starter prompt: Help me create a skill together using /skill-creator.
First ask me what the skill should do. Send the prompt, then answer Lovable’s questions about what the skill should do, when it should trigger, and what instructions it should follow. Lovable drafts the skill for you. When you approve the draft, the skill is published to your workspace. Write manually Choose Add → Write manually to write a skill from scratch. The form has three fields: Name : a short, permanent ID like launch-checklist or support-reply .
Use lowercase letters, numbers, and hyphens only. Description : the trigger Lovable uses to decide when to load the skill. Start with “Use when…” and describe the skill’s scope and boundaries. Content : the instructions Lovable follows once the skill is loaded, such as steps, constraints, examples, and the expected output. Click Add skill to publish it. The skill is available across the workspace immediately. For field requirements, naming rules, and description examples, see Anatomy of a skill .
Import from GitHub Choose Add → Import from GitHub and paste a public GitHub repository URL. A skill is a directory containing a SKILL.md file, and the URL tells Lovable which directory to take. Two forms work: Whole repository , https://github.com/owner/repo . Use this when the repository has one skill, with SKILL.md at the root. Subdirectory , https://github.com/owner/repo/tree/main/launch-checklist . Use this when one repository has several skills.
The directory must contain SKILL.md directly, and any branch works in place of main . A direct file URL also works, such as https://github.com/owner/repo/blob/main/launch-checklist/SKILL.md , and Lovable imports the parent directory that contains SKILL.md . If you are not sure which URL you need, open the skill’s directory on GitHub and copy the address from your browser. Lovable downloads the repository, validates it, and adds the skill to your workspace.
The repository must be public, and a private repository and a mistyped URL fail the same way. Upload a ZIP Choose Add → Upload ZIP , and drag in or browse for a .zip or .skill file. The archive must contain a SKILL.md file either at the root or inside one wrapping folder. Any bundled files referenced by the skill should sit alongside SKILL.md in the same directory. The file you upload can be up to 50 MB , compressed.
After Lovable unpacks it, the skill itself can include up to 200 files and 10 MB , with each file up to 1 MB . macOS metadata files, such as __MACOSX/ and .DS_Store , are ignored at the root. Example: impor
The rest of this page is on the live site.