Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

seo-aeo-content-quality-auditorSEO AEO 内容 quality auditor

Agent Skill

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

总安装

396

周安装

17

GitHub Stars

35,905

下载量

139
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:seo-aeo-content-quality-auditor(SEO AEO 内容 quality auditor)
来源仓库:https://github.com/sickn33/antigravity-awesome-skills
仓库路径:skills/seo-aeo-content-quality-auditor
安装命令:
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill seo-aeo-content-quality-auditor
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill seo-aeo-content-quality-auditor

简介

seo-aeo-content-quality-auditor 用于辅助文档、README、Markdown 和内容稿件的整理与改写,适合提炼结构或统一术语。

  • 它能帮助 Agent 检查链接或把零散材料整理成可读文档。
  • 使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论。
  • 涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

SEO-AEO Content Quality Auditor

Overview

Runs a dual SEO + AEO audit on any landing page or blog post. Produces an overall score, SEO score, AEO score, and readability score — each out of 100 — with severity-ranked issue lists (Critical / Warning / Polish), exact fix instructions for every issue, and projected scores after all fixes are applied.

Part of the SEO-AEO Engine.

When to Use This Skill

  • Use when auditing a landing page or blog post before publishing
  • Use after the blog-writer or landing-page-writer skill outputs content
  • Use when diagnosing why existing content is underperforming in search
  • Use when you need a scored, actionable SEO and AEO report

How It Works

Step 1: Run SEO Checks

Verify keyword density, H1/H2/H3 structure, meta elements, word count, sentence length, and paragraph density. Flag every issue with its severity.

Step 2: Run AEO Checks

Check for TL;DR block, definition sentence, FAQ section (minimum 4 entries), bullet and numbered lists, comparison table, and extractable direct answers. Score each signal as found or missing.

Step 3: Run Readability Checks

Check passive voice ratio, transition word presence, wall-of-text paragraphs, subheading frequency, and reading level.

Step 4: Score and Prioritise

Calculate three scores out of 100. Sort all issues into Critical (fix before publishing), Important (fix soon), and Polish (optional improvements). Generate projected scores after all fixes are applied.

Scoring System

ScoreStatusLabel
85–100✅ PassStrong
70–84⚠️ WarnAcceptable
50–69🔶 WeakNeeds work
0–49❌ FailDo not publish

Examples

Example: Audit Summary

Overall Score: 84/100 ⚠️ Acceptable SEO Score: 88/100 ✅ Pass AEO Score: 74/100 ⚠️ Acceptable Readability: 91/100 ✅ Pass Verdict: Strong SEO foundation. AEO needs a TL;DR block and one more FAQ entry before publishing. 🔴 Critical (fix before publishing):

AEO: No TL;DR block found Fix: Add a 2–3 sentence direct-answer block in a blockquote immediately after the H1.

🟡 Important (fix soon): 2. AEO: FAQ has 3 entries — minimum is 4 Fix: Add one more FAQ entry using a secondary keyword as the question. Projected score after fixes: 93/100 ✅

Best Practices

  • Do: Fix all Critical issues before publishing — they block AEO extraction
  • Do: Use the projected score to prioritise which fixes to make first
  • Do: Run the audit on both the landing page and blog post in the same session
  • Don't: Publish content scoring below 50/100 overall
  • Don't: Ignore AEO warnings — they directly affect AI engine citation probability

Common Pitfalls

  • Problem: SEO score is high but AEO score is low Solution: Traditional SEO tools miss AEO signals entirely. Run the AEO checklist separately and treat it as equally important.
  • Problem: Fix list is long and overwhelming Solution: Work through Critical issues only first, re-run the audit, then tackle Important issues.

Related Skills

  • @seo-aeo-blog-writer — produces the content this skill audits
  • @seo-aeo-landing-page-writer — produces landing pages this skill audits
  • @seo-aeo-schema-generator — uses audit output to determine schema priorities

Additional Resources

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

38.25%
按下载量换算53

Claude

29.68%
按下载量换算41

Cursor

19.16%
按下载量换算27

Gemini CLI

9.22%
按下载量换算13

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills