seo-content-brief

Generate competitive SEO content briefs with per-section word counts, competitor scoring, keyword density guidance, and page-type templates. Supports both new page briefs and improve-existing-page briefs. Use when user says "content brief", "write a brief", "content outline", "blog brief", "service page brief", "brief for", "writing brief", "content plan", or "outline for".

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/seo-content-brief/SKILL.md

Quality

Content

57%

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

A thorough, well-structured SEO brief skill with good progressive disclosure via real reference files and a fixed output template. It is held back by some concept re-explanation and a lack of explicit validation checkpoints in its workflow.

Suggestions

Trim general-knowledge exposition such as the search-intent definitions and 'Identify what is already strong' to respect Claude's competence and the token budget.

Add explicit validation/feedback checkpoints (e.g., after SERP analysis or before finalizing the outline, verify competitor scores and gap-priority calculations) to lift workflow clarity.

Replace abstract guidance like 'Score each real competitor: Depth (1-10)...' with a compact worked example or concrete scoring table so the instruction is copy-paste actionable.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but sections like the four search-intent definitions ("Informational: user wants to learn...") and generic guidance ("Identify what is already strong") restate concepts Claude already knows and could be trimmed.	2 / 3
Actionability	Provides concrete scoring rubrics, a fixed output template, and specific meta-tag character limits, but the body leans on rules and schemas rather than executable, copy-paste-ready instructions, leaving some gaps.	2 / 3
Workflow Clarity	The five-step process is clearly sequenced and an error-handling table covers failure modes, but there are no explicit validate-then-fix feedback checkpoints, which is below the top anchor.	2 / 3
Progressive Disclosure	The body points to three real, one-level-deep reference files (excluded-domains.md, page-type-templates.md, keyword-density.md), each clearly signaled and verifiable, keeping SKILL.md an effective overview.	3 / 3
	Total	9 / 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.

A strong, well-formed description that names concrete capabilities, provides a broad set of natural trigger phrases, and cleanly separates what-it-does from when-to-use. It uses third person and avoids vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — "per-section word counts, competitor scoring, keyword density guidance, and page-type templates" plus "new page briefs and improve-existing-page briefs" — matching the highest anchor.	3 / 3
Completeness	Explicitly answers both what the skill does and when to use it via a clear "Use when user says..." trigger clause.	3 / 3
Trigger Term Quality	Includes a rich set of natural phrases users would actually say ("content brief", "write a brief", "blog brief", "service page brief", "content plan", "outline for"), giving good coverage.	3 / 3
Distinctiveness Conflict Risk	The SEO content-brief niche is specific and the triggers ("content brief", "blog brief", "outline for") are unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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-seo
Path: skills/seo-content-brief/SKILL.md
Commit: 09d37c7

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.