CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

consistent-help

Use when reviewing support UI across multi-page flows such as checkout, onboarding, account recovery, or support journeys. Compare multiple pages in the same variation instead of reviewing a single page alone.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/consistent-help/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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.

A tight, well-structured overview body with a correctly wired one-level-deep reference to the real references/rule.md file. The Check and Fix sections give concrete audit criteria, but the workflow lacks an in-body validation checkpoint after fixing, and the motivating intro paragraph and the undefined 'same variation' phrasing are minor efficiency losses.

Suggestions

Add an explicit verification step after Fix, e.g. 'Re-open each page in the flow at the same breakpoint and zoom level and confirm repeated help mechanisms now appear in the same relative order', to close the batch-workflow validation gap.

Replace the undefined term 'same variation' with the concrete condition already used elsewhere ('same breakpoint and zoom level') so the audit criterion is unambiguous.

Trim the opening motivational paragraph to a single clause or move it to the reference file, since it explains why the rule matters rather than instructing what to do.

DimensionReasoningScore

Conciseness

The body is lean — terse Quick Reference bullets and four one-to-two-sentence sections with no padding and no explanation of concepts Claude already knows. One minor trim exists: the opening motivational paragraph ("Predictable placement reduces stress and makes support easier to find when a user is already struggling") argues why the rule matters rather than instructing, so this is 'minor instances of over-explanation that could be trimmed' rather than a 5 where every token earns its place. Not a 3: there is no unnecessary library or concept explanation beyond that brief rationale.

4 / 5

Actionability

The Check section gives concrete, executable audit guidance — "contact links, chat triggers, help-center links, or support phone numbers" and the criterion "same relative order on each page" — and Fix gives a concrete remediation ("keep their relative order stable across the flow at the same breakpoint"). Per the rubric's instruction-skill note, absence of code in the body is not penalized since the code examples live in references/rule.md. Minor gaps keep it at 4: no concrete procedure for comparing at the same breakpoint/zoom (e.g. responsive devtools at a fixed viewport) is given in the body itself.

4 / 5

Workflow Clarity

A clear sequence is present — Quick Reference → Check → Fix → Explain → Code Review — and this skill spans a batch of pages across a flow, but there is no validation checkpoint after Fix in the body (verification exists only in the referenced rule.md, so the checkpoint is implicit at best). The rubric's cap applies: batch/multi-page change workflows without an in-body validation step cannot score above 3. Not a 2: the sequence is well-defined with a specific failure criterion ('Flag exact pages or breakpoints where repeated help moves'), far better than a rough unordered list.

3 / 5

Progressive Disclosure

The body is a well-organized overview (quick reference plus per-audience sections) that appropriately defers detail: "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — a clearly signaled, one-level-deep reference that exists and itself contains no further nested references. Content is appropriately split (body = overview; rule.md = code, best practices, standards, exceptions, verification), matching the anchor for a clear overview with well-signaled one-level-deep references. Not a 4: there are no organization gaps — the single reference is named with its purpose and verified to exist.

5 / 5

Total

16

/

20

Passed

Description

70%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.

The description has an explicit, well-formed 'Use when...' trigger with concrete example flows and a clear what/when pair, using third person throughout. Its main weakness is that the 'what' understates the actual skill — auditing consistency of repeated help mechanisms — leaving the action vague and omitting key domain terms like 'help', 'consistent', or 'WCAG'.

Suggestions

State the concrete action in the description, e.g. 'Audit whether repeated help mechanisms (contact links, chat, phone, FAQ) appear in the same relative order across pages', instead of only 'Compare multiple pages in the same variation'.

Add natural trigger synonyms users would say — 'help', 'consistent help', 'contact', 'chat', 'WCAG' — to complement the flow names (checkout, onboarding, account recovery).

DimensionReasoningScore

Specificity

"Compare multiple pages in the same variation instead of reviewing a single page alone" names the domain ("support UI across multi-page flows") and one concrete action (comparing pages), but coverage is not comprehensive — the actual audit criteria (help mechanisms, relative order, breakpoints) are never stated. Not a 4: only one specific action is listed, matching the anchor 'names domain and 1-2 concrete actions, but not comprehensive'; not a 2 because an explicit action is given, not just a domain label.

3 / 5

Completeness

Both halves are present: an explicit "Use when reviewing support UI across multi-page flows such as checkout..." (when) and "Compare multiple pages in the same variation instead of reviewing a single page alone" (what). Not a 5: the 'what' is vague about what the comparison produces — "in the same variation" is unclear terminology and the concrete audit outcome (consistent placement/order of help mechanisms) is absent, so the what is present but imprecise rather than clearly and concretely answering both.

4 / 5

Trigger Term Quality

Strong natural flow names — "checkout, onboarding, account recovery, or support journeys" — plus "support UI" and "multi-page flows" give good keyword coverage. A few natural terms users would say are missing: "help", "consistent help", "contact", "chat", "FAQ", "WCAG". Not a 5 for those gaps; not a 3 because multiple relevant, naturally-spoken trigger phrases are present, not just a bare domain mention.

4 / 5

Distinctiveness Conflict Risk

"Reviewing support UI across multi-page flows such as checkout, onboarding, account recovery" carves a fairly distinct niche with specific flow triggers, so it would rarely fire for unrelated skills. Minor overlap remains with general UI-review, checkout-UX, or accessibility-audit skills that also trigger on "checkout" or "onboarding" — not a 5; clearly more targeted than a broad 'helps with UI review' — not a 3.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/consistent-help/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.