git clone https://github.com/AgriciDaniel/claude-blog.git--- name: blog-brief description: > 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, citation capsule planning, information gain prompts, and multi-channel distribution plans. Briefs are optimized for Google rankings and AI citations (GEO/AEO). Use when user says "content brief", "blog brief", "write brief", "outline blog", "plan blog post", "blog outline", "content outline". user-invokable: true argument-hint: "<topic>" license: MIT --- # Blog Brief Generator: Content Planning Generates comprehensive content briefs that guide blog writing for maximum impact on both Google rankings and AI citation platforms. Reference documents: - `references/content-templates.md`: template selection criteria - `references/distribution-playbook.md`: channel-specific distribution tactics - `references/internal-linking.md`: link architecture patterns - `skills/blog/references/research-quality.md` - 5-dim quality rubric, pre-flight trap classes, freshness floors (v1.8.0; cross-skill ref lives in the orchestrator's references dir) - `skills/blog/references/synthesis-contract.md` - 6 LAWs for synthesis output (v1.8.0) ## Auto-loaded inputs (v1.8.0) When `DISCOURSE.md` is present at the project root (produced by `/blog discourse`), load it before starting brief generation. Use the discourse brief's "What's NEW" themes, "Consensus" themes, and "Contrarian takes" sections to enrich the competitive landscape and information-gain sections of this brief. Cite from DISCOURSE.md using the same inline `[name](url)` pattern. If DISCOURSE.md is absent, behavior is unchanged. ## Cross-reference For evidence-led keyword discovery, audience-avatar prompts, and content prioritization (directly upstream of brief generation), see `/blog flow find`. ## Workflow ### Step 1: Topic Intake Gather from the user: 1. **Topic or keyword** (required) 2. **Target audience** (who reads this?) 3. **Search intent**: Informational, commercial, transactional, navigational 4. **Business context**: What does the company do? What's the CTA? If only a topic is given, infer the rest from context. ### Step 2: Keyword Research Using WebSearch: 1. Search for the target keyword; analyze what currently ranks 2. Identify **primary keyword** (exact match target) 3. Identify **3-5 secondary keywords** (related terms, long-tail) 4. Identify **3-5 question queries** (People Also Ask style) 5. Note the **search intent**: what do searchers actually want? ### Step 2.5: Template Recommendation Analyze the topic, search intent, and competitive landscape to recommend one of 12 content templates. Load `references/content-templates.md` for selection criteria. **Available templates:** | Template | Best For | |----------|----------| | `how-to-guide` | Step-by-step instructional content | | `listicle` | Curated lists, ranked items, resource roundups | | `case-study` | In-depth analysis of a specific example or result | | `comparison` | Side-by-side evaluation of 2+ options | | `pillar-page` | Comprehensive topic hub linking to cluster content | | `product-review` | Detailed evaluation with pros/cons/verdict | | `thought-leadership` | Expert opinion, industry trends, predictions | | `roundup` | Expert quotes, tool collections, best-of lists | | `tutorial` | Technical walkthrough with code/config examples | | `news-analysis` | Timely coverage with expert commentary | | `data-research` | Original data, survey results, benchmark findings | | `faq-knowledge` | Question-driven reference content | **Selection process:** 1. Match search intent to template strength 2. Check what format top-ranking competitors use 3. Consider the user's available assets (data, expertise, tools) 4. Load the matching template file from `templates/[type].md` 5. Include the template name in the brief output ### Step 3: Competitive Analysis Analyze the top 3-5 ranking pages for the target keyword: 1. **Content length**: What's the average word count? 2. **Heading structure**: How many H2s? What topics do they cover? 3. **Visual elements**: Do competitors use charts, images, videos? 4. **Content gaps**: What do all competitors miss? 5. **Freshness**: How recently were they updated? 6. **Schema**: Do they use FAQ or other rich results? (Note: HowTo deprecated Sept 2023) 7. **Template pattern**: What content format do top results use? ### Step 4: Statistics Research Find 8-12 statistics the article should include: 1. Search: `[topic] study 2025 2026 data statistics research` 2. Prioritize tier 1-3 sources 3. For each stat, record: value, source, URL, date, methodology 4. Identify 2-4 stats suitable for chart visualization 5. Identify 1-2 stats suitable for TL;DR and social sharing ### Step 5: Generate the Brief Output format: ``` # Content Brief: [Title Suggestion] ## Template **Recommended**: [template-name]: [1-sentence rationale] **Template file**: `templates/[type].md` ## Target Keywords - **Primary**: [keyword]: [estimated monthly search volume if available] - **Secondary**: [keyword 1], [keyword 2], [keyword 3] - **Questions**: [question 1], [question 2], [question 3] ## Search Intent [Informational/Commercial/Transactional]: [1-2 sentence explanation of what the searcher wants] ## Content Parameters - **Word count**: [2,000-2,500] words - **Reading level**: Flesch 60-70 (expert-accessible) - **Format**: [Markdown/MDX/HTML] - **H2 sections**: [6-8] - **Images**: 3-5 from Pixabay/Unsplash - **Charts**: 2-4 via built-in blog-chart (diverse types) - **FAQ items**: 3-5 ## Recommended Title [Question-format title including primary keyword, under 60 chars] Alternative titles: 1. [Option 2] 2. [Option 3] ## Meta Description [150-160 chars, fact-dense, includes 1 statistic, ends with value proposition] ## TL;DR Draft > **TL;DR:** [40-60 word summary with key finding + 1 statistic + source. > Should be self-contained; a reader who only reads this box gets the > core value of the article.] ## Information Gain Opportunities - **[ORIGINAL DATA]**: [Suggestion for proprietary data, survey, experiment, or benchmark the author can produce to differentiate this post] - **[PERSONAL EXPERIENCE]**: [Suggestion for first-hand observation, test result, or case study to include: "When we tested X, we found Y"] - **[UNIQUE INSIGHT]**: [Suggestion for contrarian take, novel analysis, or non-obvious connection that competitors have not covered] ## Content Outline ### Introduction (100-150 words) - Hook: [Surprising statistic to open with] - Problem: [What challenge does the reader face?] - Promise: [What will they learn?] - TL;DR box placement (after hook, before first H2) ### H2: [Question Format] (300-400 words) - **Answer-first**: Open with [specific stat + source] - Cover: [subtopic 1], [subtopic 2] - **Image**: [Description of recommended image] - **Key stat**: [Specific statistic to include] ### H2: [Question Format] (300-400 words) - **Answer-first**: Open with [specific stat + source] - Cover: [subtopic 1], [subtopic 2] - **Chart**: [Type] showing [data description] - **Key stat**: [Specific statistic to include] [... repeat for 6-8 sections ...] ### FAQ Section (3-5 items) 1. [Question]: Answer with [stat + source] 2. [Question]: Answer with [stat + source] 3. [Question]: Answer with [stat + source] ### Conclusion (100-150 words) - Key takeaways (bulleted) - Call to action: [What should the reader do next?] ## Statistics to Include | # | Statistic | Source | Year | Section | |---|-----------|--------|------|---------| | 1 | [stat] | [source + URL] | 2025 | H2: Section 1 | | 2 | [stat] | [source + URL] | 2026 | H2: Section 2 | | ... | ... | ... | ... | ... | ## Citation Capsule Plan For each H2, plan a 40-60 word self-contained passage optimized for AI extraction. Each capsule should include a stat, its source, and a clear claim that can stand alone when quoted. | Section | Capsule Focus | Key Stat | Source | |---------|--------------|----------|--------| | H2: [Section 1] | [Core claim this section makes] | [stat] | [source] | | H2: [Section 2] | [Core claim this section makes] | [stat] | [source] | | H2: [Section 3] | [Core claim this section makes] | [stat] | [source] | | ... | ... | ... | ... | ## Cover Image | Option | Details | |--------|---------| | Photo cover | [Pixabay/Unsplash/Pexels search terms for wide hero image] | | Generated SVG | [Text-on-gradient concept with key stat, if data-heavy topic] | | Dimensions | 1200x630 (OG-compatible) | ## Visual Element Plan | # | Type | Data | Section | |---|------|------|---------| | 1 | [Bar chart] | [Data description] | H2: Section 2 | | 2 | [Donut chart] | [Data description] | H2: Section 4 | | 3 | [Image: Pixabay] | [Search terms] | H2: Section 1 | | 4 | [Image: Pixabay] | [Search terms] | H2: Section 3 | ## Competitive Gaps to Exploit 1. [What competitors miss that we should cover] 2. [Unique angle or original data we can provide] 3. [Format advantage: charts/visuals competitors lack] ## Internal Link Architecture - **Link TO** (from this new post to existing pages): 1. [Page title/URL] - anchor text: "[descriptive anchor]" 2. [Page title/URL] - anchor text: "[descriptive anchor]" 3. [Page title/URL] - anchor text: "[descriptive anchor]" 4. [Page title/URL] - anchor text: "[descriptive anchor]" 5. [Page title/URL] - anchor text: "[descriptive anchor]" - **Link FROM** (update these existing pages to link to this new post): 1. [Page title/URL] - anchor text: "[descriptive anchor]" 2. [Page title/URL] - anchor text: "[descriptive anchor]" 3. [Page title/URL] - anchor text: "[descriptive anchor]" 4. [Page title/URL] - anchor text: "[descriptive anchor]" 5. [Page title/URL] - anchor text: "[descriptive anchor]" - **Pillar connection**: [Which pillar page this belongs to, if applicable] - **Cluster position**: [Hub / Spoke / Standalone] ## E-E-A-T Signals to Include - **Experience**: [First-hand insight, case study, or test result] - **Expertise**: [Author credentials relevant to topic] - **Authority**: [Industry recognition, citations, partnerships] - **Trust**: [Transparency, sourced data, no self-promotion] ## Distribution Plan - **Reddit**: [Specific subreddits (r/sub1, r/sub2), posting approach (value-first comment vs. link post), authentic participation strategy, timing] - **YouTube**: [Video companion concept, estimated length, key visuals from the post to reuse, thumbnail idea] - **LinkedIn**: [Article excerpt angle, target audience segment, best posting time for the niche, engagement hook] - **Email**: [Newsletter excerpt (2-3 sentences), subject line suggestion, CTA linking back to the full post] - **Twitter/X**: [Thread hook (first tweet), 3-5 key tweet ideas built from statistics in the post, hashtag suggestions] ``` ### Step 6: Save the Brief Save to the user's project as `briefs/[slug]-brief.md` or to a location they specify. Confirm the brief is ready for `/blog write`.
[{"step":"Define your blog’s purpose and audience. Fill in [TOPIC] (e.g., 'sustainable packaging'), [AUDIENCE] (e.g., 'eco-conscious millennials'), [WORD_COUNT] (e.g., '1,000'), and [TONE] (e.g., 'conversational').","action":"Use tools like Google Trends or AnswerThePublic to validate your topic’s relevance. For example, search for 'sustainable packaging trends 2024' to confirm search volume."},{"step":"Customize the headline and key takeaways. Replace placeholder data with your own research or industry benchmarks. For instance, swap generic stats with niche-specific ones (e.g., '30% of Gen Z consumers prioritize brands with recyclable packaging').","action":"Use tools like Ahrefs or SEMrush to identify low-competition, high-volume keywords for your outline. For example, target 'biodegradable packaging alternatives' if it has 5,000 monthly searches."},{"step":"Refine the outline to match your content strategy. Add or remove sections based on your goals. For example, include a 'Common Mistakes to Avoid' section if your audience is beginners.","action":"Use tools like Notion or Trello to organize your brief. Drag and drop sections to prioritize them based on your audience’s pain points."},{"step":"Optimize for SEO and readability. Fill in the meta description and internal linking suggestions with your site’s existing content. For example, link to a blog post about 'cost-effective sustainability solutions.'","action":"Use Hemingway Editor or Grammarly to ensure your brief is clear and concise. Aim for a readability score of 7th-8th grade for broad appeal."},{"step":"Finalize and export. Save the brief as a PDF or Google Doc for your content team. Include a 'Next Steps' section with deadlines (e.g., 'Draft due by [DATE]').","action":"Use tools like Canva to create a visually appealing brief template if sharing with stakeholders. Add your company’s branding for consistency."}]
No install command available. Check the GitHub repository for manual installation instructions.
git clone https://github.com/AgriciDaniel/claude-blog/tree/main/skills/blog-briefCopy the install command above and run it in your terminal.
Launch Claude Code, Cursor, or your preferred AI coding agent.
Use the prompt template or examples below to test the skill.
Adapt the skill to your specific use case and workflow.
Create a detailed blog post brief for a [TOPIC] targeting [AUDIENCE]. Include a compelling headline, 3-5 key takeaways, a suggested outline with headings, and recommendations for SEO optimization (keywords, meta description, and internal linking opportunities). Assume a word count of [WORD_COUNT] and a tone of [TONE: e.g., professional, conversational, authoritative].
### **Blog Post Brief: The Rise of AI-Powered Customer Support in 2024** **Target Audience:** Mid-sized SaaS companies exploring automation tools for customer service. **Tone:** Professional yet approachable, with data-backed insights. **Word Count:** 1,200 words --- #### **Headline Options:** 1. "How AI-Powered Customer Support is Transforming SaaS Businesses in 2024" 2. "Why 78% of SaaS Companies Are Adopting AI Support Tools (And How to Get Started)" 3. "The Ultimate Guide to AI Customer Support: Benefits, Tools, and Best Practices" #### **Key Takeaways:** 1. **Cost Efficiency:** AI reduces support costs by up to 40% while improving response times by 60% (Gartner, 2023). 2. **Scalability:** AI chatbots handle 10,000+ concurrent queries without additional staffing. 3. **24/7 Availability:** 62% of customers prefer AI-driven support for instant resolutions outside business hours (Forrester). 4. **Personalization:** Modern AI tools use NLP to tailor responses based on user history, boosting satisfaction by 35%. 5. **Integration:** Top platforms like Zendesk and Intercom now offer native AI modules for seamless adoption. #### **Suggested Outline:** 1. **Introduction (150 words)** - Hook: "Support tickets are piling up, but your team can’t scale fast enough." - Brief overview of AI in customer support. - Thesis: AI isn’t replacing humans—it’s augmenting them. 2. **The State of AI in Customer Support (300 words)** - Current adoption rates (statistics from Gartner, McKinsey). - Common use cases: chatbots, ticket triage, sentiment analysis. - Case study: How Company X reduced response times from 24 hours to 2 minutes. 3. **Key Benefits of AI Support (400 words)** - Cost savings (with examples). - Improved customer satisfaction (NPS scores pre/post-AI). - Data-driven insights (how AI identifies pain points). 4. **Challenges and Misconceptions (200 words)** - Addressing fears: "Will AI replace my job?" (Spoiler: It augments, not replaces). - Overcoming implementation hurdles (training, integration). 5. **Tools and Platforms to Consider (250 words)** - Comparison table: Zendesk AI vs. Intercom Fin vs. Freshdesk. - Pricing tiers and best-fit scenarios. 6. **Implementation Roadmap (200 words)** - Step 1: Audit your current support workflow. - Step 2: Pilot an AI tool with a small team. - Step 3: Measure KPIs (first response time, resolution rate). 7. **Conclusion (100 words)** - Recap of AI’s role in modern support. - Call-to-action: "Ready to test AI support? Start with a free trial of [Tool Name]." #### **SEO Recommendations:** - **Primary Keywords:** "AI customer support," "SaaS support automation," "best AI tools for customer service." - **Secondary Keywords:** "chatbot for SaaS," "reduce support costs with AI." - **Meta Description:** "Discover how AI-powered customer support can slash costs by 40%, improve response times, and boost satisfaction—plus the top tools to get started in 2024." - **Internal Links:** Link to your existing guides on "SaaS onboarding best practices" and "customer retention strategies." #### **Visuals to Include:** - Infographic: "AI vs. Human Support: Efficiency Breakdown." - Screenshot: Dashboard of an AI tool in action. - Quote graphic: "AI isn’t about replacing humans—it’s about giving them superpowers." — [Industry Expert].
skills-collection
Take a free 3-minute scan and get personalized AI skill recommendations.
Take free scan