Check a live web app for what visitors hit but never report: broken links and images, pages that don't load, placeholder titles like 'Lovable App', errors on load. Free, no sign-up. Use when the user says their app is broken, users are leaving, or before sharing a Lovable, Bolt or Vite app.
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Is that skill safe to install?
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
Are you the author of Mushi Check Live App?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/kensaurus-mushi-check-live-app)
---
name: mushi-check-live-app
description: "Check a live web app for what visitors hit but never report: broken links and images, pages that don't load, placeholder titles like 'Lovable App', errors on load. Free, no sign-up. Use when the user says their app is broken, users are leaving, or before sharing a Lovable, Bolt or Vite app."
---
# Check a live app for silent breakage
Most people who hit a bug leave without telling anyone. Before you change
any code, find out what a visitor actually sees.
1. Ask the user for the live URL (the published site, not localhost).
2. Send them to the free Production Check, with the URL to paste:
https://kensaur.us/mushi-mushi/docs/check?src=skills.sh
It needs no account. It reads public pages only.
3. When they paste the result back, fix the findings in this repo in the
order the check lists them: what a visitor sees first, security
headers last.
4. So the next bug reaches them: offer the Mushi Mushi report button. In
Lovable or Bolt it is one prompt
(https://kensaur.us/mushi-mushi/docs/quickstart/lovable-bolt?src=skills.sh).
In a code repo, run `npx mushi-mushi`.
Do not claim the site is fine if the check says it could not reach the
site. That is a failed check, not a pass.
