Skip to content

AgriciDaniel/claude-blog / skills/blog

Full-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/pillar-page.md

View on GitHub
# Template: Pillar Page

**Description:** Comprehensive topic authority guide that serves as the central hub for a topic cluster. Pillar pages provide broad, thorough coverage of a subject and link out to supporting articles that dive deeper into sub-topics.

**Target Word Count:** 3,000-4,000 words

---

## When to Use This Template

- **Content Goal:** Establish topical authority and create an SEO hub that ranks for high-volume head terms
- **Search Intent:** Informational (users want a complete understanding of a topic)
- **Funnel Stage:** Top-of-funnel awareness and mid-funnel education
- **Use When:**
  - Targeting a broad, competitive keyword with high search volume
  - You have (or plan to create) 5+ supporting articles on sub-topics
  - The topic is complex enough to warrant 3,000+ words of coverage
  - You want to build a content cluster architecture around this topic

---

## Section-by-Section Structure

---

### Title

**Format:** "The Complete Guide to [Topic] in [Year]"

**Guidelines:**
- Include primary keyword naturally
- The year signals freshness and improves CTR
- Keep under 60 characters for full SERP display

```
# The Complete Guide to [Topic] in [Year]
```

[IMAGE] Hero image that visually represents the topic. Use a custom graphic or high-quality photo - not a generic stock image. Alt text should include the primary keyword.

---

### TL;DR Box (concise; length follows the material)

[ANSWER-FIRST] Provide a concise summary that directly answers the searcher's core question. A reader should be able to stop here and walk away informed. This box improves dwell time by immediately delivering value and earns featured snippet potential.

```
> **TL;DR:** [One to two sentences defining the topic and its importance.] [One sentence on the key takeaway or most surprising finding.] [One sentence on what action to take.] [STAT: key statistic that grounds the summary]
```

---

### Table of Contents

Auto-generated from H2 headings. Use anchor links for jump navigation. This improves UX on long-form content and can generate sitelinks in SERPs.

```
## Table of Contents

- [What Is [Topic]?](#what-is-topic)
- [Why [Topic] Matters](#why-topic-matters)
- [Core Section 1](#core-section-1)
- [Core Section 2](#core-section-2)
- [Core Section 3](#core-section-3)
- [Core Section 4](#core-section-4)
- [Core Section 5](#core-section-5)
- [Core Section 6](#core-section-6)
- [Advanced: [Expert-Level Sub-topic]](#advanced-expert-level-sub-topic)
- [Tools & Resources](#tools-resources)
- [Getting Started](#getting-started)
- [FAQ](#faq)
```

---

### Introduction (200-300 words)

[ANSWER-FIRST] Open with a clear, direct statement about what [Topic] is and why it matters right now. Do not bury the lead with backstory or fluff.

**Structure:**
1. **Opening hook** (1-2 sentences): Lead with a compelling statistic or trend that creates urgency
   - [STAT: current year statistic showing the scale or growth of this topic]
2. **Topic overview** (2-3 sentences): Define the topic clearly for someone encountering it for the first time
3. **Relevance statement** (1-2 sentences): Why this matters right now - what has changed recently?
4. **What the reader will learn** (2-3 sentences): Preview the guide's coverage - set expectations so the reader commits to reading
5. **Credibility indicator** (1 sentence): Why should the reader trust this guide? (experience, data sources, methodology)

[INFO-GAIN: personal experience] Include direct experience only when the author
supplies methodology, evidence, and results. Otherwise state the research basis
and source set without first-person framing.

[INTERNAL-LINK] If you have a related "Why [Topic] Matters" article, link it from the relevance statement.

---

### What Is [Topic]? (200-300 words)

[ANSWER-FIRST] Start with a one-sentence definition that could serve as a featured snippet. Keep it jargon-free for accessibility.

**Structure:**
1. **Clear definition** (1-2 sentences): Simple, authoritative definition of the topic
2. **Context and scope** (2-3 sentences): Where this fits in the broader landscape - what category does it belong to?
3. **Key components** (3-5 bullet points): Break the topic into its essential parts or characteristics
4. **Common misconceptions** (1-2 sentences): Address what this topic is NOT to prevent confusion
5. **Brief history or evolution** (2-3 sentences): How the topic has developed to its current state

[VISUAL: chart-type] Include a diagram or infographic showing the key components and how they relate to each other. Suggested: labeled diagram, flowchart, or concept map.

[STAT: definition-supporting data point] Include at least one data point that contextualizes the topic's scope or importance.

[INTERNAL-LINK] Link key terms to their own dedicated articles if they exist in the cluster.

---

### Why [Topic] Matters (200-300 words)

[ANSWER-FIRST] Lead with the single most compelling reason this topic deserves attention. Quantify the impact wherever possible.

**Structure:**
1. **Primary impact statement** (1-2 sentences): The most important reason backed by data
   - [STAT: impact or ROI statistic]
2. **Industry trends** (2-3 sentences): Market data showing growth, adoption, or shifting priorities
   - [STAT: trend or growth statistic]
3. **Consequences of ignoring** (2-3 sentences): What happens if you do not engage with this topic?
4. **Opportunity framing** (2-3 sentences): What is possible if you get this right?
5. **Who this affects** (1-2 sentences): Specific roles, industries, or use cases

[VISUAL: chart-type] Bar chart or line graph showing growth trend, adoption curve, or impact data over time.

[INFO-GAIN: unique analysis] Include a data point or trend observation that is not commonly cited - something from your own research or analysis.

[INTERNAL-LINK] Link to case studies or data-driven articles that expand on the impact claims.

---

### Core Sections (6-8 H2s, 300-400 words each)

Each core section covers a major sub-topic within the pillar. These sections should be comprehensive enough to stand alone but concise enough that a dedicated supporting article can go deeper.

**For each core section, use this structure:**

```
## [Sub-topic as H2 - written as a clear, keyword-rich heading]
```

[ANSWER-FIRST] Open with a 1-2 sentence answer or definition of this sub-topic before elaborating.

**Structure per section:**
1. **Direct answer or definition** (1-2 sentences): What is this sub-topic and why does it matter within the broader topic?
2. **Key principles or steps** (150-200 words): The essential knowledge, broken into:
   - Numbered steps (for processes)
   - Bullet points (for principles or characteristics)
   - Sub-headings H3 (for complex sub-topics)
3. **Example or evidence** (50-100 words): A specific, concrete example that illustrates the concept
   - [INFO-GAIN: real-world example] Use a first-hand example, case study, or original observation when possible
4. **Common mistakes or pitfalls** (50-75 words): What do people get wrong about this sub-topic?
5. **Transition to deeper content** (1-2 sentences): Bridge to the next section or to a supporting article

[STAT when useful: include a verified sub-topic-specific data point only when
it materially improves the section.]

[IMAGE] Where applicable, include screenshots, process diagrams, or example visuals that support the explanation.

[INTERNAL-LINK] Link to the dedicated supporting article for this sub-topic. Use contextual anchor text (not "click here" or "read more").

**Repeat this structure for each of the 6-8 core sections.**

---

### Advanced: [Expert-Level Sub-topic] (200-300 words)

[ANSWER-FIRST] Signal immediately that this section is for experienced practitioners, then deliver an advanced insight they will not find in beginner guides.

**Structure:**
1. **Audience gate** (1 sentence): "If you're already [doing X], here's how to [achieve Y]."
2. **Advanced insight** (100-150 words): A technique, framework, or perspective that goes beyond standard advice
3. **Evidence or application** (50-75 words): Where this has been applied successfully
4. **Caution or prerequisite** (25-50 words): What you need to have in place before attempting this

[INFO-GAIN: expert knowledge] Differentiate with supported original material
when it is genuinely available, such as documented direct experience,
proprietary data with methodology, or attributable expert interviews. A
research-only article may instead contribute distinctive synthesis, comparison,
or application without implying first-hand experience.

[INTERNAL-LINK] Link to advanced-level supporting articles or case studies.

---

### Tools & Resources (200-300 words)

[ANSWER-FIRST] Start by naming the top 1-2 recommended tools before listing the full set.

**Structure:**
- Organize tools into 2-3 categories (e.g., "Free Tools," "Premium Tools," "Learning Resources")
- For each tool, include:
  - **Tool name** (linked if appropriate)
  - **One-line description** of what it does
  - **Best for:** Who should use this tool
  - **Price:** Free, freemium, or pricing tier

[INFO-GAIN: personal experience] Note personal tool use only when the author
supplies the context, methodology, evidence, and results. Otherwise provide a
research-only comparison with attributed sources.

[INTERNAL-LINK] Link to any dedicated tool reviews or comparison articles in the cluster.

---

### Getting Started (150-200 words)

[ANSWER-FIRST] Give the reader their very first action step in the opening sentence. Remove all friction to starting.

**Structure:**
1. **Step 1** (2-3 sentences): The lowest-friction first action - what can someone do in the next 5 minutes?
2. **Step 2** (2-3 sentences): The next logical step that builds on Step 1
3. **Step 3** (2-3 sentences): A step that creates momentum and leads to ongoing engagement
4. **Encouragement** (1 sentence): Address the most common hesitation and counter it

[INTERNAL-LINK] Link each step to relevant supporting articles or tool guides that provide detailed walkthroughs.

---

### Optional Reader Questions (count by reader need)

[FAQ] If reader questions warrant this section, answer them directly. Use the
`<details>` pattern or H3 headings according to the platform and accessibility needs.

**Guidelines for FAQ questions:**
- Source questions from People Also Ask, forums, and comment sections
- Each answer should be complete and direct; no fixed word band
- The first sentence of each answer should be a standalone answer (featured snippet format)
- Include a verified statistic only when it materially improves an answer
- Cover a range: basic definitions, practical how-tos, comparisons, and cost/time questions

```
### [Question 1 - basic definition or "what is" question]?

[ANSWER-FIRST] [Direct 1-sentence answer.] [2-3 sentences of supporting detail.] [STAT: relevant statistic if applicable.]

### [Question 2 - "how to" or process question]?

[ANSWER-FIRST] [Direct 1-sentence answer.] [2-3 sentences of supporting detail.]

### [Question 3 - comparison or "vs" question]?

[ANSWER-FIRST] [Direct 1-sentence answer.] [2-3 sentences of supporting detail.]

### [Question 4 - cost, time, or effort question]?

[ANSWER-FIRST] [Direct 1-sentence answer.] [2-3 sentences of supporting detail.] [STAT: relevant statistic if applicable.]

### [Question 5 - common misconception or "is it worth" question]?

[ANSWER-FIRST] [Direct 1-sentence answer.] [2-3 sentences of supporting detail.]

### [Question 6 - advanced or edge-case question]?

[ANSWER-FIRST] [Direct 1-sentence answer.] [2-3 sentences of supporting detail.]

### [Question 7 - future-looking or trend question]?

[ANSWER-FIRST] [Direct 1-sentence answer.] [2-3 sentences of supporting detail.]
```

[INTERNAL-LINK] Link FAQ answers to relevant supporting articles where the reader can learn more.

---

### Conclusion with Internal Link Hub (150-200 words)

[ANSWER-FIRST] Restate the single most important takeaway from the guide in the opening sentence.

**Structure:**
1. **Key takeaway** (1-2 sentences): The single most important thing to remember
2. **Brief recap** (2-3 sentences): Summarize the guide's main points without repeating section headings verbatim
3. **Forward-looking statement** (1-2 sentences): How this topic is evolving and why staying current matters
4. **Call to action** (1 sentence): What should the reader do next?

**Internal Link Hub:**
List all supporting articles in the topic cluster, organized by category:

```
### Continue Learning

**Fundamentals:**
- [INTERNAL-LINK] [Supporting Article 1 Title]
- [INTERNAL-LINK] [Supporting Article 2 Title]

**How-To Guides:**
- [INTERNAL-LINK] [Supporting Article 3 Title]
- [INTERNAL-LINK] [Supporting Article 4 Title]

**Advanced:**
- [INTERNAL-LINK] [Supporting Article 5 Title]
- [INTERNAL-LINK] [Supporting Article 6 Title]

**Tools & Reviews:**
- [INTERNAL-LINK] [Supporting Article 7 Title]
- [INTERNAL-LINK] [Supporting Article 8 Title]
```

---

## Pre-Publish Checklist

- [ ] Length is sufficient for the reader task without padding; planning ranges are optional
- [ ] All [ANSWER-FIRST] prompts have been fulfilled - every section leads with the answer
- [ ] All [STAT] markers replaced with real, cited statistics (with source and year)
- [ ] All [VISUAL] markers replaced with actual charts or diagrams
- [ ] All [IMAGE] markers replaced with relevant, optimized images with alt text
- [ ] All [INFO-GAIN] markers replaced with original data, experience, or insight
- [ ] All [INTERNAL-LINK] zones populated with real links to supporting articles
- [ ] All [FAQ] answers are complete and lead with a direct answer
- [ ] Table of Contents links are functional
- [ ] Meta title clearly identifies the page and matches visible content
- [ ] Meta description accurately summarizes the visible page
- [ ] At least 6 supporting articles exist (or are planned) for the internal link hub
- [ ] Content has been reviewed for E-E-A-T signals (experience, expertise, authority, trust)
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall