Blog Strategy Architect
Plans blog positioning, topic clusters, audience focus, search growth, and AI-citation opportunities.
The skill explicitly calls for competitor research, WebSearch, cross-platform monitoring, and external distribution through Reddit, review sites, and Wikipedia/Wikidata, but it does not define user confirmation, data flows, sensitive-data handling, external-publication boundaries, or rollback. Repository security material documents some broader controls, but they are not a complete guarantee provided by this skill itself; 12 is warranted.
The workflow, discovery questions, cluster structures, and output template are fairly coherent, and repository CI and related tests provide some supporting evidence. However, the selected skill has no dedicated tests, executed examples, or abnormal-input/failure behavior for its core strategy path, and its referenced files were not independently verified here. Static calibration therefore supports only 8.
Frontmatter provides user invocation, trigger phrases, and a <niche> argument, with clear use cases covering positioning, topics, pillars, and strategy planning. It lacks explicit non-fit boundaries, minimum inputs, negative trigger conditions, Chinese-language workflow guidance, and mainland-China reachability analysis; several recommendations depend on external AI/search platforms. Score: 10.
The document uses progressive workflow steps and includes discovery questions, reusable tables, an output format, cross-references, MIT licensing, and version markers. It lacks standalone installation/dependency notes, FAQs, troubleshooting, explicit maintenance ownership, and an update path. It also references v1.8.0 while repository metadata reports v1.9.1, creating version-coherence uncertainty. Score: 9.
The skill supplies directly reusable templates for competitive analysis, audience mapping, hub-and-spoke clusters, distribution, measurement, and a 90-day roadmap, so it plausibly completes the central strategy task. Nevertheless, results depend on user business context and first-hand data; many platform-impact and citation statistics lack verifiable sourcing in the skill, and the recommended scope may require substantial manual review. Static calibration supports 6.
The README, CI, and tests show broader engineering validation, preflight checks, and content-analysis tests, but they do not cover blog-strategy semantic triggering, strategy-output completeness, reproducible competitive research, or the stated GEO figures. Evidence is auditable but limited and lacks third-party execution proof. Score: 4.
- Key figures such as 80%, 88-92%, 450%, 0.737 correlation, and 2.6-3.5x are presented without source links, dates, or a verification method in the skill; they should not be treated as established facts or baseline targets.
- WebSearch and cross-platform monitoring introduce external content into the model context; confirm access scope before use and treat fetched material as data, not instructions.
- Repository metadata reports v1.9.1 while the selected skill still labels its research-discipline references v1.8.0; verify reference paths, content, and version coherence before release.
- Recommendations rely on Reddit, YouTube, G2/Capterra, Wikipedia/Wikidata, and several overseas AI platforms; mainland-China users should validate reachability, account availability, and compliance first.
What does this skill do, and when should you use it?
Blog Strategy is the blog-strategy skill within the claude-blog repository, focused on positioning and content architecture rather than the entire blog-production pipeline. It combines audience mapping, competitor research, and hub-and-spoke topic planning for Google visibility and citations across ChatGPT, Perplexity, and AI Overviews. It also defines differentiation, distribution, quality targets, GEO tactics, and measurement. It is best suited to people planning a blog program, not those seeking only a single generated article.
It gathers business context, blog goals, existing content, competitors, differentiators, and available resources; researches competitor blogs for publishing frequency, content types, visual quality, schema usage, social distribution, and AI citation presence; defines two to three audience segments; designs three to five content pillars with hub-and-spoke clusters, keywords, templates, and internal-linking plans; maps differentiation through original data, case studies, interviews, reviews, and industry analysis; plans on-site AI citability, off-site distribution, and platform-specific GEO tactics; sets content-quality, E-E-A-T, visual, internal-link, and schema targets; and produces a strategy document with a roadmap, metrics, and next steps.
- A solo blogger entering a new niche needs audience definitions, content pillars, and an initial topic backlog.
- A marketing team with an established blog needs competitor-gap analysis and potential AI-citation targets.
- An agency needs repeatable hub-and-spoke plans with consistent templates, internal linking, and quality requirements.
- A brand wants one editorial strategy covering both Google search visibility and citations in ChatGPT, Perplexity, and AI Overviews.
- A content lead needs a 90-day roadmap connecting publishing, off-site distribution, SEO metrics, and AI-citation tracking.
What are this skill's strengths and limitations?
- Covers the full planning path from audience and competitor research through clusters, distribution, and measurement.
- Explicitly addresses both Google rankings and AI-citation surfaces.
- Provides concrete hub-and-spoke structures, keywords, content templates, and internal-linking guidance.
- Turns editorial quality into measurable targets covering E-E-A-T, visuals, links, and structured data.
- MIT-licensed and available through the public repository.
- It plans the strategy; it is not by itself the repository's complete writing, publishing, or review pipeline.
- Competitor and AI-citation research depends on WebSearch and can vary with query coverage and changing platforms.
- The requested architecture of three to five pillars and eight to twelve spokes per pillar can require substantial research and production capacity.
- The source does not provide independent tests or a standalone installer for this individual skill.
- Several numerical platform and citation claims are included as strategic inputs without specific supporting studies in the supplied skill text.
How do you install this skill?
This is not presented as a standalone package; it is located at skills/blog-strategy/SKILL.md inside the claude-blog collection. The README supports installing the public repository with /plugin marketplace add AgriciDaniel/claude-blog, followed by /plugin install claude-blog@agricidaniel-claude-blog; it also documents a clone-and-run installer flow. No separate installation command for blog-strategy alone is documented.
How do you use this skill?
After installing claude-blog in Claude Code, run /blog strategy <niche>, for example /blog strategy B2B project management software. The workflow covers discovery, competitor research, audience mapping, topic-cluster design, AI-citation strategy, distribution, and measurement. If DISCOURSE.md exists at the project root from /blog discourse, the skill says to load it as a cross-platform discourse signal.
How does this skill compare with similar options?
The README compares the broader claude-blog suite with direct prompting, Copy.ai/Jasper, and building a workflow yourself. Those comparisons do not specifically evaluate blog-strategy alone. For adoption purposes, this skill is best understood as a structured editorial-strategy planner, not a complete content-production platform.