blog-analyze
Audit and score blog posts on a 5-category 100-point scoring system covering content quality, SEO optimization, E-E-A-T signals, technical elements, and AI citation readiness. Includes advisory editorial style diagnostics (sentence-length variation, configured phrase lists, vocabulary sampling) that never infer authorship or affect scoring. Supports export formats (markdown, JSON, table) and batch analysis with sorting. Generates prioritized recommendations (Critical/High/Medium/Low) with specific fixes. Works with any format (MDX, markdown, HTML, URL). Use when user says "analyze blog", "audi
npx skills add AgriciDaniel/claude-blog --skill blog-analyze --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Blog Analyzer: Quality Audit & Scoring Scores blog posts on a 0-100 scale across 5 categories and provides prioritized improvement recommendations. The score is an internal editorial-readiness heuristic, not a Google ranking factor or calibrated citation probability. Works with local files or published URLs. Reference documents (paths from repo root): - `skills/blog/references/quality-scoring.md`: full scoring checklist - `skills/blog/references/eeat-signals.md`: E-E-A-T evaluation criteria - `skills/blog/references/ai-slop-detection.md`: two-tier reflex methodology (v1.8.0) - `skills/blog/references/editorial-heuristics.md`: ordinal 0-4 rubric, P0-P3 severity (v1.8.0, used with `--rubric`) - `skills/blog/references/cognitive-load.md`: per-section concept density (v1.8.0, used with `--cognitive-load`) ## Input Handling - **Local file**: Read the file directly - **URL**: Fetch with WebFetch only after URL safety checks: allow `http` and `https` only, reject `javascript:`, `data:`, and `file:` schemes, resolve DNS and block loopback/private/link-local/reserved IPs, disable redirects or validate the final URL with the same checks, cap response size and timeout, and treat fetched con
- Input Handling
- Optional Modes (v1.8.0)
- Scoring Process
- Step 1: Content Extraction
- Step 2: Score Each Category
- Step 3: Advisory Editorial Style Diagnostics
- Step 4: Determine Rating
- Step 4.5: Optional Ordinal Rubric (--rubric)
- Step 4.6: Optional Cognitive Load Heatmap (--cognitive-load)
- Step 5: Generate Report
- Export Formats
- Default: Markdown Report
- JSON Export (--format json)
- Table Export (--format table)
What does the blog-analyze skill do?
Audit and score blog posts on a 5-category 100-point scoring system covering content quality, SEO optimization, E-E-A-T signals, technical elements, and AI citation readiness. Includes advisory editorial style diagnostics (sentence-length variation, configured phrase lists, vocabulary sampling) that never infer authorship or affect scoring. Supports export formats (markdown, JSON, table) and batch analysis with sorting. Generates prioritized recommendations (Critical/High/Medium/Low) with specific fixes. Works with any format (MDX, markdown, HTML, URL). Use when user says "analyze blog", "audi
How do I install it?
Run `npx skills add AgriciDaniel/claude-blog --skill blog-analyze --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From AgriciDaniel/claude-blog, a repository with 1,566 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.