# Microsoft Clarity Analyst

> Microsoft Clarity Analyst

- Skill: `dasexperten/microsoft-clarity-analyst` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add dasexperten/microsoft-clarity-analyst`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dasexperten/microsoft-clarity-analyst/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: dasexperten (https://skillmd.com/u/dasexperten)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/dasexperten/microsoft-clarity-analyst

---

# Microsoft Clarity Analyst

## Purpose

Use Microsoft Clarity observations to find real user behavior problems such as rage clicks, dead clicks, excessive scrolling, confusion, mobile friction, and layout issues.

This skill turns Clarity recordings, heatmaps, and behavior signals into practical website improvement actions.

## When to Use

Use this skill when the task is to:

- analyze Microsoft Clarity data;
- interpret heatmaps or recordings;
- find rage clicks or dead clicks;
- diagnose user confusion;
- prioritize UX and CRO fixes;
- understand mobile behavior;
- connect behavior data to conversion problems.

## When NOT to Use

Do not use for GA4 traffic attribution, SEO performance, or server-side analytics setup. Use this skill for behavior analysis from Clarity-style evidence.

## Inputs

Useful inputs:

- Clarity screenshots;
- heatmap observations;
- session recording notes;
- page URL;
- device type;
- traffic source;
- conversion goal;
- known issues;
- rage click or dead click data;
- scroll depth observations.

## Workflow

1. Define the page goal and key user action.
2. Review heatmaps for attention, scroll, and click behavior.
3. Review recordings for confusion, hesitation, repeated actions, and friction.
4. Identify rage clicks, dead clicks, missed CTAs, and mobile issues.
5. Connect behavior signals to likely causes.
6. Prioritize fixes by frequency, severity, and conversion impact.
7. Recommend tests or UX changes.

## Output

Always provide:

- behavior diagnosis;
- key Clarity signals;
- likely causes;
- page or UX issues;
- priority fixes;
- test ideas;
- KPI notes;
- next steps.

## Best Practices

- Treat recordings as clues, not absolute proof.
- Look for repeated patterns across users.
- Separate curiosity clicks from frustration clicks.
- Prioritize mobile issues when mobile traffic is high.
- Combine Clarity with GA4 when possible.

## Common Mistakes

- Overreacting to one recording.
- Ignoring traffic source intent.
- Fixing low-impact visual issues first.
- Not separating desktop and mobile behavior.
- Using heatmaps without page goal context.

## Related Skills

- cro-auditor
- ux-audit
- mobile-ux-optimizer
- google-analytics-expert
- checkout-optimizer