Token导航 LogoToken导航

Agent Skill · 研究检索

blog-seo-check(博客 SEO check)

blog-seo-check 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

blog-seo-check 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 32,113。

总安装 2,571周安装 104GitHub Stars 619下载 807核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/agricidaniel/claude-blog --skill blog-seo-check

这个 Skill 是做什么的

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

blog-seo-check 用于对已完成博客文章执行全面 SEO 校验,适合在 Codex、Claude、Cursor、Gemini CLI 中发布前做最后检查时使用。它验证标题结构、元标签、链接锚文本与图片 alt 属性,输出 pass/fail 清单。使用时读取目标文件并比对最佳实践规则,提供具体修复指引。

安装前建议确认文件读写权限及是否支持多语言内容检测。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/blog-seo-check

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

blog-seo-check 怎么安装?

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

blog-seo-check 支持哪些 AI 工具?

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

blog-seo-check 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

blog-seo-check 是免费的吗?

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

blog-seo-check 用的人多吗?

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

blog-seo-check 安全吗?

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

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

值得选的地方

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

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

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

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 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调用外部服务未明确有提醒
blog-seo-check

博客 SEO check · 本页

2,571619需要联网未明确有提醒

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

SKILL.md 原文

Blog SEO Check -- Post-Writing Validation

Runs a comprehensive on-page SEO validation against a completed blog post and generates a pass/fail checklist with specific fixes for each failure. Designed to run after writing - catches issues before publishing.

Workflow

Step 1: Read Content

Read the target file and extract:

  • Frontmatter - title, description, date, lastUpdated, author, tags, canonical, og:image, slug/URL
  • Heading structure - H1, H2, H3 hierarchy with full text
  • Links - All internal and external links with anchor text
  • Meta tags - OG tags, Twitter Card tags, canonical URL
  • Body content - Full text for keyword and structural analysis

If the user provides a URL instead of a file path, use WebFetch to retrieve the page and extract the relevant elements.

Step 2: Title Tag Validation

CheckPass Criteria
Character count40-60 characters (no truncation in SERPs)
Keyword placementPrimary keyword in first half of title
Power wordContains at least one power word (e.g., Guide, Best, How, Why, Essential, Proven, Complete)
Truncation riskNo critical meaning lost if truncated at 60 chars
UniquenessNot generic - specific to the content

Step 3: Meta Description

CheckPass Criteria
Character count150-160 characters
Statistic includedContains at least one specific number or data point
Value propositionEnds with clear reader benefit or value proposition
Keyword presencePrimary keyword appears naturally (not stuffed)
No keyword stuffingKeyword appears at most once
Call to actionImplies action (learn, discover, find out, see)

Step 4: Heading Hierarchy

CheckPass Criteria
Single H1Exactly one H1 tag (the title)
No skipped levelsH1 -> H2 -> H3, never H1 -> H3 or H2 -> H4
Keyword in headingsPrimary keyword in 2-3 headings (natural, not forced)
Question format60-70% of H2 headings are questions
H2 count6-8 H2 sections for a standard blog post
Heading lengthEach heading under 70 characters

Step 5: Internal Links

CheckPass Criteria
Link count3-10 internal links per post
Anchor textDescriptive (not "click here" or "read more")
BidirectionalCheck if linked pages also link back (flag if not)
No orphan statusPost links to at least 3 other pages on the site
Link distributionLinks spread across the post, not clustered
No self-linksPost does not link to itself

Use Grep and Glob to scan the project for existing blog content and verify bidirectional linking where possible.

Step 5.5: Link Deduplication

CheckPass Criteria
No duplicate URLsEach URL appears at most once in body content
Best instance keptIf duplicates exist, keep the one with most descriptive anchor text
Navigation exemptHeader/footer nav links don't count toward body dedup
Fragment normalizationURLs with different #fragments treated as same URL

For each duplicate found:

  1. Normalize URLs (strip trailing slashes, query parameters, fragments)
  2. Score each instance by anchor text descriptiveness (keyword-rich > generic)
  3. Recommend keeping the highest-scored instance, removing others
  4. Deduct 1 point per duplicate from SEO Optimization score

Google records 1-2 anchor texts per URL per page (Zyppy 2023). Optimal: link to same URL once in body content; 5-10 internal links per 2,000 words; max ~50 total links per page.

Step 6: External Links

CheckPass Criteria
Source tierLinks to tier 1-3 sources only (authoritative, not SEO blogs)
Broken linksUse WebFetch to verify top external links are reachable
Rel attributesExternal links have appropriate rel attributes (nofollow for sponsored/UGC)
Link countAt least 3 external links to authoritative sources
No competitor linksNot linking to direct competitors unnecessarily

Step 7: Canonical URL

CheckPass Criteria
PresentCanonical URL is defined in frontmatter or meta tags
Correct formatFull absolute URL (https://domain.com/path)
Trailing slashConsistent with site convention (no mixed trailing slashes)
Self-referencingCanonical points to the page itself (unless intentional cross-domain)

Step 8: OG Meta Tags

CheckPass Criteria
og:titlePresent, matches or complements the title tag
og:descriptionPresent, 150-160 characters, compelling for social sharing
og:imagePresent, 1200x630 minimum dimensions, absolute URL
og:typeSet to "article" for blog posts
og:urlPresent, matches canonical URL
og:site_namePresent, matches site/brand name

Step 9: Twitter Card

CheckPass Criteria
twitter:cardSet to "summary_large_image" for blog posts
twitter:titlePresent, under 70 characters
twitter:descriptionPresent, under 200 characters
twitter:imagePresent, same as or similar to og:image
twitter:sitePresent if the site has a Twitter/X account

Step 10: URL Structure

CheckPass Criteria
LengthShort - under 75 characters for the path portion
Keyword presencePrimary keyword or close variant in the URL slug
No datesURL does not contain /2025/ or /2026/ date segments
No special charactersOnly lowercase letters, numbers, and hyphens
LowercaseEntire URL path is lowercase
No stop wordsMinimal use of "the", "a", "and", "of" in slug
No file extensionNo.html or.php in the URL (clean URLs)

Step 11: Generate Report

Output a comprehensive SEO validation report in this format:

## SEO Validation Report: [Title]

**File**: [path or URL]
**Date**: [check date]
**Overall**: [X/Y checks passed] - [PASS/NEEDS WORK/FAIL]

### Results

| # | Check | Status | Details | Fix |
|---|-------|--------|---------|-----|
| 1 | Title length | PASS | 52 chars | - |
| 2 | Title keyword | PASS | "keyword" in first half | - |
| 3 | Title power word | FAIL | No power word found | Add "Guide", "Essential", or "Complete" |
| 4 | Meta description length | PASS | 155 chars | - |
| 5 | Meta description stat | FAIL | No number found | Add a key statistic from the post |
| ... | ... | ... | ... | ... |

### Summary

**Passed**: [N] checks
**Failed**: [N] checks

### Priority Fixes
1. [Most impactful fix - what to change and where]
2. [Second most impactful fix]
3. [Third most impactful fix]

### Notes
- [Any observations about overall SEO health]
- [Suggestions for improvement beyond the checklist]

Status values:

  • PASS - Meets the criteria
  • FAIL - Does not meet the criteria, fix provided
  • WARN - Partially meets criteria or edge case, recommendation provided
  • N/A - Not applicable (e.g., no Twitter Card tags if site has no X account)

Optional: Live Performance Check (blog-google)

If the post has a published URL and blog-google credentials are available:

  1. Check credentials: python3 skills/blog-google/scripts/run.py google_auth --check --json
  2. If Tier 0+, run PageSpeed: python3 skills/blog-google/scripts/run.py pagespeed_check <url> --json
  3. Append to report:

- Lighthouse Performance, Accessibility, Best Practices, SEO scores - CWV field data (LCP, INP, CLS) with traffic-light ratings - Top 3 opportunities with estimated savings

  1. Falls back silently if credentials unavailable or URL not published.

平台分布

Codex

33.88%
按下载量换算273

Claude

31.39%
按下载量换算253

Cursor

16.48%
按下载量换算133

Gemini CLI

8.66%
按下载量换算70

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

继续浏览同类 Skills