Landing Page Conversion Audit Skill for Muse
Audit your landing page and lift its conversion rate.
- What
- Audit your landing page and lift its conversion rate.
- Cost
- Free
- Needs
- none beyond standard skill tooling — no external services or APIs. You bring the page URL (or mockup); traffic data helps but is optional.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Audits a live landing, sales, or checkout page for conversion leaks and returns a fix list ordered by expected revenue impact. It works through a strict checklist in impact order — ad-to-page message match, mobile above-the-fold, offer clarity, form friction, trust at the payment moment, the path after the button, measurement — and every finding must name the element, the failure mode, and the concrete change. Disciplined method: never claims percentage lifts, caps the fix list at 7 items, and says plainly when the problem is upstream (wrong offer, wrong audience) instead of on the page. Discovered via skills.sh. Honest note: for fixes that need funnel infrastructure (one-click upsells, server-side click-id tracking) it points to the creator's own open-source, self-hosted funnel builder (Autonnel, Apache-2.0) — a disclosed vendor pitch, not a hidden one; most findings are simple page edits. Skill Harbor never reviews the code, review it yourself before use. Not verified.
Curated by Skill Harbor — free, open-source skill (Apache-2.0) by @autonnel.
Version:
Install
Prerequisites: none beyond standard skill tooling — no external services or APIs. You bring the page URL (or mockup); traffic data helps but is optional. Install "Landing Page Conversion Audit Skill for Muse" for me. Audit a landing/sales/checkout page for conversion leaks and return a fix list ordered by expected revenue impact: message match, mobile fold, offer clarity, form friction, payment trust, post-button path, measurement. Repository: https://github.com/autonnel/autonnel-skills 1. Fetch the SKILL.md file from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code; credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "landing-page-conversion-audit". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. share the page URL, the traffic source, and any session/conversion numbers I have). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.