← ClaudeAtlas

clarity-skilllisted

Reads Microsoft Clarity aggregated project metrics (via the Data Export API) and, when available, per-session event exports, to surface performance/UX/UI problems and turn them into a prioritized report, a visual dashboard, and concrete code changes in the connected app. Triggers on "Clarity", "session recording", "rage click", "dead click", "heatmap", "quickback", "scroll depth", "UX audit from analytics", "migliora UX/performance con i dati di Clarity".
VincenzoManto/clarity-skill · ★ 1 · AI & Automation · score 64
Install: claude install-skill VincenzoManto/clarity-skill
# Clarity Skill Turns Microsoft Clarity data into shippable UX/performance/UI fixes. Two data tiers, one pipeline: 1. **Aggregated project metrics** — official Clarity **Data Export API** (`project-live-insights`). This is the only officially supported programmatic source. It covers the **last 1–3 days only** and is **rate-limited to 10 requests/day per project**, returned as counts broken down by up to 3 dimensions (Browser, Device, OS, Country, URL, PageTitle, Source, Medium, Campaign, Channel). 2. **Per-session / per-event data** — Clarity does **not** expose raw session recordings or event streams through a public API; that data only lives in the dashboard UI. Two ways to get it into the pipeline: - The user hands you an export (manual export, custom snippet, saved JSON) — ingest it as documented in `references/session-event-format.md`. - Or use `scripts/clarity-login.js` + `scripts/scrape-sessions.js`, which drive a real browser against the user's own Clarity dashboard to read session metadata and rage/dead-click/error markers from the Recordings UI. This is DOM automation against an undocumented, changeable UI — **fragile by nature** (selectors break on any Clarity redesign) and it is the user's responsibility to confirm this stays within Clarity's Terms of Service for their use case. It captures session metadata and flagged-event markers, not raw mouse-movement replay data (Clarity renders that a