quality
thedaviddias/Front-End-Checklist · Agent Skill
評估內容頁面的 SEO 品質,檢查深度、專業知識和使用者意圖滿意度。
前往安裝 ↓總覽
| 發布者 | |
|---|---|
| 儲存庫 | thedaviddias/Front-End-Checklist ↗ |
| 技能資料夾 | quality |
| 星 | 74,050 |
| 附帶檔案 | 1 |
| 授權 | MIT |
| 最近更新 | 2026年5月28日 |
| 連結 | 技能原始碼 ↗ · 儲存庫 ↗ |
Mozgi 檢查
我們在技能檔案中發現的內容。詳細資訊需訂閱。
安裝
技能就是一個含 SKILL.md 的資料夾。選擇你的代理,在專案根目錄的終端機(macOS、Linux 或 Windows 的 Git Bash)執行指令。
把提示貼到 Claude、Codex 或其他助理:它會自行檢查並安裝技能。
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
重新啟動 Claude Code — 技能就會出現在清單中,手動呼叫:/quality。要套用到所有專案,請放在 ~/.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 會從目前資料夾往上到儲存庫根目錄,在 .agents/skills 中尋找技能;用 /skills 或 $quality 呼叫。所有專案:~/.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 啟動時會載入技能;在 Agent 聊天輸入「/」呼叫。Cursor 也會讀取 .claude/skills 與 .agents/skills。所有專案:~/.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 會提議啟用技能,由你確認。所有專案:~/.gemini/skills。
安裝前請先檢視 SKILL.md 與相關檔案。點擊檔案即可預覽。
SKILL.md 內容
作者原文 · 唯讀Publish 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
常見問題
quality 技能有什麼用途?
評估內容頁面的 SEO 品質,檢查深度、專業知識和使用者意圖滿意度。
如何安裝 quality?
打開本頁的「安裝」區塊並選擇你的代理 — Claude Code、Codex、Cursor 或 Gemini CLI:那裡有把技能資料夾複製到正確位置的現成指令。也可以複製「透過助理」分頁中的提示,讓助理自行檢查並安裝技能。
quality 適用哪些 AI 模型?
技能是純 Markdown 指示(Agent Skills 格式),因此 quality 適用任何讀取 SKILL.md 的代理:Claude Code、Codex、Cursor、Gemini CLI、GitHub Copilot、OpenCode 等。只有在任務符合技能描述時,模型才會載入指示。
quality 是免費的嗎?
此技能由 thedaviddias 公開發布,採用 MIT 授權。技能本身免費 — 你只需向 AI 供應商支付實際使用的 token 費用。
安裝技能安全嗎?
技能是代理會遵循的指示,安裝前請閱讀 SKILL.md 及相關檔案。技能資料夾中的腳本只有在代理執行時才會運行 — 留意它的動作,不要授予多餘權限。
技能和 MCP 伺服器或外掛有何不同?
MCP 伺服器或外掛為模型提供新工具 — 會執行並回傳結果的程式碼。技能提供的是知識與流程:如何處理任務、要遵循哪些步驟、好的成果長什麼樣子。它不需要伺服器或 API 金鑰。