How do I install the Lovable Deploy skill?

Run npx skillmds@latest add 10k-digital/lovable-deploy in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Lovable Deploy safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Lovable Deploy?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Lovable Deploy free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Lovable Deploy?

10k-digital (@10k-digital) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Lovable Deploy by 10k-digital — Agent Skill

Name: Lovable Deploy
Rating: 4.666666666666667 (3 reviews)
Author: 10k-digital

File contents

Lovable Deployment

Use the following deterministic fallback order:

Official Lovable MCP at https://mcp.lovable.dev when the server and required operation are available. Read its tool schema and server instructions before calling it.
Browser automation against the configured Lovable project when MCP is unavailable or does not support the operation.
Manual prompt copied to the user when neither automation path is available.

Before deployment:

Confirm GitHub has the latest commit and allow the normal GitHub → Lovable sync delay.
Read .lovable-agent/config.json (or the legacy Claude configuration) for the project ID and mode.
Scan the changed code for required secret names and report missing configuration without exposing values.
Ask for confirmation before applying destructive or irreversible migrations.

After deployment, distinguish accepted (the agent received the request) from verified (the response/logs or Preview checks confirm the result). Never claim verification from an asynchronous MCP acknowledgement alone. If polling is supported, poll with a bounded timeout; otherwise report the accepted state and give the manual verification step.

Classify MCP failures before falling back: an unsupported operation, timeout, or unavailable server uses browser automation; an authentication failure requires re-authentication or a manual handoff. Do not retry authentication failures indefinitely, and never include preview tokens or secret values in MCP requests, browser URLs, logs, or generated reports.

The existing ../yolo/ skill and ../yolo/references/mcp-workflows.md contain the Claude browser and MCP procedures. Keep them as compatibility references rather than creating a custom MCP server.

---name: lovable-deploydescription: Deploy Lovable backend work from any coding agent. Use for Supabase Edge Functions, database migrations, Lovable MCP setup, deployment verification, or deciding between MCP, browser, and manual fallbacks.---# Lovable DeploymentUse the following deterministic fallback order:1. **Official Lovable MCP** at `https://mcp.lovable.dev` when the server and required operation are available. Read its tool schema and server instructions before calling it.2. **Browser automation** against the configured Lovable project when MCP is unavailable or does not support the operation.3. **Manual prompt** copied to the user when neither automation path is available.Before deployment:- Confirm GitHub has the latest commit and allow the normal GitHub → Lovable sync delay.- Read `.lovable-agent/config.json` (or the legacy Claude configuration) for the project ID and mode.- Scan the changed code for required secret *names* and report missing configuration without exposing values.- Ask for confirmation before applying destructive or irreversible migrations.After deployment, distinguish **accepted** (the agent received the request) from **verified** (theresponse/logs or Preview checks confirm the result). Never claim verification from an asynchronousMCP acknowledgement alone. If polling is supported, poll with a bounded timeout; otherwise reportthe accepted state and give the manual verification step.Classify MCP failures before falling back: an unsupported operation, timeout, or unavailable serveruses browser automation; an authentication failure requires re-authentication or a manual handoff.Do not retry authentication failures indefinitely, and never include preview tokens or secret valuesin MCP requests, browser URLs, logs, or generated reports.The existing `../yolo/` skill and `../yolo/references/mcp-workflows.md` contain the Claude browserand MCP procedures. Keep them as compatibility references rather than creating a custom MCP server.

Frequently asked questions

Lovable Deploy