AgriciDaniel/claude-blog / skills/blog
blog
VerifiedFull-lifecycle blog engine with 31 sub-skills, 12 templates, 100-point scoring, and 5 agents. Routes requests to the right sub-skill: writing, rewriting, analysis, outlines, audits, schema, charts, images, repurposing, AI citation SEO, FLOW prompts, topic clusters, and multilingual publishing. Optimized for Google rankings, E-E-A-T, and AI citations. Supports any platform. Use when the user asks to create, revise, analyze, plan, translate, localize, audit, or repurpose blog content, or invokes a /blog subcommand. Do not activate merely because the word "blog" appears in an unrelated coding, theme-debugging, database, log-analysis, or definition request.
templates/news-analysis.md
View on GitHub# Template: News Analysis (Timely Event Commentary)
**Template ID:** news-analysis
**Target Length:** 800-1,200 words
**Content Type:** Timely event analysis with actionable implications
**Primary Search Intent:** Informational / Navigational ("what happened," "what does X mean," "reaction to")
## When to Use This Template
Use this template when:
- A significant event, announcement, or release has just occurred
- The audience needs fast, opinionated analysis (not just a summary)
- You can publish within 2-4 hours of the event
- Search queries will include the event name + "what it means," "implications," "analysis"
- You have a clear perspective or expertise that adds value beyond the press release
Do NOT use this template for:
- Evergreen how-to content (use tutorial)
- Original research or data studies (use data-research)
- Reference/FAQ content (use faq-knowledge)
- Events more than 2 weeks old (the window for this format has passed)
**Speed Priority:** This template prioritizes speed of publication over depth. Get it out fast, then update if needed.
---
## Title Format
```
[Event/Announcement]: What It Means for [Audience]
```
**Examples:**
- "OpenAI's GPT-5 Release: What It Means for AI Developers"
- "Google's March 2026 Core Update: What It Means for Content Creators"
- "React 20 Announcement: What It Means for Frontend Teams"
**Title Rules:**
- Name the event explicitly (people search for event names)
- Specify the audience who should care
- Keep under 60 characters for full SERP display when possible
- Avoid clickbait - the event itself is the hook
**Alternative Title Formats:**
- "[N] Things [Audience] Should Know About [Event]"
- "[Event] Explained: [Impact Statement]"
- "Breaking Down [Event]: Implications for [Audience]"
---
## Section-by-Section Structure
---
### TL;DR Box (concise; length follows the material)
[ANSWER-FIRST] Distill the key implications into 2-3 sentences. Focus on what the reader should know and do, not on rehashing the event.
```markdown
> **TL;DR:** [Event name] [what happened in one clause]. The biggest implications for
> [audience] are [implication 1] and [implication 2]. [One-sentence recommendation
> or prediction]. [Action to take now].
```
**Rules:**
- Assume the reader already saw the headline - don't just restate the news
- Lead with implications, not with what happened
- Include one actionable recommendation
---
### What Happened (100-150 words)
[ANSWER-FIRST] State the facts of the event concisely. This is the objective section - save opinion for later.
```markdown
## What Happened
[ANSWER-FIRST] On [date], [organization/person] [announced/released/changed] [specific thing].
[1-2 sentences of factual detail].
**Key facts:**
- [Fact 1 with source attribution]
- [Fact 2 with source attribution]
- [Fact 3 with source attribution]
> "[Direct quote from announcement or key figure]" - [Attribution]
[STAT: one data point that establishes scale or significance - user count, market size, adoption rate]
```
**Rules:**
- Cite sources for every factual claim
- Include at least one direct quote from a primary source
- Keep this section objective - no analysis yet
- Include dates and specific version numbers
---
### Why This Matters (200-300 words)
[ANSWER-FIRST] Open with a clear statement of why this event is significant - not just what it is, but why the reader should care right now.
```markdown
## Why This Matters
[ANSWER-FIRST] [Event] matters because [core reason - be specific and opinionated].
[2-3 paragraphs of analysis covering:]
**Context:** How does this compare to previous events in this space? What pattern does it fit into or break?
[STAT: relevant market data, adoption metrics, or trend data that puts the event in context]
**Significance:** What makes this different from routine updates or announcements? What threshold does it cross?
[INFO-GAIN: your expert analysis or prediction - this is where you earn the reader's attention over generic coverage]
**Comparison:**
| Before [Event] | After [Event] |
|-----------------|---------------|
| [Previous state] | [New state] |
| [Previous state] | [New state] |
| [Previous state] | [New state] |
```
**Rules:**
- Be opinionated - "this matters because" not "this might matter"
- Compare to a previous event or baseline so readers understand scale
- Include at least one data point for context
- The [INFO-GAIN] here is your unique perspective - make it count
---
### What This Means for [Audience] (200-300 words)
[ANSWER-FIRST] Translate the event into specific implications for the target audience. Be concrete about what changes for them.
```markdown
## What This Means for [Audience]
[ANSWER-FIRST] For [audience], the immediate impact is [specific change]. Here's how this affects your work.
### Impact 1: [Specific Change]
[2-3 sentences explaining the implication with concrete examples]
### Impact 2: [Specific Change]
[2-3 sentences explaining the implication with concrete examples]
### Impact 3: [Specific Change]
[2-3 sentences explaining the implication with concrete examples]
[INFO-GAIN: prediction or non-obvious implication based on expertise - "What most coverage is missing is..."]
[INTERNAL-LINK: link to your existing content that helps readers understand the underlying concepts]
```
**Rules:**
- Use the actual audience name in the heading (e.g., "What This Means for Frontend Developers")
- Each impact should be a concrete change, not a vague observation
- Include at least one non-obvious implication (this is your differentiation)
- Link to your existing content where it provides deeper context
---
### What to Do Now (150-200 words)
[ANSWER-FIRST] Give the reader 3-5 concrete action steps, ordered by priority (most urgent first).
```markdown
## What to Do Now
[ANSWER-FIRST] Here are [N] steps to take in response to [event], ordered by urgency.
1. **[Immediate - today/this week]:** [Specific action with brief explanation]
2. **[Short-term - this month]:** [Specific action with brief explanation]
3. **[Medium-term - this quarter]:** [Specific action with brief explanation]
4. **[If applicable]:** [Specific action with brief explanation]
5. **[If applicable]:** [Specific action with brief explanation]
**Do NOT:**
- [Common overreaction to avoid]
- [Premature action to avoid]
[INTERNAL-LINK: link to tutorial or guide that helps with the recommended actions]
```
**Rules:**
- Order by urgency - what should they do today vs. this quarter?
- Be specific enough that the reader can act without further research
- Include "do NOT" items to prevent overreaction (shows credibility)
- Link to your own content that helps them take action
---
### The Bigger Picture (100-150 words)
[ANSWER-FIRST] Zoom out. Place this event in the context of broader industry trends.
```markdown
## The Bigger Picture
[ANSWER-FIRST] [Event] is part of a larger trend toward [broader pattern].
[1-2 paragraphs connecting this event to:]
- Industry direction or macro trends
- Previous events that form a pattern
- What this signals about the future
[INTERNAL-LINK: link to your strategy or trend-analysis content that covers the broader context]
[VISUAL: timeline showing this event in context of related events, if applicable]
```
**Rules:**
- This section is where you demonstrate strategic thinking
- Connect to 1-2 broader trends maximum - don't overextend
- End with a forward-looking statement (prediction or question to watch)
---
### Optional Reader Questions (count by reader need)
[ANSWER-FIRST] for each question. Optimize for the exact queries people will search in the hours/days after the event.
```markdown
## Frequently Asked Questions
### [Question 1 - the most obvious question about the event]?
[ANSWER-FIRST] [Direct answer in 1-2 sentences]. [Brief supporting detail].
### [Question 2 - practical question about what to do]?
[ANSWER-FIRST] [Direct answer in 1-2 sentences]. [Brief supporting detail].
[INTERNAL-LINK: link to detailed how-to content if relevant]
### [Question 3 - forward-looking question about what happens next]?
[ANSWER-FIRST] [Direct answer in 1-2 sentences]. [Brief supporting detail].
[STAT: data point that supports the answer]
```
**FAQ Rules:**
- Use questions people are actually searching for right now
- Answers must be self-contained and extractable for search snippets and AI citations
- Keep answers concise and complete; Google has no required answer length
- Include only questions that add useful material; count follows reader need
---
### References and Retrieval Notes
```markdown
## References and Retrieval Notes
- [Source 1 title]([URL]) - [Organization], [Date], retrieved YYYY-MM-DD
- [Source 2 title]([URL]) - [Organization], [Date], retrieved YYYY-MM-DD
- [Source 3 title]([URL]) - [Organization], [Date], retrieved YYYY-MM-DD
- [Source 4 title]([URL]) - [Organization], [Date], retrieved YYYY-MM-DD
```
**Rules:**
- Every factual claim in the article must have an inline citation
- Retrieval notes provide provenance and must not duplicate inline citations as a raw source dump
- Use primary sources (official announcements, press releases) over secondary coverage
- Include the date of each source
- Aim for 4-8 sources minimum
---
## Content Checklist
Before publishing, verify:
- [ ] Published within 2-4 hours of the event
- [ ] Title names the event explicitly and specifies the audience
- [ ] TL;DR focuses on implications, not just restating the news
- [ ] "What Happened" section is purely factual with source citations
- [ ] At least one direct quote from a primary source
- [ ] Statistics appear only when material to the analysis and are verified
- [ ] At least 2 [INFO-GAIN] sections with original analysis or predictions
- [ ] "What to Do Now" has 3-5 concrete, prioritized action steps
- [ ] At least 3 [INTERNAL-LINK] zones connecting to existing content
- [ ] FAQ questions match actual search queries about the event
- [ ] All sources listed with URLs and dates
- [ ] Analysis is opinionated and differentiated from generic coverage
- [ ] "Do NOT" section included to prevent overreaction
- [ ] Content is under 1,200 words (resist the urge to over-explain)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |