CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

frontend-checklist-global

Use when auditing or improving any frontend codebase against the full Front-End Checklist rule corpus through one entry point.

Quality

61%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/frontend-checklist-global/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 delivers genuinely actionable audit guidance — per-tool routing, conservative-evidence stance rules, and concrete safe-pattern snippets — organized into clear, scannable sections. Its weaknesses are redundancy and token bloat: the same decorative-image, table, and metadata caveats repeat across four or five sections, and the Rule-Derived Highlights duplicate both content Claude already knows and material that exists in references/categories.md. Trimming the duplicated sections and moving the rule highlights into the reference would materially tighten the skill.

Suggestions

Consolidate the decorative-image guidance (repeated in Audit Stance, Coverage Checklist, Rule-Derived Highlights, Known Safe Patterns, and Conflict Resolution) into one authoritative statement plus one safe-pattern example; the `<img src="/divider.svg" alt="" aria-hidden="true">` pattern alone appears four times.

Move the ~85-line Rule-Derived Highlights section into references/categories.md (where much of it is already duplicated) and keep only a short pointer, eliminating both the inlining and the duplication.

Cut restatements of standard frontend knowledge (GPU compositing of transform/opacity, tables-for-layout, 3-flashes-per-second seizure guidance, aria-describedby/aria-invalid basics) and instead defer to `get_rule`/`explain_rule` retrieval, which the skill itself advocates.

DimensionReasoningScore

Conciseness

The body is noticeably padded: the zero-issue pattern `<img src="/divider.svg" alt="" aria-hidden="true">` appears in at least four sections (Audit Stance, Rule-Derived Highlights, Known Safe Patterns, Conflict Resolution), decorative-image and table caveats each repeat across 3-4 sections, and the ~85-line Rule-Derived Highlights section restates frontend fundamentals Claude already knows ("Only transform and opacity can be composited on the GPU", "Never use tables for layout") while duplicating content in references/categories.md. It avoids anchor 1's conceptual fluff (the audit stance is genuinely useful), but the redundancy is pervasive rather than incidental, keeping it below anchor 3.

2 / 5

Actionability

Concrete MCP tool routing maps each input type to a specific tool ("Start with `review_code` for pasted code", "Use `audit_url` for a public page") and the Known Safe Patterns give copy-paste-able recognition snippets (e.g. the generateMetadata and aspect-ratio wrapper examples). It stops short of anchor 5 because no example invocation syntax for the MCP tools is shown — the tool names and purposes are given but not how to call them.

4 / 5

Workflow Clarity

The 5-step numbered workflow sequences input triage → scope narrowing → rule drill-down → remediation, with an explicit pre-conclusion checkpoint ("When no issue is found automatically, use `search_rules` to broaden review coverage before concluding clean") and conservative-reporting stance rules. The audit is read-only so the destructive/batch validation cap does not apply; the minor gap is the absence of an explicit verify-findings-against-`get_rule` step, which keeps it below anchor 5.

4 / 5

Progressive Disclosure

There is exactly one reference, clearly signaled ("See `references/categories.md` for category coverage and tool routing"), one level deep, and the file exists — but ~85 lines of Rule-Derived Highlights are inlined in SKILL.md when they belong in the reference file, and are in fact duplicated there. This matches 'content that should be separate is inline' with a well-signaled reference: better than anchor 2's buried/minimal structure, but the inlining and duplication keep it below anchor 4.

3 / 5

Total

13

/

20

Passed

Description

50%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 trigger clause and names its distinctive rule corpus, but it functions purely as a 'when' statement: it never says what the skill does (route to Front-End Checklist MCP tools to retrieve rules, remediations, and explanations). Trigger vocabulary is also thin, omitting the natural synonyms (review, check, best practices, accessibility, SEO) users would say for a frontend audit. Third-person voice is respected and there is no fluff.

Suggestions

Add a distinct 'what' clause stating the concrete capability, e.g. "Routes frontend code and page audits to the Front-End Checklist MCP tools (review_code, audit_url, get_rule, fix_rule) covering 386 rules." before the 'Use when' clause.

Expand trigger terms with natural synonyms users would say: "review", "check", "frontend best practices", "accessibility", "SEO", "performance".

Narrow "any frontend codebase" to reduce overlap with generic code-review skills — anchor the trigger to the checklist corpus, e.g. "auditing or improving a frontend codebase against the Front-End Checklist best-practice corpus".

DimensionReasoningScore

Specificity

"auditing or improving" are generic verbs with the domain and standard named ("any frontend codebase", "full Front-End Checklist rule corpus"), but the actual capability (routing to MCP tools, retrieving rules and fixes) is never stated, so coverage is not comprehensive. It sits above anchor 2 (which names only a domain with minimal actions) but below anchor 4 (which requires several specific actions).

3 / 5

Completeness

The single sentence is entirely a trigger clause — "Use when auditing or improving any frontend codebase" — giving an explicit 'when', but the 'what' (connecting one entry point to 386 rules via MCP retrieval tools) is only weakly implied by "against the full Front-End Checklist rule corpus through one entry point". It falls between anchor 2 ('when' present without a distinct 'what') and anchor 4 (both clearly present), landing at 3.

3 / 5

Trigger Term Quality

Relevant natural terms are present ("auditing", "improving", "frontend codebase", "Front-End Checklist"), but common variations users would actually say — "review", "check", "best practices", "accessibility", "SEO", "lint" — are missing. This matches 'some relevant keywords but missing common variations or synonyms' rather than anchor 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

"any frontend codebase" combined with broad "auditing or improving" overlaps with general frontend and code-review skills, though "Front-End Checklist rule corpus" carves out a recognizable niche. This matches 'somewhat specific but could still overlap with similar skills' rather than anchor 4, since the 'any frontend codebase' phrasing invites conflicts.

3 / 5

Total

12

/

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/frontend-checklist-global/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.