CtrlK
BlogDocsLog inGet started
Tessl Logo

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

1.26x
Quality

100%

Does it follow best practices?

Impact

72%

1.26x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tightly written methodology skill: lean yet substantive, highly actionable with concrete commands and templates, a clearly sequenced workflow with validation checkpoints, and exemplary progressive disclosure via real one-level references. No dimension shows meaningful weakness.

DimensionReasoningScore

Conciseness

The body is information-dense and assumes Claude's competence — it never explains basic concepts Claude knows — and every block (commands, templates, thresholds) earns its place; specific figures like 'ad-blocker ~25–40%, consent decline ~50–55%' add value Claude would not reliably recall.

3 / 3

Actionability

Provides copy-paste-ready, executable guidance: concrete `rg` scanning commands, an exact nine-field Journey Brief template, an exact Finding Contract markdown template, and a severity scale with measurable thresholds and examples.

3 / 3

Workflow Clarity

A four-phase sequenced workflow table pairs with explicit validation checkpoints — gate analytics on instrumentation trust before believing numbers, assert a cause only with evidence, and read guardrails before finalizing — plus checklists (brief, finding, report) for the complex process.

3 / 3

Progressive Disclosure

Clear overview with well-signaled, one-level-deep references — all four referenced files (context-gathering, specialist-agents, synthesis-report, guardrails-decision-logic) exist in references/ — with core contracts kept inline and phase details split out for easy navigation.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: it states concrete actions, provides rich natural-language trigger terms, answers both 'what' and 'when' explicitly, and stakes out a distinct niche. Voice is appropriately third-person/trigger-style, incurring no penalty.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'audit a user journey', 'find the friction in a funnel', 'understand why users are dropping off', 'improve conversion', and 'Produces a severity-ranked, prioritized, experiment-validated improvement backlog' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what (audits an in-product journey and produces a prioritized, experiment-validated backlog) and when (two 'Use when/Use it whenever' clauses with explicit triggers), well above the cap of 2 for missing triggers.

3 / 3

Trigger Term Quality

Strong coverage of natural terms users would say: 'drop-off, funnels, session replay, heatmaps, activation, time-to-value, cart or checkout abandonment, onboarding friction, or rage clicks', plus 'UX audit' and 'improve conversion'.

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche — diagnostic review of a multi-step, in-product flow — and explicitly defers landing-page audits elsewhere, so it is unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents