← Search

Lovable Agent Skills for Muse
Developer tools 📌 Pinned version: commit 83f881f
⚙ Needs: Claude Code (or a compatible plugin host).

Lovable Agent Skills for Muse

Drive your Lovable project from Muse: sync, deploy, migrate, test.

At a glance
What
Drive your Lovable project from Muse: sync, deploy, migrate, test.
Cost
Free
Needs
Claude Code (or a compatible plugin host). A Lovable account and credits for Lovable-side actions (deploy, migrations, preview tests) — never tested here.
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version: 2.0.3

1
✓ Created by: 10K-Digital

Quick answer

Lovable Agent Skills lets Muse work on your Lovable project: sync with GitHub, deploy edge functions, run migrations and test the preview. YOLO mode is off by default, destructive database work still asks first, and auto-push only runs if you turn it on. Lovable-side actions need your own Lovable account and credits.

⌁

Install

Copy the install package below, then paste it into Muse📌 Pinned version: commit 83f881f

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: Claude Code (or a compatible plugin host). A Lovable account and credits for Lovable-side actions (deploy, migrations, preview tests) — never tested here. Install "Lovable Agent Skills" for me (plugin "lovable", v2.0.3). Eight skills that let Muse work on your Lovable project instead of only describing it: project setup, GitHub sync, edge-function deploys, migrations, and testing, with Lovable's exact prompts for the backend. The guardrails are real and readable in the code: YOLO mode is off by default and never enables auto-push on its own; confirmation is always kept for destructive database work; `deploy.confirm_migrations` is honoured even in YOLO; auto-push runs only if you explicitly turn it on. The git hooks run automatically when the plugin is loaded: sync at session start (`git pull --rebase` on main only, never with uncommitted changes), push at stop only if auto-push is explicitly enabled. Sandbox test, November 8, 2026: manifest valid, 8 skills valid, the YOLO / confirmation / auto-push guardrails verified in the code. Lovable-side actions, the marketplace install in Claude Code and `migrate-workspace.py` on a real project were not tested. Repository: https://github.com/10K-Digital/lovable-agent-skills Pinned version: install the code at commit 83f881f73258896d54e52eaebadf5627ad80dce7 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the plugin folder (`plugins/lovable/`) from the repository into a temporary folder 2. Integrity check: compute the SHA-256 of the fetched `plugins/lovable/plugin.json`; it must match 025d587db3a83622e0c73f385283daa49f3cedc4274d337736d4c609a2356645, the fingerprint Skill Harbor recorded on November 8, 2026. If it does not match, STOP, do not install, and tell me, showing the expected and actual hashes. 3. Safety check: review the plugin files for anything suspicious (unexpected network calls, shell commands, credential harvesting). The `secrets-*` helpers only extract secret NAMES, never values. Verify that holds here; STOP on any red flag and tell me. 4. Install it as a plugin in Claude Code: run `/plugin marketplace add 10K-Digital/lovable-agent-skills`, then `/plugin install lovable@10k-digital`. 5. Verify with no network calls: manifest valid (name: lovable, version 2.0.3), the 8 SKILL.md files in place. 6. Report what was installed, where, and what I still need to do myself (e.g. my Lovable account and credits for deploys, migrations and preview tests; confirm the auto-push setting before relying on it). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🔒 Security and provenance
📌 Pinned version: commit 83f881f · 2026-11-08
🔎 Last checked · Nov 10, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
83f881f · 2026-11-08
Sandbox install test
No sandbox install test on record for this listing.
Creator identity
Verified · 2026-11-08
Fingerprint watch
Last checked · Nov 10, 2026 : no change detected in the files linked by this install prompt

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.