Blog Brief Planner
Build research-led blog briefs designed for Google visibility and AI citation readiness.
The skill requires web research, source URLs, and citation planning, providing some data-flow transparency. However, it does not define least-privilege behavior, sensitive-data boundaries, confirmation before external search or file saving, or recovery on external failures, so substantial points are deducted.
The workflow, inputs, and Markdown template are detailed, but abnormal-input handling is largely reduced to inference, while WebSearch access, reference paths, and template availability are not verified. No tests cover this skill's key paths, so the static score is capped below 10 and reduced further.
The description specifies trigger phrases, a topic argument, and audience, intent, and business-context inputs, making the target scenario clear. Non-fit boundaries, Chinese-language behavior, mainland-China reachability, and degradation without WebSearch are unspecified, so points are deducted.
The skill has a name, description, MIT metadata, argument hint, staged workflow, template catalog, and structured output contract. It lacks skill-specific versioning, changelog, maintenance ownership, installation/dependency notes, FAQs, and troubleshooting; its cross-reference paths may also be ambiguous.
The template covers keywords, competition, statistics, structure, citation capsules, linking, and distribution, so it plausibly supports useful briefs. However, many fields remain placeholders, completion depends on external search and omitted companion files, and no representative output evidence is supplied; only limited credit is justified.
The source contains a detailed workflow and auditable output fields, and repository-level CI and tests are supplied. The included tests do not cover blog-brief search, statistics, template loading, or saving behavior, and there is no independent reproduction evidence, so the score remains low.
- Before use, confirm WebSearch/WebFetch availability, network reachability, and source access; otherwise keyword, competitor, and statistics sections may be incomplete.
- Do not publish placeholders, estimated search volumes, or unverified statistics; validate each source, date, methodology, and value.
- The skill saves a brief into the project without specifying overwrite, path-confirmation, or rollback behavior; confirm the destination and existing files first.
- The cross-references depend on the full repository layout and may break when this skill is installed or distributed alone.
What does this skill do, and when should you use it?
Blog Brief is one skill within the claude-blog suite that turns a topic or keyword into an actionable blog content brief. It covers keyword research, search intent, competitive analysis, statistics planning, template selection, outlining, internal linking, citation capsules, and multi-channel distribution. It uses WebSearch for current search and competitor research and can read DISCOURSE.md from the project root to enrich competitive and information-gain analysis. It fits authors, marketing teams, and agencies that need structured planning, but it is not the suite’s complete writing or publishing pipeline.
Accepts a topic or keyword, target audience, search intent, and business context, inferring missing details when only a topic is supplied. It uses WebSearch to identify primary and secondary keywords, question queries, and search intent; analyzes leading ranking pages; and plans statistics, charts, images, titles, meta descriptions, TL;DR copy, information-gain opportunities, content sections, FAQs, citation capsules, competitive gaps, internal links, E-E-A-T signals, and Reddit, YouTube, LinkedIn, email, and X distribution. When present, it reads DISCOURSE.md for themes and citations, then saves the brief as briefs/[slug]-brief.md or to a user-specified location.
- A solo blogger has chosen a topic and needs a writing blueprint with keywords, structure, evidence, and visual suggestions.
- A marketing team is preparing an SEO article and needs competitor analysis, content gaps, and a statistics plan before drafting.
- An agency is creating repeatable client briefs and needs consistent templates, internal-link architecture, citation capsules, and distribution ideas.
- A content team wants to target both Google search and AI citation platforms and needs answer-first structure planned before writing.
What are this skill's strengths and limitations?
- Covers the main planning stages from keyword research through distribution planning.
- Includes selection logic for 12 content templates and plans titles, metadata, FAQs, statistics, and section structure.
- Explicitly plans AI citation capsules, answer-first passages, and information-gain opportunities.
- Can use DISCOURSE.md to incorporate recent themes, consensus, and contrarian takes into the brief.
- It depends on WebSearch and current search results, so research quality depends on available network access and sources.
- The workflow calls for analyzing ranking pages and finding 8-12 statistics, but the source does not provide fixed data sources, guaranteed search-volume figures, or precomputed results.
- The source provides no standalone test suite or standalone package for this individual skill.
- It plans content; it should not be treated as the suite’s complete article-writing, fact-checking, or publishing capability.
How do you install this skill?
This skill is bundled in AgriciDaniel/claude-blog; the source does not document a standalone installation for skills/blog-brief. The README-supported public installation is /plugin marketplace add AgriciDaniel/claude-blog, followed by /plugin install claude-blog@agricidaniel-claude-blog. Alternatively, clone the public repository, inspect the installer, and follow the repository instructions; restart Claude Code after installation.
How do you use this skill?
In Claude Code, run /blog brief <topic>, for example /blog brief content marketing for small businesses. The documented trigger phrases also include “content brief,” “blog brief,” “write brief,” “outline blog,” “plan blog post,” “blog outline,” and “content outline.” Supplying the audience, search intent, business context, and CTA improves the brief. The documented output path is briefs/[slug]-brief.md or a location the user specifies; the source does not document a separate standalone invocation mechanism or automatic creation of reference files.
How does this skill compare with similar options?
Compared with asking Claude or ChatGPT directly for an outline, Blog Brief supplies a defined workflow for research, competitor analysis, statistics, citation capsules, internal linking, and distribution planning. Compared with claude-blog’s full /blog write workflow, it focuses on pre-writing planning rather than complete article delivery.