quality
thedaviddias/Front-End-Checklist · Agent Skill
Evaluates content pages for SEO quality, checking for depth, expertise, and user intent satisfaction.
Jump to install ↓Overview
| Publisher | |
|---|---|
| Repository | thedaviddias/Front-End-Checklist ↗ |
| Skill folder | quality |
| Stars | 74,050 |
| Bundled files | 1 |
| License | MIT |
| Last updated | May 28, 2026 |
| Links | Skill source ↗ · Repository ↗ |
Mozgi check
What we found in the skill files. Details come with a subscription.
Installation
A skill is a folder with a SKILL.md file. Pick your agent and run the commands in a terminal (macOS, Linux or Git Bash on Windows) from your project root.
Copy the prompt into Claude, Codex or another assistant: it will review the skill and install it for you.
Install the “quality” skill from mozgi.io (https://mozgi.io/skills/quality/) for me. 1. Download the archive: https://mozgi.io/skills/quality/download If it fails, take the skill folder from the source: https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/quality 2. Read SKILL.md and the other files. Check the skill is safe: no hidden commands, no sending data elsewhere, no scripts doing something other than described. If anything looks suspicious, stop and tell me. 3. Put the “quality” folder into your agent's skills folder: .claude/skills/ for Claude Code, .agents/skills/ for Codex, .cursor/skills/ for Cursor, .gemini/skills/ for Gemini CLI. Inside the project if we are in one, otherwise in the home folder (~/.claude/skills/ etc.). 4. Make sure <skills folder>/quality/SKILL.md exists. 5. Briefly tell me what this skill does and offer to try it on my task. If you cannot do a step yourself, tell me what to click or type.
git clone --depth 1 --branch main https://github.com/thedaviddias/Front-End-Checklist.git /tmp/Front-End-Checklist mkdir -p .claude/skills cp -r /tmp/Front-End-Checklist/skills/quality .claude/skills/quality
Restart Claude Code — the skill appears in the list; call it manually with /quality. For all projects use ~/.claude/skills.
git clone --depth 1 --branch main https://github.com/thedaviddias/Front-End-Checklist.git /tmp/Front-End-Checklist mkdir -p .agents/skills cp -r /tmp/Front-End-Checklist/skills/quality .agents/skills/quality
Codex looks for skills in .agents/skills from the current folder up to the repo root; call one with /skills or $quality. For all projects use ~/.agents/skills.
git clone --depth 1 --branch main https://github.com/thedaviddias/Front-End-Checklist.git /tmp/Front-End-Checklist mkdir -p .cursor/skills cp -r /tmp/Front-End-Checklist/skills/quality .cursor/skills/quality
Cursor picks the skill up on start; call it with “/” in Agent chat. Cursor also reads .claude/skills and .agents/skills. For all projects use ~/.cursor/skills.
git clone --depth 1 --branch main https://github.com/thedaviddias/Front-End-Checklist.git /tmp/Front-End-Checklist mkdir -p .gemini/skills cp -r /tmp/Front-End-Checklist/skills/quality .gemini/skills/quality
Gemini CLI offers to activate the skill when a task matches — you approve it. For all projects use ~/.gemini/skills.
Read SKILL.md and any companion files before deciding whether to install. Click a file to preview it.
SKILL.md contents
Original author text · read-onlyPublish high-quality content
Google's Search Quality Rater Guidelines and Helpful Content system reward pages that demonstrate genuine expertise and fully satisfy user intent—low-quality pages are algorithmically suppressed site-wide.
Quick Reference
- Content quality is Google's primary ranking differentiator—E-E-A-T applies to every page
- Thin content (low word count, generic text) is a leading cause of ranking loss
- Each page must have a clear primary purpose and fully satisfy user intent
- First-hand experience, expert authorship, and cited sources raise quality signals
Check
Evaluate this page's content for E-E-A-T signals: Does it demonstrate first-hand experience or expertise? Does it fully answer the apparent search intent? Is the information accurate, specific, and supported by evidence? Is there meaningful depth beyond what competitors cover? Identify specific quality gaps.
Fix
Identify the primary search intent for this page. Rewrite or expand the content to: (1) fully satisfy that intent, (2) add specific details, examples, or data not found on competing pages, (3) attribute claims to authoritative sources, (4) add author byline with relevant credentials, (5) update any outdated information.
Explain
Google's ranking systems are designed to surface content that demonstrates Experience, Expertise, Authoritativeness, and Trustworthiness (E-E-A-T). Content that is generic, lacks depth, or does not fully answer user questions is classified as 'unhelpful' and deprioritised in rankings. High-quality content is the most durable long-term SEO investment.
Code Review
Analyse the page content for quality signals: (1) Word count — is the topic covered in appropriate depth? (2) Specificity — are claims backed by data or examples? (3) Authorship — is a named author with credentials visible? (4) Freshness — does the page show a publication or updated date? (5) Sources — are external authoritative sources cited? (6) Originality — does the content offer unique insights not found on competing pages?
---
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/seo/quality
Frequently asked questions
What does the quality skill do?
Evaluates content pages for SEO quality, checking for depth, expertise, and user intent satisfaction.
How do I install quality?
Open the “Installation” block on this page and pick your agent — Claude Code, Codex, Cursor or Gemini CLI — for ready-made commands that copy the skill folder to the right place. Or copy the prompt from the “Via assistant” tab and let the assistant review and install the skill.
Which AI models work with quality?
Skills are plain Markdown instructions (the Agent Skills format), so quality works with any agent that reads SKILL.md: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and more. The model loads the instructions only when a task matches the skill's description.
Is quality free?
The skill is published openly by thedaviddias under the MIT license. The skill itself costs nothing — you only pay your AI provider for the tokens you use.
Is it safe to install skills?
A skill is a set of instructions your agent will follow, so read SKILL.md and its companion files before installing. Scripts in the skill folder only run if your agent runs them — keep an eye on what it does and do not grant unnecessary permissions.
How is a skill different from an MCP server or a plugin?
An MCP server or plugin gives the model new tools — code that runs and returns a result. A skill gives it knowledge and process: how to approach a task, which steps to follow and what good output looks like. It needs no server or API key.