CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

competitor-experience-audit

Audit the brand, UX, and site design of the leading sites in a vertical as a set of observable cross-site patterns, producing the experience bar a new build must meet or beat. Use this skill whenever the user wants to assess the competitive design field, capture vertical conventions, identify the design and UX bar of a category, or set the experience standard before a build. Triggers on competitor experience audit, UX audit, site design audit, brand audit, design conventions, what makes these sites good, vertical conventions, storefront patterns, merchandising patterns, layout density, primary task, design bar, category conventions, retail vs marketing register, what does the field do. Also triggers when an audit of the competitive field has captured technical signals (SEO, accessibility) but never named the brand, UX, or design conventions, and the build downstream will read as off-vertical without that bar.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

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

The body is well-structured and genuinely actionable for an instruction-only audit skill, with a clear sequenced workflow, real one-level-deep references, and strong honesty safeguards. Its main weakness is token efficiency: the core no-aesthetic-verdicts guardrail, the 3-of-N pattern rule, and the static-vs-rendered rule are each restated multiple times, and the dimension sections duplicate material already in the checklist reference.

Suggestions

Consolidate the honesty guardrail: state the no-aesthetic-verdicts and 3-of-N rules once in the load-bearing guardrail section, and reduce the restatements in the dimensions intro, dimension 5, and failure patterns to short back-references — the same rule currently appears roughly six times.

De-duplicate the seven-dimension framework against references/experience-dimensions-checklist.md: keep a one-line definition plus the observable signal per dimension in the body, and let the checklist carry the full question lists, removing the repeated static-vs-rendered caveats.

Add one worked example of a scored dimension (e.g., a two-line primary-task-prominence pattern plus gap for a named vertical) so the Pattern present / Mixed / Gap / not_assessable labels have a filled-in model to follow.

DimensionReasoningScore

Conciseness

The body is mostly efficient — no explanation of concepts Claude already knows, and the dimension guidance is domain-specific — but the honesty guardrail is restated roughly six times ("Never write Good design or Bad design", "Do not rate the taste", "Do not render personal aesthetic judgments", "Substituting personal taste for field patterns", "Aesthetic verdicts dressed as observations"), the 3-of-N convention rule appears three times, and the static-vs-rendered rule is repeated in three sections. This matches the anchor for mostly efficient content with unnecessary repetition that could be tightened, rather than the minor-trim level of 4.

3 / 5

Actionability

For an instruction-only skill the guidance is concrete and executable: each dimension has observable questions ("What is the largest, earliest interactive element on the first viewport?", "How many clicks or scrolls to the core task?"), defined score labels (Pattern present / Mixed / Gap / not_assessable), explicit thresholds (3 to 6 sites, 3 of N recurrence, under 1500 words), a named output file, and vertical examples ("For auto-parts: typically a fitment selector"). It is 4 rather than 5 because there is no worked example of a scored dimension or a filled pattern statement, and device-class guidance is given for only some verticals.

4 / 5

Workflow Clarity

The 7-step workflow is clearly sequenced (confirm field → render → score with checklist → synthesize → name gap → write with template → hand off) with input validation in step 1 ("Ask if either is unclear"), the failure-patterns section providing push-back checkpoints before delivery, and partial-audit marking when sites cannot be rendered. It is 4 rather than 5 because the checkpoints are distributed across separate sections (failure patterns, honesty guardrail, output format) rather than embedded as explicit validation steps in the workflow itself, and the showcase-scrub step lives in the output section instead of the workflow.

4 / 5

Progressive Disclosure

Structure is good: the body is an overview, both referenced files (references/audit-template.md, references/experience-dimensions-checklist.md) exist, are one level deep with no nested references, and are clearly signaled with a dedicated "Reference files" section plus inline links in the workflow. It is 4 rather than 5 because the seven-dimension framework in the body substantially duplicates the checklist's observable questions, so the split between overview and reference file is not as clean as it could be.

4 / 5

Total

15

/

20

Passed

Description

91%Weight 40%Scale 1-5

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

A strong description: it answers what and when explicitly, carries comprehensive and natural trigger phrasing including colloquial variants, and defines a distinct competitive-field niche. The only softness is that its capability verbs are variations of one audit action, and broad terms like "brand audit" have minor overlap risk with adjacent skills.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Audit the brand, UX, and site design of the leading sites in a vertical as a set of observable cross-site patterns, producing the experience bar a new build must meet or beat" — naming the domain, the method (observable cross-site patterns), and the deliverable (the experience bar). It sits at 4 rather than 5 because the enumerated actions (assess the field, capture conventions, identify the bar, set the standard) are largely synonymous framings of the single audit-and-produce-a-bar action rather than distinct capabilities, leaving minor coverage gaps.

4 / 5

Completeness

Both what and when are explicitly answered: the what is the observable cross-site audit producing an experience bar, and the when is stated twice with concrete trigger phrasing ("Use this skill whenever the user wants to assess the competitive design field, capture vertical conventions..." and the SEO/accessibility-audit-without-design-conventions case). This matches the anchor for a clear what plus explicit when with concrete triggers; it is not 4 because the when clauses are specific rather than merely present.

5 / 5

Trigger Term Quality

Trigger coverage is comprehensive and natural: "competitor experience audit, UX audit, site design audit, brand audit, design conventions, what makes these sites good, vertical conventions, storefront patterns, merchandising patterns, layout density, primary task, design bar, category conventions, retail vs marketing register, what does the field do." These include the synonyms and colloquial phrasings a user would actually say ("what makes these sites good", "what does the field do"), matching the top anchor; file extensions are not applicable to this domain.

5 / 5

Distinctiveness Conflict Risk

The cross-site competitive framing ("leading sites in a vertical", "cross-site patterns", "the experience bar a new build must meet or beat") carves a clear niche distinct from single-site design or technical audits. It is 4 rather than 5 because terms like "brand audit", "UX audit", and "design conventions" carry some overlap risk with adjacent brand-guide, design-standards, and UX-research skills, and the description does not itself state the boundary (the when-not-to-use guidance lives in the body).

4 / 5

Total

18

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rampstackco/claude-skills

Path

dist/codex/.agents/skills/competitor-experience-audit/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.