blog-brief

Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal linking architecture, template recommendations (12 types), TL;DR drafts, evidence-backed section planning, information gain prompts, and multi-channel distribution plans. Briefs are optimized for Google rankings and AI citation visibility as part of SEO. Use when user says "content brief", "blog brief", "write brief", "SEO brief", "article brief", or "content requirements".

Quality

91%

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

82%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.

The body is a detailed, actionable, well-sequenced workflow with a comprehensive output template and clearly signaled references. Its main weaknesses are mild verbosity in the inlined template and references that point outside the skill's own bundle rather than to local files.

Suggestions

Add an explicit validation/checkpoint step in the workflow (e.g. after Step 4, verify every statistic has provenance before generating the brief) to strengthen feedback loops.

Move the large inlined output template into a referenced file (e.g. references/brief-template.md) and keep only a concise structural summary in SKILL.md to tighten conciseness and improve progressive disclosure.

Clarify which referenced files live in this skill's bundle versus the orchestrator's references dir, or co-locate the referenced material so navigation stays one level deep within the skill.

Dimension	Reasoning	Score
Conciseness	The body is efficient and avoids explaining concepts Claude already knows, but the inlined output template and repeated detail across E-E-A-T / distribution sections are long enough that a few tokens could be trimmed without losing clarity.	4 / 5
Actionability	Provides concrete executable guidance throughout — specific WebSearch queries (e.g. '[topic] study 2025 2026 data statistics research'), exact numbered steps, and a copy-paste-ready brief template covering all common cases; absence of code is appropriate for this instruction-only skill.	5 / 5
Workflow Clarity	A clearly sequenced six-step workflow with validation sprinkled in ('Drop unverifiable statistics', 'validate source URLs before citing', safe WebFetch rule, mark unavailable surfaces), but it lacks an explicit validate→fix→retry feedback loop and concrete per-step checkpoints.	4 / 5
Progressive Disclosure	Good structure with a 'Reference documents' list and clearly signaled one-level-deep references, but the referenced paths (skills/blog/references/..., skills/blog/templates/...) point to cross-skill/orchestrator files not present in this skill's own bundle, a minor navigation gap.	4 / 5
	Total	17 / 20 Passed

Description

100%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.

The description is exemplary: it enumerates concrete capabilities, gives explicit natural-language trigger phrases, answers both what and when, and occupies a distinct niche with low conflict risk. No improvements needed.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal linking architecture, template recommendations (12 types), TL;DR drafts' — giving comprehensive coverage with no vague filler.	5 / 5
Completeness	Clearly answers both what ('Generate detailed content briefs for blog posts with...') and when (explicit 'Use when user says...' trigger clause with concrete phrases); uses third-person voice with no first/second-person penalty.	5 / 5
Trigger Term Quality	Explicit 'Use when user says "content brief", "blog brief", "write brief", "SEO brief", "article brief", or "content requirements"' provides comprehensive coverage of natural phrases and synonyms a user would actually say.	5 / 5
Distinctiveness Conflict Risk	Clear niche (SEO blog content briefs) with distinct, specific triggers ('content brief', 'SEO brief', 'blog brief') that are unlikely to collide with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: AgriciDaniel/claude-blog
Path: skills/blog-brief/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.