Audit and debug your Storesynk build with Claude

When something on your store isn’t behaving, you usually know the symptom (“add to cart does nothing”, “the cart won’t open”, “checkout 404s”) but not the cause. The Storesynk Audit Skill hands that diagnosis to Claude: it fetches your published page, validates your Storesynk components against the official rules, matches your symptom against the most common support issues, and returns a structured report with the exact fix and links back to these docs. It’s open source, and this guide walks you through installing it and running your first audit.

What it checks

The skill runs the same checks our support team would, in seconds:

• Installation: the Storesynk script is present (and only once), and your token and domain are configured.
• Structure: component nesting rules, such as nested Product Containers or the cart hierarchy, each with a stable rule code.
• Attributes: every sf-* attribute is checked against the full catalog, so a typo like sf-add-to-cart-button on the wrong element gets caught.
• Element types: each component sits on the right kind of HTML element.
• Known issues: frequent problems (checkout 404s, sync failures, market quirks, account loops) matched by the symptom you describe.

Requirements

The skill audits your published page by fetching its HTML, so Claude needs network access in your environment.

• Claude Code (terminal, desktop app, IDE, web): works out of the box — no extra setup.
• Claude (claude.ai): requires a paid plan with code execution and web search turned on.

Install in Claude Code (terminal)

The quickest path is the plugin marketplace. Run these two commands in Claude Code:

/plugin marketplace add storesynk/audit-skill
/plugin install storesynk-audit@storesynk

‍
Prefer a manual install? Clone the repository and copy the skill into your skills directory:‍

git clone https://github.com/storesynk/audit-skill.git
cp -r audit-skill/skills/storesynk-audit ~/.claude/skills/

‍Use your project’s .claude/skills/ directory instead of ~/.claude/skills/ to install it for a single project only.

Install in the Claude desktop app

Follow the below steps to add the skill from the desktop app:

1. Open the Customize panel in the left sidebar.
2. Click Skills (or Plugins, depending on your app version).
3. Click the + button next to Personal plugins / Personal skills, then Create plugin.
4. Click Add marketplace, then Add from a repository.
5. Paste the repository URL: https://github.com/storesynk/audit-skill
6. Click the Use link that appears below the skills list, then click Sync.

Install on claude.ai

Available on paid plans (Pro, Max, Team, Enterprise). Menu labels can shift as claude.ai evolves — if something looks different, search “skills” in the Claude help center.

1. Enable code execution. Go to Settings > Capabilities and turn on Code execution. Skills run inside this sandbox.
2. Enable web search. In the same Capabilities settings, turn on Web search so Claude can fetch your live page.
3. Install the skill. Open the Customize panel and follow the same steps as the desktop app above — add the marketplace from the repository URL and click Sync.

Run your first audit

Start a new conversation and describe your issue, including the page URL. For example:

• “My add to cart button doesn’t do anything on https://mystore.com/products/blue-shirt — can you check it?”
• “Audit my Storesynk build before launch: https://mystore.webflow.io”

Claude will ask for whatever it needs (the exact page URL, what’s broken, whether it’s a CMS page) and then produce a structured audit report. If the skill doesn’t kick in on its own, say “use the Storesynk Audit skill”.

Tips for the best results

• Share the published page where the problem happens — your custom domain or the *.webflow.io staging domain. The skill audits served HTML, so the page must be published.
• Paste any browser console errors — they give Claude a big head start.
• If Claude has browser tools (such as Claude in Chrome), it can also inspect runtime state and console output on the live site itself, not just the served HTML.