# The Clarity teardown kit

Two things in this folder:

1. **clarity-cheat-sheet.pdf** — one page. Eight signals worth watching inside Microsoft
   Clarity, what each one is actually telling you, and the fix. There's a 15 minute weekly
   ritual at the bottom that is the whole thing in five steps. Print it, run it tomorrow.

2. **skills/microsoft-clarity/** — the Claude skill version, "Clarity Lens." Connect it to your
   own live Clarity data and it doesn't just list the loudest signals, it segments your traffic,
   finds the one stage of your funnel actually leaking, and tells you exactly where a button or
   CTA belongs based on your own heat map, not a guess.

## Using the cheat sheet

Open the PDF. Run the weekly ritual on your own site once by hand before reaching for the skill,
so you know what the raw signals actually look like on your own store.

## Using Clarity Lens (10 minutes, one-time setup)

1. In your Clarity dashboard, go to Settings, Data Export, and generate a new API token.
2. Add the Microsoft Clarity MCP server to your Claude config with that token
   (`@microsoft/clarity-mcp-server`, started with `--clarity_api_token=<your token>`).
3. Copy `skills/microsoft-clarity/` into your project's `.claude/skills/` (or upload it to a
   claude.ai project as a skill).
4. Say "run my Clarity" or type `/microsoft-clarity`.

That's it. Open it once a week, ship one fix, and it checks next time whether the last one
actually worked. See `CLARITY-LENS-README.md` for the full detail on what it does and what it
never does (it never edits your live site; every fix is staged for your own review).

Built by Daily Needs Association. dailyneedsassociation.com
