sharaf/product-experience-audit
Use when the user wants to audit a user journey, audit a signup/onboarding/checkout flow, do a UX audit, find the friction in a funnel, understand why users are dropping off or where they are being lost, or improve conversion in a web app — any diagnostic review of a multi-step, in-product flow. Use it whenever the user mentions drop-off, funnels, session replay, heatmaps, activation, time-to-value, cart or checkout abandonment, onboarding friction, or rage clicks, or wants to know where users struggle and what to fix first, even if they don't say "audit." Produces a severity-ranked, prioritized, experiment-validated improvement backlog via evidence-first intake, five parallel specialist lenses, and synthesis.
94
100%
Does it follow best practices?
Impact
72%
1.26xAverage score across 3 eval scenarios
Passed
No known issues
README.md
Product Experience Audit
Use this Tessl skill to audit a user's journey through a live web application — a multi-step, stateful, in-product flow such as signup→activation, onboarding, checkout, or a core task flow — and produce a severity-ranked, prioritized, experiment-validated improvement backlog.
The skill assembles a factual journey brief from whatever evidence exists (live or staging app, source repo, product analytics, session replay, heatmaps, and qualitative inputs), runs five parallel specialist lenses, and synthesizes the findings into a narrative report that says where users leak, why they leak there, how much it costs, which fix to make first, and how to prove the fix worked. Its defining discipline is triangulation: expert inspection, behavioral quantification, and qualitative evidence, used together rather than alone.
When to use
- User-journey and in-product flow audits (signup, onboarding, activation, checkout, core task flows)
- UX audits and funnel drop-off investigations ("why are users dropping off", "where are we losing people")
- Conversion reviews for a web app's in-product experience
- Session-replay, heatmap, and frustration-signal interpretation (rage clicks, dead clicks, u-turns, form re-entry)
- Onboarding friction, time-to-value, and activation analysis
- Cart and checkout abandonment diagnosis
For an acquisition or marketing landing page, use a landing-page audit instead; this skill audits the in-product journey after the click.
Install
tessl install sharaf/product-experience-auditHow it is organized
| Path | Purpose |
|---|---|
skills/product-experience-audit/SKILL.md | Main workflow, severity scale, finding contract, report contract, and routing |
skills/product-experience-audit/references/context-gathering.md | Evidence intake, journey mapping, instrumentation trust, and the journey-brief contract |
skills/product-experience-audit/references/specialist-agents.md | The five specialist lens checklists, benchmarks, and evidence bases |
skills/product-experience-audit/references/synthesis-report.md | Synthesis rules, prioritization, validation methods, report template, and worked example |
skills/product-experience-audit/references/guardrails-decision-logic.md | Guardrails, evidence/symptom routing, journey archetypes, and success criteria |
tile.json | Tessl manifest and registry summary |
README.md | Registry-facing overview |
Output Shape
Default output is a product-experience audit report with:
- Executive summary sizing the biggest opportunity by recoverable conversion
- Journey map marking where users leak, with data-trust caveats
- Findings by lens (funnel, usability, friction, conversion, technical)
- Prioritized backlog sorted by absolute recoverable conversion or a stated ICE/PXL score, each row with a fix and a validation method
- A specific "What's Working Well" section to prevent over-correction
- Evidence and assumptions, naming what was missing rather than inventing it
Each finding includes evidence, why it matters, a concrete fix, a validation method with a one-line hypothesis, and severity.
Eval Results
Evals pending — to be added after the registry Quality gate and the eval run.