Click-Path Audit
Behavioral UI audit for Muse: trace every button through its state changes to catch bugs where handlers work alone but cancel each other out.
- What
- Behavioral UI audit for Muse: trace every button through its state changes to catch bugs where handlers work alone but cancel each other out.
- Cost
- Free
- Needs
- none to install. Pure guidance; have the app area or the suspicious button in mind, plus access to the state store code.
- Level
- Beginner
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a behavioral flow audit that finds the bugs static code reading misses. Traditional debugging checks whether the function exists, whether it crashes, whether types line up. It never checks whether the final UI state matches what the button label promised, whether function B silently undoes what function A just did, or whether shared state has side effects that cancel the intended action. The motivating example: a "New Email" button called setComposeMode(true) then selectThread(null); both worked individually, but selectThread had a side effect resetting composeMode to false, so the button did nothing, and 54 other bugs found by systematic debugging had missed it. The method: first map every state store action to what it sets and what it silently resets (the critical reference), then audit each touchpoint handler call by call in order, checking six patterns: sequential undo, async races, stale closures, missing state transitions (button says Save but nothing saves), conditional dead paths, and useEffect interference. Each finding gets a severity, the exact trace with the conflicting call marked, expected versus actual state, and a specific fix. Includes scope control guidance (full app, single page, or store-focused audits, with a recommended parallel agent split) and positions itself after systematic debugging and before verification. Use when systematic debugging found "no bugs" but users report broken buttons, after modifying any shared state store, after refactors touching shared state, or before release on critical flows. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: the audit is expensive, scope it deliberately; examples lean Zustand and React, adapt the mapping step to your state solution; it finds interaction bugs, not API or styling issues. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Click-Path Audit is a free Muse skill for a behavioral user interface audit that finds bugs static code reading misses. Traditional debugging checks whether a function exists or crashes, but never whether the final interface state matches the button label promise, or whether one function silently undoes another.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Use "Click-Path Audit" with your Muse. Prerequisites: none to install. Pure guidance; have the app area or the suspicious button in mind, plus access to the state store code. 1. Open the skill: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/click-path-audit/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Audit the click paths here: [describe the page or the broken button]. Map the state stores first." 3. Ask it to report every touchpoint with its call-by-call trace, marking any call that undoes an earlier one. Tip: when a button "does nothing", this is the tool. Start store-focused after any store change. Safety: a skill is plain-text instructions; it runs nothing by itself. Fixes still need tests; every bug found here should get one.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
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.