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

62%

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

57%

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 progressive disclosure to a real reference file, but it suffers from duplicative SEO explanation, a migration script that is described rather than provided inline, and a missing validation checkpoint for the destructive batch-rename workflow.

Suggestions

Remove the duplicate SEO explanation: keep the rationale in one place (either the intro or 'Explain'), not both.

Add an explicit validation step after renaming, e.g. grep for the old filename across the project to confirm no dangling references, then rebuild/run the site to verify.

Either inline the migration script or make the pointer to references/rule.md explicit for the batch-rename case so the executable artifact is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and well-sectioned, but the intro paragraph and the 'Explain' section both restate the same SEO rationale (Google uses filenames as a signal), which is duplicative and could be tightened.	2 / 3
Actionability	Check and Fix give concrete criteria and examples (e.g. IMG_1234.jpg -> blue-running-shoes-side-view.jpg), but the migration script is only described ('provide a migration script that reads old paths...') rather than shown inline, with executable code deferred to the reference.	2 / 3
Workflow Clarity	A Check->Fix sequence with numbered steps is present, but the destructive batch rename and reference-update operation has no validation checkpoint (e.g. confirm no dangling references, rebuild/test), which caps workflow clarity for batch operations.	2 / 3
Progressive Disclosure	The body is a well-organized overview (Quick Reference, Check, Fix, Explain, Code Review) with a clearly signaled one-level-deep pointer to references/rule.md, which exists and holds the executable scripts.	3 / 3
	Total	9 / 12 Passed

Description

67%

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 explicitly covers both what and when, but it is malformed ('related to Use descriptive image filenames') and describes image performance/optimization rather than filename quality, creating a mismatch with the skill's actual purpose and overlap with other image skills.

Suggestions

Rewrite the description to actually describe filename quality, e.g. 'Review image filenames for descriptive, lowercase, hyphen-separated naming. Use when auditing image assets, renaming generic or auto-generated filenames, or improving image SEO.'

Remove the performance-focused actions (encoded size, rendered size, loading strategy, above-the-fold) which belong to a different image-optimization skill and cause conflict risk.

Fix the broken 'related to Use descriptive image filenames' phrasing so the trigger reads as a natural user phrase.

Dimension	Reasoning	Score
Specificity	It names several concrete actions ('reviewing image assets, markup, and CDN or build transforms', 'Check encoded size, rendered size, loading strategy, and above-the-fold impact'), but these describe image performance/optimization rather than the skill's actual filename-renaming purpose, so they are concrete but not comprehensive to this skill.	2 / 3
Completeness	Both 'what' ('Check encoded size, rendered size, loading strategy...') and 'when' ('Use when reviewing image assets...') are explicitly stated with an explicit trigger clause, satisfying the what-and-when requirement.	3 / 3
Trigger Term Quality	It contains relevant keywords ('image filenames', 'descriptive image filenames'), but the phrasing 'related to Use descriptive image filenames' is garbled and a user would not naturally say this trigger clause.	2 / 3
Distinctiveness Conflict Risk	The image-optimization framing (encoded/rendered size, loading strategy, above-the-fold impact) overlaps with other image skills, and the filename niche is buried, so it could still trigger for the wrong skill.	2 / 3
	Total	9 / 12 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: 48405aa

Reviewed: about 10 hours 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.