blog-rewrite

Rewrite and optimize existing blog posts for Google SEO (May 2026 Core Update, March 2026 core/spam context, June 2026 spam context, E-E-A-T) and AI citation visibility as one SEO discipline. Full rewrite for both Google rankings AND AI citations. For AI-citation-only audit (no Google work), use blog-geo instead. Replaces fabricated statistics with sourced data, applies answer-first formatting, adds Pixabay/Unsplash images, generates built-in SVG charts, validates Article-priority schema, performs AI content detection, adds citation capsules and information gain markers, and updates freshness signals. Works with any blog format (MDX, markdown, HTML). Use when user says "rewrite blog", "optimize blog", "update blog", "improve blog", "fix blog", "refresh blog post", "blog optimization".

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-sequenced, highly actionable multi-phase workflow with strong validation feedback loops and clean progressive disclosure via a labeled references list. Its only weakness is conciseness: a few sections (notably the Phase 6 report template and enumerated phrase lists) are heavier than necessary.

Suggestions

Move the large Phase 6 summary-report template into a reference file (e.g. references/summary-template.md) and keep only the required fields listed inline, cutting the repeated per-category breakdown blocks.

Relocate the enumerated AI-phrase list and its replacement mappings to the already-referenced agents/blog-writer.md or a dedicated reference, keeping only a short pointer and a few examples in SKILL.md.

Group the inline version markers (v1.8.0, v1.9.0) into a single changelog/deprecation note so they stop interrupting the workflow narrative.

Dimension	Reasoning	Score
Conciseness	Most content is task-specific and assumes Claude's competence, but the long Phase 6 report template and inline enumeration of AI-phrase/replacement lists could be tightened or externalized, so it sits at 'mostly efficient but could be tighter' rather than fully lean.	2 / 3
Actionability	Provides fully executable commands (e.g. `python3 scripts/blog_preflight.py --draft <folder> --strict`, `python3 scripts/blog_render.py`), concrete search-query templates, and copy-ready markdown blocks, reaching the executable/copy-paste-ready anchor.	3 / 3
Workflow Clarity	Six phases are explicitly sequenced with validation checkpoints (Phase 5 quality gates, Phase 5.5 preflight exit codes, 'maximum 3 iterations' feedback loop, 'Wait for user approval'), matching the clear-sequence-with-explicit-validation anchor.	3 / 3
Progressive Disclosure	A clearly signaled 'Key references' list with one-line descriptions points one level deep to split-out material (scoring, E-E-A-T, linking, visual-media, slop-detection, delivery-contract), and inline references are placed at the relevant step, giving easy navigation.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, and complete, naming concrete actions and an explicit 'Use when' clause while staying in third person and distinguishing itself from the related blog-geo skill. No weak dimensions; it matches the top anchor on every rubric dimension.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("Replaces fabricated statistics with sourced data, applies answer-first formatting, adds images, generates SVG charts, and updates freshness signals"), matching the top anchor rather than the domain-only level 2.	3 / 3
Completeness	Explicitly answers both what (rewrite/optimize existing posts with the listed actions) and when (the "Use when user says..." clause), so it clears the explicit-trigger bar rather than capping at 2.	3 / 3
Trigger Term Quality	Provides natural phrasings a user would actually say ("Use when user says 'rewrite blog', 'optimize blog', 'update blog', 'improve blog', 'fix blog'"), giving good coverage of trigger variations.	3 / 3
Distinctiveness Conflict Risk	Carves a clear niche and even disambiguates from a sibling skill ("For AI-citation-only audit (no Google work), use blog-geo instead"), making misfires unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	14 / 16 Passed

Repository: AgriciDaniel/claude-blog
Path: brain/.raw/sources/claude-blog-skill/skills/blog-rewrite/SKILL.md
Commit: aec971a

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.