blog

Full-lifecycle blog engine with 31 sub-skills, 12 templates, 100-point scoring, and 5 agents. Routes requests to the right sub-skill: writing, rewriting, analysis, outlines, audits, schema, charts, images, repurposing, AI citation SEO, FLOW prompts, topic clusters, and multilingual publishing. Optimized for Google rankings, E-E-A-T, and AI citations. Supports any platform. Use when user says "blog", "blog post", "blog audit", "topic cluster", "multilingual blog", or any /blog subcommand.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%Weight 40%Scale 1-5

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

A highly actionable, well-structured orchestrator skill with excellent workflow validation and progressive disclosure to 22 real reference files. Its main weakness is conciseness: conceptual over-explanation in the security section, scattered version/date stamps, and some duplicated command listings.

Suggestions

Move the detailed Untrusted-Data Contract / nonce rationale into a dedicated reference file and keep only the invocation contract inline, trimming the security concept explanation Claude can infer.

Consolidate the Quick Reference command table and the Command Routing list into one structure to remove duplication, and move version-history annotations (v1.8.0, v1.9.0, etc.) into a changelog reference rather than the body.

Relocate time-sensitive Google update dates ('May 2026 Core Update', 'March/June 2026 spam enforcement') to the google-landscape-2026.md reference so the intro prose stays stable and concise.

Dimension	Reasoning	Score
Conciseness	Mostly efficient dense reference tables, but several padded sections could be tightened: the nonce/security rationale over-explains concepts Claude can infer, version annotations (v1.8.0, v1.9.0, v1.8.3…) and date-stamped prose ('May 2026 Core Update, March 2026…') add noise outside a deprecated section, and the Quick Reference table duplicates the Command Routing list. Not a 2 because the bulk is genuinely lean reference material.	3 / 5
Actionability	Copy-paste-ready bash blocks with real flags and absolute-path guards, concrete /blog commands, and specific thresholds (reviewer score >= 90/100, zero P0, max 3 iterations, 20% QoQ decline) cover the common cases fully.	5 / 5
Workflow Clarity	The 7-step Execution Flow has explicit validation (5-gate preflight with --strict), a real feedback loop (check BLOCKING line, loop to Step 4 with diagnostic, max 3 iterations, STOP on 3rd failure), and the Quality Gates table acts as a checklist — matching the top anchor; validation is present for the destructive/batch operations so no cap applies.	5 / 5
Progressive Disclosure	Clear overview pointing to 22 one-level-deep, well-signaled references (all verified present in ./references/), but the lengthy inline Untrusted-Data Contract section (~60 lines of security implementation detail) could itself be split into a reference file, leaving a minor organization gap rather than the clean top-anchor split.	4 / 5
	Total	17 / 20 Passed

Description

96%Weight 40%Scale 1-5

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

A strong, well-structured description that explicitly states both capabilities and natural-language trigger conditions with concrete examples. The only weak spot is slight overlap risk with general content/SEO writing skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities comprehensively — 'writing, rewriting, analysis, outlines, audits, schema, charts, images, repurposing, AI citation SEO, FLOW prompts, topic clusters, and multilingual publishing' — matching the comprehensive-coverage anchor; not a 4 because coverage spans the full blog lifecycle with no meaningful gaps.	5 / 5
Completeness	Clearly answers both 'what' (full-lifecycle blog engine routing to sub-skills) and 'when' ('Use when user says...') with concrete trigger phrases; matches the top anchor exactly, not a 4 where 'when' is only loosely specified.	5 / 5
Trigger Term Quality	Explicit natural trigger phrases users would actually say — 'blog', 'blog post', 'blog audit', 'topic cluster', 'multilingual blog', plus 'any /blog subcommand' — with synonyms (blog/blog post); matches the comprehensive-coverage anchor rather than a 4 which expects missing natural terms.	5 / 5
Distinctiveness Conflict Risk	A clear blog niche with specific triggers (blog audit, topic cluster, multilingual blog), but 'blog'/'blog post' could overlap with generic content-writing or SEO skills, so minor overlap risk keeps it just below the minimal-conflict anchor.	4 / 5
	Total	19 / 20 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: 2 missing	Warning

	Total	14 / 16 Passed

Repository: AgriciDaniel/claude-blog
Path: skills/blog/SKILL.md
Commit: 84f7abf

Reviewed: 4 days 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.