Token导航 LogoToken导航TokenDH.com
研究检索敏感数据github未标认证来源可访问许可证需确认审计提醒

seo-audit-fullSEO 审核 full

Agent Skill

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

总安装

3,354

周安装

137

GitHub Stars

298

下载量

1,085
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

简介

seo-audit-full 用于辅助安全审计、权限检查、凭据风险和认证流程排查,适合梳理敏感配置或分析鉴权逻辑。

  • 它能帮助 Agent 生成安全复核清单或检查依赖风险。
  • 使用时不能把工具输出直接当最终结论。
  • 涉及密钥、令牌、用户数据或生产系统时,应先确认最小权限、脱敏方式和操作边界。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

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:

  • statuspass / 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

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

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、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

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

来源信息

继续浏览同类 Skills