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

blog-audit博客审核

Agent Skill

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

总安装

2,233

周安装

94

GitHub Stars

628

下载量

782
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

简介

用于全站博客健康度扫描,发现孤儿页面、陈旧内容与关键词蚕食问题。

  • 适合 SEO 优化团队系统性诊断站点结构缺陷与内容更新计划制定。
  • 并行分析多篇文档,生成可执行的任务队列提升维护效率。
  • 安装方式:GitHub 仓库,使用 npx skills add 命令添加;支持批量模式加速处理。
  • 注意:部分结论依赖文件命名规范,非常规目录需手动补充路径信息。

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

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

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