filename-quality

Use when reviewing image assets, markup, and CDN or build transforms related to Use descriptive image filenames. Check encoded size, rendered size, loading strategy, and above-the-fold impact together.

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/filename-quality/SKILL.md

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 content is well-structured with clear sections, concrete filename examples, and a real one-level-deep reference file containing executable scripts. Its main weaknesses are repeated SEO rationale, missing validation checkpoints for the batch-rename workflow, and some content overlap between the body and the reference.

Suggestions

Add an explicit validation step to the Fix/batch-rename workflow, e.g. after renaming run `grep -r` to confirm no stale references remain and verify the page still loads the images.

De-duplicate the 'why descriptive filenames matter' explanation so it appears once (in Explain) rather than being repeated in the intro and reference.

Trim the Google image-search background Claude already knows; keep only the actionable naming rules and examples.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with clear sections, but it restates the 'why descriptive filenames matter' SEO explanation in three places (intro, Explain, and the same paragraph repeated verbatim) and explains Google's image-search behavior Claude already knows, which could be tightened.	3 / 5
Actionability	It gives concrete, executable guidance — specific bad/good filename examples, a numbered rename procedure, and points to a working batch rename script plus a TypeScript sanitiser in the reference — with only minor gaps (no inline copy-paste command for the common single-file case).	4 / 5
Workflow Clarity	Check/Fix/Explain provide a rough sequence and the Fix steps are numbered, but the batch rename workflow has no validation checkpoint (e.g. confirm references were updated and no broken links remain), so the destructive/batch cap of 3 applies.	3 / 5
Progressive Disclosure	The SKILL.md is a concise overview split into clearly labeled sections with a single well-signaled one-level-deep pointer ('see references/rule.md') that resolves to a real file; it is not a 5 only because some example content overlaps between the body and the reference rather than being cleanly partitioned.	4 / 5
	Total	14 / 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 a clear trigger clause but its stated actions describe image delivery/performance rather than filename naming, creating a purpose mismatch and high overlap risk with image-optimization skills. The 'what' is further weakened by the fragmented 'related to Use descriptive image filenames' phrasing.

Suggestions

Rewrite the 'what' to describe actual filename actions, e.g. 'Scans image filenames for generic, uppercase, spaced, or underscored names and renames them to descriptive hyphen-separated lowercase names.'

Replace delivery jargon ('encoded size, rendered size, loading strategy, above-the-fold impact') with filename-relevant trigger terms users would say, such as 'image filenames', 'rename images', 'image SEO', or 'asset naming'.

Fix the broken 'related to Use descriptive image filenames' fragment so the description reads as a single coherent sentence.

Dimension	Reasoning	Score
Specificity	Names the domain ('reviewing image assets, markup, and CDN or build transforms') and lists concrete actions ('Check encoded size, rendered size, loading strategy, and above-the-fold impact'), but the actions describe image delivery/performance rather than filename quality, so coverage of the skill's actual purpose is incomplete.	3 / 5
Completeness	It has an explicit 'Use when' clause for the 'when', but the 'what' is broken — 'related to Use descriptive image filenames' is fragmented and the listed actions (size, loading strategy) don't describe what the skill does; the cap for a present-but-weak 'what' with a clear 'when' lands at 3.	3 / 5
Trigger Term Quality	It opens with 'Use when reviewing image assets, markup, and CDN or build transforms', giving a reasonable trigger phrase, but it omits natural filename-specific terms users would say (e.g., 'image filenames', 'rename images', 'SEO filenames') and leans on delivery jargon instead.	3 / 5
Distinctiveness Conflict Risk	The description's actions (encoded size, rendered size, loading strategy, above-the-fold impact, CDN/build transforms) overlap heavily with general image-performance skills, and the awkward filename framing makes it likely to trigger for the wrong image-related skill.	2 / 5
	Total	11 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/filename-quality/SKILL.md
Commit: 30756a7

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.