Token导航 LogoToken导航

Agent Skill · 研究检索

seo-audit-full(SEO 审核 full)

用于辅助安全审计、权限检查、凭据风险、认证流程和常见漏洞排查。它适合让 Agent 梳理敏感配置、检查依赖风险、分析鉴权逻辑或生成安全复核清单。使用时不能把工具输出直接当最终结论,涉及密钥、令牌、用户数据或生产系统时,应先确认最小权限、脱敏方式和操作边界。

seo-audit-full 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为接触敏感数据;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 27,645。

总安装 3,354周安装 137GitHub Stars 298下载 1,085核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/jeffli1993/seo-audit-skill --skill seo-audit-full

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

seo-audit-full 用于辅助安全审计、权限检查、凭据风险和认证流程排查,适合梳理敏感配置或分析鉴权逻辑。它能帮助 Agent 生成安全复核清单或检查依赖风险。使用时不能把工具输出直接当最终结论。涉及密钥、令牌、用户数据或生产系统时,应先确认最小权限、脱敏方式和操作边界。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/seo-audit-full

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/jeffli1993/seo-audit-skill --skill seo-audit-f…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

seo-audit-full 怎么安装?

在终端执行 npx skills add https://github.com/jeffli1993/seo-audit-skill --skill seo-audit-full。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

seo-audit-full 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

seo-audit-full 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

seo-audit-full 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

seo-audit-full 用的人多吗?

公开数据是累计安装 3,354 次,近一周安装 137 次,下载 1,085 次,GitHub 298 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

seo-audit-full 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
seo-audit-full

SEO 审核 full · 本页

3,354298接触敏感数据未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

seo-audit-full — Advanced Full SEO Audit

Full = Basic + Extra Checks. This skill runs all checks from seo-audit (basic) first, then adds advanced modules on top. Both are single-page audits — Full simply covers more dimensions and provides deeper analysis.


When to Use This Skill

Use seo-audit-full when the user says any of the following:

  • "deep audit" / "advanced audit" / "technical SEO audit"
  • "full SEO audit" / "full report" / "key report"
  • "comprehensive SEO review" / "audit everything"
  • After seo-audit (basic) runs: "what else?", "go deeper", "full version"

Input Expected

InputRequiredNotes
Page URLYesThe primary page to audit
Primary keywordRecommendedImproves content relevance scoring
Raw HTML / source codeOptionalEnables more accurate on-page analysis
GSC API credentialsOptionalEnables search performance analysis (future)

Architecture: Full = Basic + Extra

┌─────────────────────────────────────────────────────────────┐
│  seo-audit-full Workflow                                    │
│                                                             │
│  Phase 1: Run ALL basic scripts (../seo-audit/scripts/)     │
│  ┌──────────────────────────────────────────────────────┐   │
│  │  check-site.py      → robots.txt, sitemap, 404, URL  │   │
│  │  check-page.py      → title, H1, meta desc, slug     │   │
│  │  check-schema.py    → JSON-LD validation              │   │
│  │  check-pagespeed.py → PageSpeed Insights              │   │
│  │  fetch-page.py      → raw HTML for analysis           │   │
│  └──────────────────────────────────────────────────────┘   │
│                          ↓                                  │
│  Phase 2: Run full-only scripts (./scripts/)                │
│  ┌──────────────────────────────────────────────────────┐   │
│  │  check-social.py    → OG Tags + Twitter Card          │   │
│  │  (more scripts added here as modules grow)            │   │
│  └──────────────────────────────────────────────────────┘   │
│                          ↓                                  │
│  Phase 3: LLM-only advanced checks                         │
│  ┌──────────────────────────────────────────────────────┐   │
│  │  E-E-A-T content quality scoring                      │   │
│  │  Duplicate content signals                            │   │
│  │  Anchor text quality assessment                       │   │
│  └──────────────────────────────────────────────────────┘   │
└─────────────────────────────────────────────────────────────┘

Output

Produce an Advanced Full SEO Audit Report by filling the template at assets/report-template.html, then save it to a file — never print raw HTML to the terminal.

File naming: reports/<hostname>-<slug>-full-audit.html

https://example.com/blog/best-tools → reports/example-com-blog-best-tools-full-audit.html
https://example.com/                → reports/example-com-full-audit.html

After saving, tell the user:

✅ Full Report saved → reports/example-com-full-audit.html
   Open it now? (yes / no)

If yes → run: open reports/example-com-full-audit.html


Scripts

Run scripts in two phases. All output structured JSON — use it directly as evidence.

Dependencies: pip install requests

Phase 1: Basic scripts (from ../seo-audit/scripts/)

# 1. site-level checks (robots.txt + sitemap.xml + 404 + URL canonicalization)
python ../seo-audit/scripts/check-site.py https://example.com

# 2. page-level checks (H1, title, meta description, canonical, URL slug)
python ../seo-audit/scripts/check-page.py https://example.com --keyword "primary keyword"

# 3. fetch raw HTML for downstream scripts
python ../seo-audit/scripts/fetch-page.py https://example.com --output /tmp/page.html

# 4. JSON-LD schema validation
python ../seo-audit/scripts/check-schema.py --file /tmp/page.html

# 5. PageSpeed Insights
python ../seo-audit/scripts/check-pagespeed.py https://example.com

Phase 2: Full-only scripts (from ./scripts/)

# 6. Social tags: OG + Twitter Card validation
python scripts/check-social.py --file /tmp/page.html
# Or directly from URL:
python scripts/check-social.py https://example.com

Each script exits with code 0 (all pass/warn) or 1 (any fail/error).


Scope — Full Audit Check Whitelist

Full includes everything in Basic plus the items marked ★ below.

Site-Level Checks (in {{site_checks_html}})

Inherited from Basic:

  • robots.txt · sitemap.xml · 404 Handling · URL Canonicalization · i18n / hreflang

E-E-A-T Checks (in {{eeat_checks_html}})

Inherited from Basic:

  • About Us · Contact · Privacy Policy · Terms of Service · Media/Partners (only if present)

Page-Level Checks (in {{page_checks_html}}), output in this exact order:

Inherited from Basic: PageSpeed (Mobile) · PageSpeed (Desktop) · URL Slug · Title Tag · Meta Description · H1 Tag · Canonical Tag · Image Alt Text · Word Count · Keyword Placement · Heading Structure · Internal Links · Schema (JSON-LD)

★ Full-only additions:

  • OG Tags — og:title, og:description, og:image, og:type, og:url presence and validity
  • Twitter Card — twitter:card type, title/description/image (with OG fallback detection)

How to Use Script JSON Output

Same rules as Basic — map each field's status directly to the report check table:

  • status → pass / warn / fail / error → badge in report
  • detail → starting point for Evidence line
  • Do not contradict script output unless you have additional observable evidence

For check-social.py output:

  • og.status → OG Tags row status
  • twitter_card.status → Twitter Card row status
  • og.fields.* → individual field details for the detail cell
  • twitter_card.fields.* → individual field details, note fallback fields

LLM Review Instructions

Inherited from Basic

All llm_review_required: true handling from seo-audit applies here unchanged: H1 semantic judgment, Title keyword position, URL Slug evaluation, Meta Description quality. See seo-audit/SKILL.md for full instructions.

Full-only LLM checks

OG Tags quality (always review):

og:title   : Does it differ meaningfully from <title>? It should be optimized for social sharing.
og:description : Is it compelling for social feeds? Different focus than meta description is OK.
og:image   : Is the URL an actual image path (not a page URL)?

Twitter Card completeness:

If twitter:card is "summary_large_image", twitter:image (or og:image fallback) must be
at least 300x157px. Flag if the image URL looks like a small icon or favicon.

Recommended Workflow

  1. Acknowledge scope — confirm this is a full audit; note any missing data or API keys
  2. Infer primary keyword — same logic as Basic
  3. Phase 1: Run ALL basic scripts — check-site → check-page → fetch-page → check-schema → check-pagespeed
  4. Basic checks — 404 handling, URL canonicalization, E-E-A-T trust pages, i18n/hreflang (same as Basic)
  5. Phase 2: Run full-only scripts — check-social
  6. LLM-only advanced checks — E-E-A-T content quality, duplicate content signals, anchor text quality
  7. Summarize findings — Evidence / Impact / Fix format
  8. Priority actions — top 5 highest-impact fixes with effort/impact tags
  9. Render report — save to reports/<hostname>-<slug>-full-audit.html

Report Detail Writing Rules

Same as Basic — strict formatting:

Pass → one short phrase. No lists, no elaboration.

Warn → one <div class="detail-issue"> with ≤2 bullet points. One <div class="detail-fix">.

Fail → same as Warn. Lead with the exact failure.


Mandatory Finding Format

**Finding: [Finding Title]**

- **Evidence:** [Observable fact, data point, or marked assumption]
- **Impact:** [SEO / UX consequence]
- **Fix:** [Actionable recommendation with example]

For Priority Actions, add effort/impact tags:

1. [High Impact / Low Effort] Fix og:image — social shares currently show no preview.

Reference Files

平台分布

Codex

36.31%
按下载量换算394

Claude

31.41%
按下载量换算341

Cursor

19.45%
按下载量换算211

Gemini CLI

8.37%
按下载量换算91

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills