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

65%

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 ./.claude/cloud-profile/skills/frontend-checklist-global/SKILL.md

The canonical home for this skill is frontend-checklist-global in thedaviddias/Front-End-Checklist

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 MCP routing guidance and a clear, conservative audit workflow with concrete safe-pattern examples. However, it is significantly bloated: the same decorative-image and table-header guidance repeats across four to five sections, standard frontend concepts are re-explained, and roughly 100 lines duplicate the bundle reference verbatim instead of being delegated to it.

Suggestions

State each policy once: consolidate the decorative-image/alt="" guidance (currently in Audit Stance, Coverage Checklist, Highlights, Safe Patterns, and Conflict Resolution) into a single section, cutting the '/divider.svg' example from 4+ occurrences to one.

Remove the Rule-Derived Highlights section from SKILL.md — it duplicates references/categories.md nearly verbatim and re-teaches frontend basics Claude already knows; keep only a one-line pointer to the reference.

Trim explanations of well-known concepts (GPU compositing of transform/opacity, prefers-reduced-motion basics, th/scope semantics) down to the skill-specific audit stance, keeping only the non-obvious calibration rules (e.g. when to prefer scope findings over caption findings).

DimensionReasoningScore

Conciseness

The ~180-line body states the decorative-image/alt="" guidance in five separate sections (Audit Stance, Coverage Checklist, Rule-Derived Highlights, Known Safe Patterns, Conflict Resolution — the '/divider.svg' example alone appears 4+ times), and the Highlights sections re-teach standard knowledge Claude already has (transform/opacity compositing, prefers-reduced-motion, th/scope semantics). This matches anchor 2: noticeably verbose with several padded, redundant sections.

2 / 5

Actionability

The workflow gives exact MCP tool names with routing conditions ('review_code' for pasted code, 'audit_url' for public pages, 'get_rule'/'fix_rule'/'explain_rule' for remediation), and Known Safe Patterns provides concrete snippet-level examples. Minor gaps (no example tool invocations) keep it at anchor 4 rather than 5.

4 / 5

Workflow Clarity

A clear 5-step numbered workflow with per-step tool selection, an Audit Stance governing what to report, and a pre-conclusion checkpoint ('use search_rules to broaden review coverage before concluding clean'). It lacks an explicit validate-findings feedback loop, so anchor 4 rather than 5; no destructive or batch operations, so no cap applies.

4 / 5

Progressive Disclosure

The single reference (references/categories.md) is one level deep and clearly signaled at the end, but the Rule-Derived Highlights, Known Safe Patterns, and Category Coverage sections (~100 lines) are duplicated nearly verbatim in the bundle file — content that should live only in the reference is inlined in SKILL.md. Anchor 3 is the best fit: structure and signaling are present, but separation is not.

3 / 5

Total

13

/

20

Passed

Description

58%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 a clear explicit trigger clause and names a distinct rule corpus, but describes the skill's actual capabilities only vaguely ('auditing or improving... through one entry point') and misses natural trigger synonyms like 'review' or 'best practices'. It is serviceable but sits mid-range on specificity, triggers, and distinctiveness.

Suggestions

State the concrete capabilities after the trigger, e.g. 'Retrieves rules, audits code or live URLs, and returns exact remediation guidance via Front-End Checklist MCP tools' — this would lift both specificity and completeness.

Add natural trigger synonyms users would say: 'frontend review', 'web best practices', 'accessibility/performance/SEO audit' rather than only 'auditing or improving'.

Narrow the trigger from 'any frontend codebase' to checklist-driven auditing (e.g. 'when the user wants a structured frontend best-practices audit') to reduce overlap with generic code-review skills.

DimensionReasoningScore

Specificity

The description names the domain ('frontend codebase', 'Front-End Checklist rule corpus') and two actions ('auditing or improving'), but the verbs are generic and no concrete capability (rule retrieval, remediation guidance, MCP tooling) is stated. It matches anchor 3 rather than 4, which requires several specific actions.

3 / 5

Completeness

An explicit 'Use when auditing or improving any frontend codebase' trigger is present, and the what is stated, but only implicitly inside the when-clause — 'through one entry point' is vague about what the skill actually does. Anchor 4 (both present, one could be more specific) is the best fit; anchor 5 requires a concrete, separately stated capability list.

4 / 5

Trigger Term Quality

'Auditing', 'improving', 'frontend codebase', and 'Front-End Checklist' are natural terms, but common variations users would actually say — 'review my frontend', 'best practices', 'accessibility', 'performance', 'web audit' — are missing. This sits at anchor 3 (relevant keywords, missing synonyms).

3 / 5

Distinctiveness Conflict Risk

'Front-End Checklist rule corpus' carves out a recognizable niche, but the trigger 'auditing or improving any frontend codebase' is broad enough to overlap with general code-review and linting skills. Anchor 3 (somewhat specific, overlap still possible) fits better than 4.

3 / 5

Total

13

/

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

BigSimmo/PsychSift

Path

.claude/cloud-profile/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.