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.

references/distribution-playbook.md

View on GitHub
# Content Distribution Strategy: Playbook for AI Visibility

Distribution helps content reach people on the channels they use. Vendor
datasets also observe off-site sources in AI answers, but those observations are
non-causal and do not establish a universal citation share or budget formula.
Allocate effort according to audience relevance, evidence, and measured
business outcomes.

## Contents

- [Reddit](#reddit)
- [YouTube](#youtube)
- [LinkedIn](#linkedin)
- [Twitter / X](#twitter--x)
- [Email Newsletter](#email-newsletter)
- [Review Platforms (B2B)](#review-platforms-b2b)
- [Wikipedia and Wikidata](#wikipedia-and-wikidata)
- [Distribution Timeline](#distribution-timeline)
- [Measurement Framework](#measurement-framework)

---

## Reddit

**Platform change (June 2023):** Reddit restricted high-volume and commercial API
access. Limited compliant API use may still be available, but content strategy
should rely on organic participation, not programmatic posting, scraping, or
automation.

### Why Reddit Matters for AI
- Community discussions can reveal language, questions, and practitioner
  context that first-party pages miss.
- Visibility observations vary by query, product, and date. Do not infer a
  ranking or citation benefit from participation.

### Subreddit Research Methodology

1. **Find active communities** (target 5-10 subreddits in your niche):
   - Search Reddit directly: `site:reddit.com [your niche] subreddit`
   - Check subreddit sidebar for rules, posting guidelines, and related subs
   - Use Reddit search, subreddit sidebars, mod posts, and native community stats
     for activity signals
   - Look for subs with 10K-500K members (sweet spot for engagement vs noise)

2. **Evaluate each subreddit before participating**:

   | Check | What to Look For |
   |-------|-----------------|
   | Self-promotion rules | Most subs require max 10% self-promotional content |
   | Post types allowed | Some ban links entirely; others require text posts |
   | Active moderators | Dead subs provide no value |
   | Comment quality | High-quality discussions better serve the community |
   | Flair requirements | Some subs require specific post flair |

3. **Observe before posting**: Spend 1-2 weeks reading and commenting
   before submitting any content. Understand what gets upvoted, what gets
   removed, and the community's tone.

### Reddit Content Strategy

**Self-promotion rules**: Maximum 10% of your activity should be your own
content. For every 1 promotional post, you need 9 genuine contributions
(comments, answers, discussions).

**Format that works on Reddit**:
- Lead with an insight or question, not a link
- Share specific data points and findings in the post body
- Provide standalone value: the post should be useful without clicking any link
- Place your blog link in context within the post, not as the sole purpose
- Use formatting: bold for key stats, bullet points for lists, TL;DR at top

**Example post structure**:
```
Title: [Specific finding] - [context/data point]

TL;DR: [concise standalone summary with verified support where needed]

[Paragraph 1: The insight or finding with data]

[Paragraph 2: Why this matters / what it means]

[Paragraph 3: What you can do about it]

I wrote a more detailed breakdown here: [link]: but the key takeaways
are all above.

[Paragraph 4: Ask a question to drive discussion]
```

### Thread Mining for Long-Tail Keywords

Reddit threads surface in Google's "Discussions and Forums" SERP feature.
Mine existing threads for content ideas:

1. Search: `site:reddit.com [your topic] "how do" OR "what is" OR "best way"`
2. Find recurring questions with no authoritative answer
3. Write blog posts that answer these questions with data
4. Answer the Reddit thread with a genuine, helpful response (link optional)

This can create a useful cross-reference when the Reddit comment genuinely
helps the community and the blog post provides deeper verified support. Do not
promise ranking, authority, or citation outcomes.

---

## YouTube

### When YouTube Helps
Use video when a relevant demonstration, walkthrough, or expert explanation
adds material value for the audience. Vendor observations about video mentions
and measured visibility are non-causal, time-bound context, not a ranking,
readiness, or citation bonus.

### Companion Video Structure

When the same material suits both formats, video chapters may mirror the blog's
topic sequence so people can navigate consistently. Do not manufacture a
companion video or claim machine-recognized authority.

| Blog Section | Video Chapter | Notes |
|-------------|---------------|-------|
| Introduction | 0:00 Hook + overview | Match blog's opening stat |
| H2 Section 1 | Chapter 1 | Same data points, visual explanation |
| H2 Section 2 | Chapter 2 | Show charts/data on screen |
| H2 Section 3 | Chapter 3 | Demo or walkthrough if applicable |
| FAQ | Q&A Chapter | Answer the same FAQ questions |
| Conclusion | Summary + CTA | Link to blog in description |

### Title Optimization
- Match the blog title format closely (builds topical association)
- Include the target keyword within the first 60 characters
- Keep total length under 70 characters
- Use numbers when possible: "5 Ways...", "2026 Data Shows..."
- Front-load the value: "[Key Finding]: How to [Achieve Outcome]"

### Transcript SEO
YouTube auto-captions can contain errors. Upload your own transcript for
accuracy:

1. Export transcript from your blog post (strip formatting)
2. Add timestamps matching video chapters
3. Upload via YouTube Studio > Subtitles > Add Language > Upload File
4. Verify accuracy and keyword presence

**Why transcripts matter**: accurate transcripts help YouTube and retrieval
systems understand the video, improve accessibility, and make quotations easier
to extract. Do not claim transcript keywords are a direct ranking signal unless
a current primary source is loaded.

### Thumbnail Best Practices

| Element | Guideline |
|---------|-----------|
| Colors | Contrasting colors (complementary palette), avoid YouTube red |
| Text | Maximum 4 words, large readable font (even on mobile) |
| Face | Close-up with expressive emotion (test against your own channel data) |
| Consistency | Use brand template for recognizable channel identity |
| Resolution | 1280x720 minimum, 16:9 aspect ratio |
| File size | Under 2MB (YouTube compresses further) |

### YouTube Description Template
```
[First 2 lines appear before "Show more": use them wisely]

[Key stat from blog]: in this video, I break down [topic].

Chapters:
0:00 Introduction
1:30 [Chapter 1 title]
4:00 [Chapter 2 title]
...

Read the full blog post: [URL]

Resources mentioned:
- [Resource 1]: [URL]
- [Resource 2]: [URL]

#keyword1 #keyword2 #keyword3
```

### Video Performance Observations

| Metric | How to Use It |
|--------|---------------|
| Length | Match the time needed to teach or demonstrate the topic |
| Retention | Diagnose where the intended audience stops finding value |
| CTR | Review whether the title and thumbnail accurately set expectations |
| Upload frequency | Choose a sustainable cadence; no authority quota applies |

### YouTube Shorts Note

Treat YouTube Shorts as a separate discovery surface with its own metrics unless
current channel analytics prove it is driving long-form viewers or blog clicks.
Use Shorts for top-of-funnel awareness, but do not assume it will boost
long-form authority.

---

## LinkedIn

LinkedIn distribution favors native content in many creator reports. Without a
current primary LinkedIn engineering source, do not cite named internal algorithm
systems or exact reach penalties. Practical guidance: publish native text,
documents, and video, then place external links in a comment or follow-up when
that fits the audience.

### Content Adaptation
Adapt blog posts for LinkedIn as shorter articles (800-1,200 words).
LinkedIn audiences prefer opinion-led, personal, and industry-relevant content
over keyword-optimized SEO content.

### Format Guidelines

| Element | LinkedIn Optimization |
|---------|----------------------|
| Length | 800-1,200 words (shorter than blog) |
| Tone | Personal, opinion-led, first-person |
| Paragraphs | 1-2 sentences each (very short) |
| Emphasis | **Bold text** for key phrases and stats |
| Lists | Bullet points for scannable takeaways |
| Closing | Ask a question to drive comments |
| Links | Put external links in the FIRST COMMENT, not the body |

### Why First Comment for Links
Some practitioners report lower reach for posts with external links in the
body. Observational studies disagree: some find a reach penalty, others find
little or none, and LinkedIn has not confirmed a link penalty (for example
Ordinal's analysis, https://www.tryordinal.com/blog/linkedin-link-penalty-study,
seen in search 2026-10-11, not fully verified). As a low-cost hedge, place
your blog link as the first comment immediately after publishing.

### Thought Leadership Positioning

| Content Type | Purpose | Frequency |
|-------------|---------|-----------|
| Contrarian takes | Challenge industry assumptions with data | 1-2/month |
| Industry analysis | Break down trends and what they mean | 2-4/month |
| Lessons learned | Share failures and successes transparently | 1-2/month |
| Data snapshots | Share one compelling stat with analysis | Weekly |
| Frameworks | Original models or processes | Monthly |

### Posting Schedule
- **Best times**: 7-8 AM or 12 PM (local timezone of your audience)
- **Critical window**: Engage with every comment within the first hour
- LinkedIn's algorithm evaluates engagement velocity in the first 60 minutes
- Reply to comments with substantive responses, not just "thanks"

### LinkedIn Post Template
```
[Hook line with surprising stat or contrarian statement]

[1-2 sentence context or personal connection]

Here's what the data shows:

- [Key finding 1 with stat]
- [Key finding 2 with stat]
- [Key finding 3 with stat]

[2-3 sentences of analysis: your unique take]

[What this means for the reader: actionable insight]

[Question to drive engagement]

---
[Hashtags: #topic1 #topic2: max 3-5]
```

---

## Twitter / X

### Thread Format
Convert blog posts into Twitter threads (7-9 tweets) for maximum reach:

**Thread structure**:
1. **Hook tweet**: Most surprising finding + promise of value
2-7. **Insight tweets**: One key insight per tweet with standalone value
8. **Summary tweet**: Key takeaway recap
9. **CTA tweet**: Link to full blog post + retweet request

### Tweet Optimization

| Guideline | Rule |
|-----------|------|
| Hook tweet | Must stop the scroll: use a surprising stat or counterintuitive claim |
| Insight tweets | Each must deliver value independently |
| Stats per tweet | Include one specific data point |
| Length | 200-280 characters per tweet (not maximum, but substantive) |
| Hashtags | Maximum 2 per tweet, use niche hashtags over broad ones |
| Media | Add an image or chart to 2-3 tweets in the thread |
| CTA | Clear and specific: "Read the full breakdown" not "check it out" |

### Thread Template
```
Tweet 1 (Hook):
[Surprising stat]. [What it means in one sentence].

Here's what the data reveals (and what to do about it):

๐Ÿงต๐Ÿ‘‡

Tweet 2-7 (Insights):
[Number]. [Finding]

[Supporting stat] ([Source]).

[Why it matters in 1-2 sentences].

Tweet 8 (Summary):
Key takeaways:

1. [Finding 1]
2. [Finding 2]
3. [Finding 3]

Tweet 9 (CTA):
Full breakdown with all the data and charts:

[Blog URL]

If this was useful, retweet the first tweet so others can find it.
```

### Hashtag Strategy
- Use niche hashtags that your target audience follows (e.g., `#SEOdata`, `#AISearch`)
- Avoid broad hashtags that get lost (e.g., `#marketing`, `#AI`)
- Research active hashtags: search the hashtag, check tweet frequency and quality
- Maximum 2 hashtags per tweet to avoid looking spammy

---

## Email Newsletter

### Timing
Send when the audience expects the newsletter and the material is ready. Do not
claim that delivery timing creates search or AI-citation benefits.

### Subject Line Formulas

| Formula | Example |
|---------|---------|
| `[Verified Stat]: [Supported Finding]` | `[VERIFIED RESULT]: [READER-RELEVANT FINDING]` |
| `How [Method] Affected [Measured Outcome]` | Use only with supplied methodology, evidence, and results |
| `[Number] [Things] for [Reader Task]` | Use only when the item count follows the real material |
| `[Clear Finding] About [Topic]` | State the supported finding without clickbait |
| `We Analyzed [N] [Things]: [Specific Finding]` | Use only when the real sample, method, limitations, and results are supplied |

### Excerpt Structure (sized to the message)

```
**TL;DR**: [concise summary of the blog post's core finding]

3 key takeaways from this week's analysis:

1. **[Finding 1]**: [Stat] ([Source]). [One sentence implication.]

2. **[Finding 2]**: [Stat] ([Source]). [One sentence implication.]

3. **[Finding 3]**: [Stat] ([Source]). [One sentence implication.]

[Read the full analysis with charts and data โ†’](blog-url)

---

*What are you seeing in your own data? Reply to this email. I read every response.*
```

### Email Performance Benchmarks

| Metric | Good | Excellent |
|--------|------|-----------|
| Open rate | 25-30% | 35%+ |
| Click rate | 3-5% | 7%+ |
| Unsubscribe rate | < 0.5% | < 0.2% |
| Reply rate | 1-2% | 3%+ |

---

## Review Platforms (B2B)

### Why Review Platforms Matter
Review platforms can help buyers compare products and expose recurring
questions or objections. Vendor citation-share studies conflict across samples,
so treat them as non-causal context rather than a multiplier.

### Platform Priority (B2B)

| Platform | Audience Fit | Priority Rule |
|----------|--------------|---------------|
| G2 | B2B software buyers | Use when the category and customers are active there |
| Capterra | Software comparison | Use when it supports the buyer journey |
| TrustRadius | Detailed B2B reviews | Use when depth and category coverage fit |
| Gartner Peer Insights | Enterprise software | Use for relevant enterprise categories |
| Trustpilot | Broad consumer reviews | Use when the audience researches there |

### Profile Optimization Checklist

| Element | Action |
|---------|--------|
| Company description | Keyword-rich, 250-500 words, mirrors website positioning |
| Product categories | Select all relevant categories (increases discoverability) |
| Screenshots | 5-10 product screenshots with descriptive captions |
| Logo | High-resolution, matches website branding |
| Pricing info | Keep current (outdated pricing hurts trust) |
| Integration list | Link all integrations/partnerships |
| Comparison pages | Claim and optimize vs-competitor pages |

### Review Generation Strategy
- Ask customers at high-satisfaction moments (post-onboarding, after milestone)
- Make the process frictionless: provide direct links to review forms
- Respond to reviews when a useful, accurate reply is warranted
- Handle negative reviews transparently and without suppressing criticism
- Track rating and review coverage in context; no universal score or volume
  threshold creates trust, ranking, or citation benefits

---

## Wikipedia and Wikidata

### Optional Entity and Reference Context
Wikipedia and Wikidata can be useful public reference projects when an entity
independently satisfies their policies. Do not create or edit entries as an AI
citation, ranking, credibility, or Knowledge Graph tactic.

### Strategy
Wikipedia requires notability established through independent, reliable
sources. You cannot create a Wikipedia page for self-promotion.

**Policy-compliant pathway**:
1. Confirm independent notability using reliable, substantive sources
2. Disclose conflicts of interest and follow the project's contribution rules
3. Create or request a Wikidata item only if the entity meets Wikidata notability
   policy; disclose conflicts of interest and avoid promotional edits
4. If notable, an independent editor may create a Wikipedia article
5. For a connected subject, prefer talk-page or requested-edit processes and
   follow current conflict-of-interest guidance

### Wikidata Entry
```
Entity: [Organization Name]
Instance of: Q4830453 (business enterprise) or Q7397 (software)
Official website: [URL]
Founded: [Date]
Industry: [Q-ID for your industry]
```

---

## Distribution Timeline

### Day 0 (Publication Day)

| Time | Action | Channel |
|------|--------|---------|
| 9:00 AM | Publish blog post | Website |
| 9:15 AM | Send email newsletter | Email |
| 9:30 AM | Post LinkedIn text (link in comment) | LinkedIn |
| 10:00 AM | Post Twitter/X thread | Twitter/X |
| 12:00 PM | Share in relevant subreddits (if genuine value) | Reddit |

### Week 1

| Day | Action | Channel |
|-----|--------|---------|
| Day 1-2 | Engage with all comments on LinkedIn/Twitter | Social |
| Day 2-3 | Publish companion YouTube video | YouTube |
| Day 3-5 | Answer related Reddit threads with insights | Reddit |
| Day 5-7 | Repurpose as short-form content (carousel, clip) | Social |

### Month 1

| Week | Action | Purpose |
|------|--------|---------|
| Week 2 | Pitch to industry newsletters | Earned media |
| Week 3 | Participate in relevant Reddit discussions when helpful | Community building |
| Week 4 | Update the blog post only if facts or evidence changed | Accuracy |

### Quarterly

| Action | Purpose |
|--------|---------|
| Refresh blog post when statistics materially change | Accuracy and reader trust |
| Record updated YouTube video if the changed data affects its usefulness | Cross-platform accuracy |
| Audit review platform profiles | Ensure accuracy |
| Review AI citation metrics | Adjust strategy |

---

## Measurement Framework

### Metrics by Channel

| Channel | Primary Metric | Secondary Metrics |
|---------|---------------|-------------------|
| Reddit | Thread engagement (upvotes + comments) | Referral traffic, keyword rankings for thread URLs |
| YouTube | Watch time for the intended audience | Subscriber growth, referral traffic, useful feedback |
| LinkedIn | Engagement rate (reactions + comments / impressions) | Profile views, connection requests, referral traffic |
| Twitter/X | Thread impressions and retweets | Profile clicks, link clicks |
| Email | Click-through rate | Open rate, reply rate, unsubscribe rate |
| Review platforms | Rating and review count | Profile views and qualified referrals |

### AI Citation Tracking

Track AI citations manually (no automated tool covers all platforms yet):

1. **ChatGPT**: Search your brand and key topics weekly. Record mentions.
2. **Google AI Overviews**: Check Google Search Console for AI Overview impressions.
3. **Perplexity**: Search your topics monthly. Record source citations.
4. **Claude**: Search your topics monthly. Note when your content is referenced.

### GA4 AI Referral Traffic Segments

Create custom segments to track AI-referred visitors:

| Source | GA4 Filter |
|--------|-----------|
| ChatGPT | source contains "chatgpt" OR "chat.openai" |
| Perplexity | source contains "perplexity" |
| Claude | source contains "claude" OR "anthropic" |
| Google Search AI | Use Search Console generative-AI reports for Search AI visibility; GA4 cannot reliably isolate AI Overview traffic |
| Bing Copilot | source contains "bing" AND referrer contains "copilot" |

Historical Similarweb reporting from January to May 2025 showed rapid AI referral
growth from a small base. Do not cite a fixed total-web share for July 2026
without refreshing the source. Track the trend monthly.
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