Token导航 LogoToken导航

Agent Skill · 研究检索

blog-audit(博客审核)

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

blog-audit 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为执行命令;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 34,372。

总安装 2,233周安装 94GitHub Stars 628下载 782核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

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

这个 Skill 是做什么的

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

用于全站博客健康度扫描,发现孤儿页面、陈旧内容与关键词蚕食问题。适合 SEO 优化团队系统性诊断站点结构缺陷与内容更新计划制定。并行分析多篇文档,生成可执行的任务队列提升维护效率。安装方式:GitHub 仓库,使用 npx skills add 命令添加;支持批量模式加速处理。

注意:部分结论依赖文件命名规范,非常规目录需手动补充路径信息。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

blog-audit 怎么安装?

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

blog-audit 支持哪些 AI 工具?

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

blog-audit 需要什么权限?

权限级别是执行命令。安装流程涉及命令执行,可能通过 npx skills add https://github.com/agricidaniel/claude-blog --skill blog-audit 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

blog-audit 是免费的吗?

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

blog-audit 用的人多吗?

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

blog-audit 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

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

值得选的地方

  • 同时适配 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调用外部服务未明确有提醒
blog-audit

博客审核 · 本页

2,233628执行命令未明确通过

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

SKILL.md 原文

Blog Audit -- Full-Site Health Assessment

Performs a comprehensive blog health assessment across all posts in the project. Scans for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness. Uses parallel subagents for efficient analysis and produces a prioritized action queue.

Audit Process

Step 1: Discover Blog Files

Scan the project for all blog content files:

  • Glob for *.md, *.mdx, *.html in common blog directories
  • Common paths to check:

- content/ - posts/ - blog/ - src/content/ - _posts/ - pages/blog/ - articles/ - src/pages/blog/

  • Filter out non-blog files: README, CHANGELOG, LICENSE, config files, SKILL.md, package.json, node_modules
  • Report: "Found N blog files in [directories]"

If no blog files are found in standard locations, search the entire project root for markdown files with blog-like frontmatter (title, date, description).

Step 2: Parallel Analysis

Spawn subagents via the Task tool for parallel processing across all discovered blog files:

Content Quality Agent
  • Score each post on the 30-point content quality scale
  • Check paragraph length (target 40-80 words, hard limit 150)
  • Check sentence length (target 15-20 words)
  • Evaluate heading structure and question-format headings
  • Assess readability (Flesch Reading Ease 60-70 target)
SEO Optimization Agent
  • Check on-page SEO elements per post:

- Title tag length (50-60 chars) - Meta description (150-160 chars, includes statistic) - H1 presence and uniqueness - Image alt text coverage - Internal and external link counts - URL slug quality

Schema Validation Agent
  • Detect structured data across all posts
  • Validate BlogPosting schema completeness
  • Check FAQ schema presence and format
  • Verify dateModified matches lastUpdated frontmatter
  • Flag missing or malformed schema
Link Health Agent
  • Map internal links across all posts
  • Build a directed link graph
  • Detect orphan pages (zero inbound internal links)
  • Detect dead-end pages (zero outbound internal links)
  • Check for broken internal link targets
  • Recommend bidirectional link opportunities
Freshness Check Agent
  • Read lastUpdated or dateModified from each post's frontmatter
  • Calculate days since last update
  • Flag posts not updated in 90+ days
  • Categorize by refresh priority
AI Readiness Agent
  • Score each post for AI citation readiness
  • Check passage-level citability (120-180 word sections)
  • Evaluate Q&A formatting and entity clarity
  • Check for TL;DR boxes and citation capsules
  • Assess AI crawler accessibility

Step 3: Topic Cannibalization Detection

Analyze across all posts for keyword competition:

  1. Extract primary keyword/topic from each post:

- Title text - H1 heading - Meta description - First paragraph

  1. Normalize keywords (lowercase, remove stop words)
  2. Detect multiple posts targeting the same primary keyword
  3. Flag competing posts with one of these recommendations:

- Merge: Combine two weak posts into one strong post - Redirect: 301 redirect the weaker post to the stronger one - Differentiate: Adjust focus so posts target distinct intents

Step 4: Orphan Page Detection

Build and analyze the internal link graph:

  1. For each blog post, extract all internal links (relative and absolute)
  2. Build an adjacency map: {page -> [pages it links to]}
  3. Build a reverse map: {page -> [pages linking to it]}
  4. Identify orphan pages: posts with zero inbound internal links
  5. Identify dead-end pages: posts with zero outbound internal links
  6. For each orphan, recommend 2-3 existing posts that should link to it based on topic relevance

Step 5: Stale Content Detection

Audit content freshness across all posts:

  1. Read frontmatter fields: lastUpdated, dateModified, date, updated
  2. Calculate days since last update for each post
  3. Categorize by refresh priority:

- High (>180 days): Likely outdated, statistics may be stale - Medium (90-180 days): Review for accuracy, update statistics - Low (<90 days): Recently updated, no immediate action

  1. Estimate refresh effort per post:

- Light refresh: Update statistics, check links (1-2 hours) - Moderate refresh: Rewrite sections, add new data (3-4 hours) - Heavy refresh: Full rewrite recommended (5+ hours)

Step 6: Generate Site-Wide Report

Aggregate all results into a comprehensive report:

Summary Dashboard
## Blog Audit Report

**Audit Date:** [date]
**Total Posts:** N
**Average Score:** XX/100

### Health Overview
| Metric | Count |
|--------|-------|
| Posts Scoring 90+ (Excellent) | N |
| Posts Scoring 70-89 (Good) | N |
| Posts Scoring 50-69 (Needs Work) | N |
| Posts Scoring <50 (Poor) | N |
| Orphan Pages | N |
| Dead-End Pages | N |
| Cannibalization Issues | N |
| Stale Content (90+ days) | N |
Per-Post Table
### Per-Post Scores
| Post | Score | Content | SEO | E-E-A-T | Technical | AI Citation | Issues |
|------|-------|---------|-----|---------|-----------|-------------|--------|
| [filename] | XX/100 | X/25 | X/20 | X/20 | X/15 | X/20 | [count] |
Prioritized Action Queue
### Prioritized Action Queue (Lowest Score First)
| Priority | Post | Score | Top Issue | Recommended Action |
|----------|------|-------|-----------|--------------------|
| 1 | [file] | XX | [issue] | [action] |
| 2 | [file] | XX | [issue] | [action] |
Cannibalization Report
### Topic Cannibalization
| Keyword | Competing Posts | Recommendation |
|---------|----------------|----------------|
| [keyword] | post-a.md, post-b.md | Merge / Redirect / Differentiate |
Orphan Pages
### Orphan Pages (No Inbound Links)
| Page | Inbound Links | Recommended Link Sources |
|------|---------------|--------------------------|
| [file] | 0 | post-a.md, post-b.md, post-c.md |
Stale Content
### Stale Content
| Post | Last Updated | Days Stale | Priority | Refresh Effort |
|------|-------------|------------|----------|----------------|
| [file] | [date] | [N] | High/Med/Low | Light/Moderate/Heavy |

Step 7: Save Report

Save the complete report to blog-audit-report.md in the project root.

After saving, inform the user:

  • Report location: [project-root]/blog-audit-report.md
  • Summary of findings (total posts, average score, critical issues count)
  • Suggest running /blog analyze <file> on the lowest-scoring post first
  • Suggest running /blog geo <file> for AI citation optimization on key posts

平台分布

Codex

37.58%
按下载量换算294

Claude

31.09%
按下载量换算243

Cursor

18.62%
按下载量换算146

Gemini CLI

9.96%
按下载量换算78

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/agricidaniel/claude-blog --skill blog-audit 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

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

继续浏览同类 Skills