Schema Markup
alirezarezvani/claude-skills
When the user wants to implement, audit, or validate structured data (schema markup) on their website.
A skill your agent uses when reviewing image assets, markup, and CDN or build transforms related to Use descriptive image filenames.
MITAuto-check passed
Install Filename Quality
$ npx skills add thedaviddias/Front-End-Checklist --skill filename-quality -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist filename-quality --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/filename-quality .claude/skills/filename-quality && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "filename-quality" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/filename-quality into .claude/skills/filename-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "filename-quality", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/filename-qualityType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thedaviddias/Front-End-Checklist --skill filename-quality -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist filename-quality --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/filename-quality .agents/skills/filename-quality && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "filename-quality" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/filename-quality into .agents/skills/filename-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "filename-quality", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill filename-quality -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist filename-quality --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/filename-quality .cursor/skills/filename-quality && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "filename-quality" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/filename-quality into .cursor/skills/filename-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "filename-quality", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thedaviddias/Front-End-Checklist.git --path skills/filename-quality--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thedaviddias/Front-End-Checklist --skill filename-quality -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist filename-quality --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/filename-quality .gemini/skills/filename-quality && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "filename-quality" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/filename-quality into .gemini/skills/filename-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "filename-quality", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thedaviddias/Front-End-Checklist filename-qualityInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thedaviddias/Front-End-Checklist --skill filename-quality -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/filename-quality .github/skills/filename-quality && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "filename-quality" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/filename-quality into .github/skills/filename-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "filename-quality", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill filename-quality -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thedaviddias/Front-End-Checklist filename-quality --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/filename-quality .opencode/skills/filename-quality && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "filename-quality" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/filename-quality into .opencode/skills/filename-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "filename-quality", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
filename-quality- GitHub stars
- 74k
- Token cost
- ~799 tokens
- SKILL.md length
- 355 words
- Files
- 2 (incl. references)
- Skills in repo
- 390
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reviewing image assets, markup, and CDN or build transforms related to Use descriptive image filenames.
- Reviewing image assets
- SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Build transforms related to Use descriptive image filenames
What it does
Filename Quality is an agent skill from thedaviddias/Front-End-Checklist. 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.
Its SKILL.md is about 800 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).
The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.
When your agent uses it
- Reviewing image assets
- Build transforms related to Use descriptive image filenames
Example prompts
- “/filename-quality”
What it can do on your machine
Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
frontendchecklist.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Filename Quality loads about 799 tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 55 tokens; SKILL.md has 355 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 355 words, ~799 tokens.
Download SKILL.mdSave it as
.claude/skills/filename-quality/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- filename-quality
- description
- 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.
- metadata.category
- images
- metadata.priority
- low
- metadata.difficulty
- beginner
- metadata.estimatedTime
- 10
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/images/filename-quality
Use descriptive image filenames
Google explicitly recommends descriptive filenames in its Image SEO best practices. A file named red-leather-wallet.jpg gives search engines context about the image content, improving discoverability in image search. Generic filenames waste this SEO signal. Descriptive names also help developers maintain large asset libraries without opening every file to identify its content.
Quick Reference
- Use descriptive, hyphen-separated filenames:
hero-homepage-team-collaboration.jpg - Avoid generic names like
image1.jpg,photo.png, or camera defaults likeIMG_4532.jpg - Use lowercase only—avoid uppercase letters and spaces which can cause URL encoding issues
- Google uses filenames as a relevance signal for image search results
Check
Scan all image file references in this codebase (<img src>, CSS url(), import statements, and public/assets directories). Identify filenames that: 1) Use auto-generated names (e.g., IMG_1234.jpg, DSC_0056.png, screenshot-2024-01-01.png). 2) Use meaningless names (e.g., image1.jpg, photo.png, pic.jpg). 3) Contain spaces (e.g., 'my photo.jpg'). 4) Use underscores as word separators (e.g., hero_image.jpg instead of hero-image.jpg). 5) Mix uppercase and lowercase letters. Report each problematic filename with its path.
Fix
Rename image files with descriptive, SEO-friendly names: 1) Replace generic names with descriptive ones reflecting the content (e.g., rename IMG_1234.jpg to blue-running-shoes-side-view.jpg). 2) Use lowercase letters only. 3) Replace spaces and underscores with hyphens. 4) Keep names concise but meaningful—3 to 5 words is ideal. 5) Update all references to the renamed file in HTML, CSS, and JavaScript. For large-scale renames, provide a migration script that reads old paths, generates new names, and updates all references.
Show full SKILL.md (114 more words)Show less
Explain
Explain why descriptive filenames matter for image SEO. Google explicitly states it uses filename as a signal for image search ranking. A filename like product-red-leather-wallet.jpg gives Google context about the image before it even analyses the pixels. Generic filenames (image1.jpg, photo.png) provide no signal. Additionally, descriptive filenames improve developer experience—team members can understand what an asset is without opening it.
Code Review
Review image assets, markup, and delivery configuration related to Use descriptive image filenames. Flag exact files or components where format choice, sizing, or loading behavior violates the rule, and describe how to confirm the fix in DevTools.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/images/filename-quality
© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/filename-quality of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
Filename Quality next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Filename Quality this skillthedaviddias/Front-End-Checklist | 74k | — | ~799 | Automated safety check: Pass | MIT | |
| Schema Markupalirezarezvani/claude-skills | 28k | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Schema Markup Generatorsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Remotion Markupremotion-dev/remotion | 63k | 2 repos | ~4.6k | Automated safety check: Pass | Custom licence | |
| Cdn Setupsickn33/agentic-awesome-skills | 47k | 2 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Schema Markupmohitagw15856/pm-claude-skills | 1.4k | — | ~838 | Automated safety check: Pass | MIT |
Similar skills
Schema Markup Generator
sickn33/agentic-awesome-skills
Generate and implement JSON-LD structured data for web apps, blogs, FAQs, and SaaS sites.
- Official
Remotion Markup
remotion-dev/remotion
Content, animation and effects best practices. An agent skill from remotion-dev/remotion.
Cdn Setup
sickn33/agentic-awesome-skills
Configure CDNs for content delivery. An agent skill from sickn33/agentic-awesome-skills.
Schema Markup
mohitagw15856/pm-claude-skills
Generate structured-data (Schema.org / JSON-LD) markup to win rich results in search.
Schema Markup
freekmurze/dotfiles
When the user wants to add, fix, or optimize schema markup and structured data on their site.
More from thedaviddias/Front-End-Checklist
All 390 skills in this repoContent Dates Audit
thedaviddias/Front-End-Checklist
Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.
FAQPage Schema Markup
thedaviddias/Front-End-Checklist
Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.
Favicon Audit and Setup
thedaviddias/Front-End-Checklist
Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.
Content Freshness Signals
thedaviddias/Front-End-Checklist
Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.
Geo Meta Tags Audit
thedaviddias/Front-End-Checklist
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
Improve a Front-End Checklist Rule
thedaviddias/Front-End-Checklist
Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.
Questions about Filename Quality
What does Filename Quality do?
A skill your agent uses when reviewing image assets, markup, and CDN or build transforms related to Use descriptive image filenames. Filename Quality is an agent skill from thedaviddias/Front-End-Checklist. Use when reviewing image assets, markup, and CDN or build transforms related to Use descriptive image filenames.
When should I use Filename Quality?
Filename Quality fits situations like: reviewing image assets; build transforms related to Use descriptive image filenames.
How do I install Filename Quality in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill filename-quality -a claude-code`. Or copy the skill folder (skills/filename-quality in thedaviddias/Front-End-Checklist) into .claude/skills/filename-quality in your project. Claude Code loads it when a task matches its description.
How do I install Filename Quality in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill filename-quality -a codex`. Or copy the skill folder (skills/filename-quality in thedaviddias/Front-End-Checklist) into .agents/skills/filename-quality in your project. Codex loads it when a task matches its description.
Can I use Filename Quality in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill filename-quality -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/filename-quality, .gemini/skills/filename-quality, .github/skills/filename-quality and .opencode/skills/filename-quality in your project.
What does Filename Quality need to run?
SKILL.md names no scripts, command-line tools or credentials: Filename Quality is instructions for the agent only.
Does Filename Quality access the network?
SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.
Is Filename Quality safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Filename Quality use?
Filename Quality is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Filename Quality use?
About 799 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.
What are the alternatives to Filename Quality?
Skills that share tags, products or a category with Filename Quality: Schema Markup (alirezarezvani/claude-skills, 28k stars), Schema Markup Generator (sickn33/agentic-awesome-skills, 47k stars), Remotion Markup (remotion-dev/remotion, 63k stars) and Cdn Setup (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Filename Quality?
thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,421 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.
Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.