Skip to content

feat(content): add distribution channel reference agents (t199.8)#880

Merged
marcusquinn merged 1 commit intomainfrom
feature/t199.8
Feb 10, 2026
Merged

feat(content): add distribution channel reference agents (t199.8)#880
marcusquinn merged 1 commit intomainfrom
feature/t199.8

Conversation

@marcusquinn
Copy link
Owner

@marcusquinn marcusquinn commented Feb 10, 2026

Summary

  • Create content/distribution/ directory with 6 distribution channel agents completing the content pipeline's multi-channel fan-out
  • All agents referenced in content.md orchestrator now have corresponding implementation files
  • Fixed 41 markdownlint errors in pre-existing short-form.md (MD031 blank lines, MD040 language specifiers)

Files Added

File Purpose
youtube/README.md Reference agent pointing to root youtube/ subagents
short-form.md TikTok, Reels, Shorts (pre-existing, lint-fixed)
social.md X, LinkedIn, Reddit - platform-native tone adaptation
blog.md SEO-optimized articles integrating legacy content tools
email.md Newsletters, sequences, FluentCRM integration
podcast.md Audio-first distribution, show notes, syndication

Design Decisions

  • YouTube as reference: Root youtube.md and youtube/ remain authoritative; distribution/youtube/README.md provides the pipeline integration point (chose simplest approach - matches existing architecture where root agents are authoritative)
  • Consistent structure: All agents follow established pattern (YAML frontmatter with name/description/mode/model, AI-CONTEXT markers, cross-references to pipeline stages)
  • Pipeline integration: Each agent includes content adaptation examples showing how upstream story/research assets transform into channel-specific formats
  • Cross-channel references: Every agent links to all other distribution channels for repurposing workflows

Verification

  • npx markdownlint-cli2 ".agents/content/distribution/**/*.md" → 0 errors
  • All 6 distribution channels referenced in content.md have corresponding files
  • Cross-references verified between agents

Closes t199.8

Summary by CodeRabbit

Documentation

  • Added comprehensive content distribution guides for blog articles, email campaigns, podcasts, short-form videos, social media, and YouTube, including platform-specific best practices, optimization workflows, SEO strategies, and integration guidelines.

Create content/distribution/ directory with 6 distribution channel agents
that complete the content pipeline's multi-channel fan-out:

- youtube/README.md: Reference agent pointing to root youtube/ subagents
- short-form.md: TikTok, Reels, Shorts (existed, fixed MD lint errors)
- social.md: X, LinkedIn, Reddit with platform-native tone adaptation
- blog.md: SEO-optimized articles integrating legacy content tools
- email.md: Newsletters, sequences, FluentCRM integration
- podcast.md: Audio-first distribution, show notes, syndication

All agents follow the established pattern (YAML frontmatter, AI-CONTEXT
markers, cross-references to pipeline stages and related tools).
Zero markdownlint errors across all 6 files.
@gemini-code-assist
Copy link

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 10, 2026

Walkthrough

This PR introduces a suite of content distribution agent configuration files covering blog, email, podcast, short-form video, social media, and YouTube channels. Each file contains YAML metadata and comprehensive markdown documentation defining workflows, best practices, formatting standards, analytics targets, and integration points for its respective distribution channel.

Changes

Cohort / File(s) Summary
Content Distribution Documentation
.agents/content/distribution/blog.md, .agents/content/distribution/email.md, .agents/content/distribution/podcast.md
New markdown guides defining SEO-optimized article strategy, email sequence workflows (newsletter, welcome, launch, nurture), and podcast production with show notes, audio specs, syndication, and cross-channel repurposing.
Social & Short-Form Distribution
.agents/content/distribution/short-form.md, .agents/content/distribution/social.md
New documentation for 9:16 vertical video optimization (TikTok, Reels, Shorts, Snapchat) with hook formulas and production workflows, plus multi-platform social strategy (X, LinkedIn, Reddit) with voice profiles and adaptation matrices.
YouTube Distribution
.agents/content/distribution/youtube/README.md
New README establishing YouTube as a distribution subagent with workflow definition, format specs (aspect ratio, resolution, length), and cross-channel repurposing outputs.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~18 minutes

Possibly related issues

Possibly related PRs

Poem

📡 Content flows through channels new,

Blog and email, shorts and true,

YouTube, social—every lane,

Distribution blueprints, crystal-plane!

A framework's song, from code to content's reign. 🎬

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: adding distribution channel reference agents to complete the content pipeline's multi-channel distribution strategy.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feature/t199.8

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link

🔍 Code Quality Report

�[0;35m[MONITOR]�[0m Code Review Monitoring Report

�[0;34m[INFO]�[0m Latest Quality Status:
SonarCloud: 0 bugs, 0 vulnerabilities, 61 code smells

�[0;34m[INFO]�[0m Recent monitoring activity:
Tue Feb 10 02:22:03 UTC 2026: Code review monitoring started
Tue Feb 10 02:22:04 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 61

📈 Current Quality Metrics

  • BUGS: 0
  • CODE SMELLS: 61
  • VULNERABILITIES: 0

Generated on: Tue Feb 10 02:22:06 UTC 2026


Generated by AI DevOps Framework Code Review Monitoring

@sonarqubecloud
Copy link

@marcusquinn marcusquinn merged commit 53d2c15 into main Feb 10, 2026
9 of 10 checks passed
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In @.agents/content/distribution/youtube/README.md:
- Around line 8-79: This file currently contains operational guidance (notably
the "Distribution Workflow", "YouTube-Specific Format Rules", and "Cross-Channel
Repurposing" sections) that must be moved into the canonical AGENTS.md or
converted into a pure index; relocate the procedural content and concrete rules
into AGENTS.md (preserving content and attribution), then replace those sections
in .agents/content/distribution/youtube/README.md with brief pointers/links to
the new AGENTS.md entries (leave the "Quick Reference", subagent table, and root
links as a purely referential index).

Comment on lines +8 to +79
# YouTube Distribution

<!-- AI-CONTEXT-START -->

## Quick Reference

- **Purpose**: YouTube long-form video distribution within the content pipeline
- **Authoritative Source**: Root `youtube.md` and `youtube/` subagents
- **This Directory**: Reference agents that integrate YouTube into the content distribution pipeline

**This is a distribution channel reference**. The full YouTube agent lives at the root level (`youtube.md`) with its subagents in `youtube/`. This directory provides the distribution-pipeline integration point so the content orchestrator (`content.md`) can fan out to YouTube alongside other channels.

<!-- AI-CONTEXT-END -->

## Subagents (Root References)

| Subagent | Source | Purpose |
|----------|--------|---------|
| `channel-intel` | `youtube/channel-intel.md` | Competitor analysis, outlier detection |
| `topic-research` | `youtube/topic-research.md` | Niche trends, content gaps, keyword clustering |
| `script-writer` | `youtube/script-writer.md` | Long-form scripts with hooks and retention curves |
| `optimizer` | `youtube/optimizer.md` | Title, description, tags, thumbnail optimization |
| `pipeline` | `youtube/pipeline.md` | End-to-end automation pipeline |

## Distribution Workflow

When the content pipeline fans out to YouTube:

1. **Receive story and production assets** from upstream pipeline stages
2. **Adapt to YouTube format** using `youtube/script-writer.md`
- Long-form script (8-20 minutes)
- Scene-by-scene breakdown with B-roll directions
- Hook optimization for first 30 seconds
3. **Optimize metadata** using `youtube/optimizer.md`
- Title variants with CTR signals
- SEO-optimized description with timestamps
- Tag generation (primary + long-tail + competitor)
- Thumbnail brief
4. **Publish and monitor** using `youtube/pipeline.md`

## YouTube-Specific Format Rules

| Parameter | Specification |
|-----------|--------------|
| **Aspect ratio** | 16:9 (landscape) |
| **Resolution** | 1080p minimum, 4K preferred |
| **Length** | 8-20 minutes (optimal for ad revenue) |
| **Thumbnail** | 1280x720, high contrast, readable text |
| **Title** | Under 60 characters, keyword-front |
| **Description** | First 2 lines visible, timestamps, links |
| **Tags** | 5-10 relevant keywords |
| **Chapters** | Timestamps for videos over 5 minutes |

## Cross-Channel Repurposing

From one YouTube video, generate:

- **YouTube Short** - Best 30-60s clip, 9:16 reformat (`content/distribution/short-form.md`)
- **Blog post** - Transcript-based SEO article (`content/distribution/blog.md`)
- **Social posts** - Key insights as X thread, LinkedIn post, Reddit discussion (`content/distribution/social.md`)
- **Email** - Newsletter featuring video + key takeaways (`content/distribution/email.md`)
- **Podcast** - Audio-only version with show notes (`content/distribution/podcast.md`)

## Related Agents

- `youtube.md` - Root YouTube agent (authoritative)
- `youtube/` - Root YouTube subagents
- `content/production/video.md` - Video generation (Sora 2 Pro, Veo 3.1)
- `content/production/audio.md` - Voice pipeline
- `content/story.md` - Narrative design and hook formulas
- `content/optimization.md` - A/B testing and analytics
- `youtube-helper.sh` - YouTube Data API v3 wrapper
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Consolidate operational guidance into AGENTS.md (single source of truth).

This adds substantial instruction and operational guidance inside a new agent doc. Repo learnings state AGENTS.md must be the authoritative single source. Please move this guidance into AGENTS.md (with pointers back here if needed) or reframe this file as a purely referential index without new instructions.

Based on learnings: “All instructions, documentation, and operational guidance should be maintained in AGENTS.md as the single source of truth.”

🧰 Tools
🪛 LanguageTool

[uncategorized] ~15-~15: The official name of this popular video platform is spelled with a capital “T”.
Context: ...peline - Authoritative Source: Root youtube.md and youtube/ subagents - **This D...

(YOUTUBE)


[uncategorized] ~15-~15: The official name of this popular video platform is spelled with a capital “T”.
Context: ...itative Source**: Root youtube.md and youtube/ subagents - This Directory: Refer...

(YOUTUBE)


[uncategorized] ~18-~18: The official name of this popular video platform is spelled with a capital “T”.
Context: ... YouTube agent lives at the root level (youtube.md) with its subagents in youtube/. ...

(YOUTUBE)


[uncategorized] ~18-~18: The official name of this popular video platform is spelled with a capital “T”.
Context: ...el (youtube.md) with its subagents in youtube/. This directory provides the distribu...

(YOUTUBE)


[uncategorized] ~26-~26: The official name of this popular video platform is spelled with a capital “T”.
Context: ...--------|---------| | channel-intel | youtube/channel-intel.md | Competitor analysis...

(YOUTUBE)


[uncategorized] ~27-~27: The official name of this popular video platform is spelled with a capital “T”.
Context: ...utlier detection | | topic-research | youtube/topic-research.md | Niche trends, cont...

(YOUTUBE)


[uncategorized] ~28-~28: The official name of this popular video platform is spelled with a capital “T”.
Context: ...eyword clustering | | script-writer | youtube/script-writer.md | Long-form scripts w...

(YOUTUBE)


[uncategorized] ~29-~29: The official name of this popular video platform is spelled with a capital “T”.
Context: ... and retention curves | | optimizer | youtube/optimizer.md | Title, description, tag...

(YOUTUBE)


[uncategorized] ~30-~30: The official name of this popular video platform is spelled with a capital “T”.
Context: ...thumbnail optimization | | pipeline | youtube/pipeline.md | End-to-end automation pi...

(YOUTUBE)

🤖 Prompt for AI Agents
In @.agents/content/distribution/youtube/README.md around lines 8 - 79, This
file currently contains operational guidance (notably the "Distribution
Workflow", "YouTube-Specific Format Rules", and "Cross-Channel Repurposing"
sections) that must be moved into the canonical AGENTS.md or converted into a
pure index; relocate the procedural content and concrete rules into AGENTS.md
(preserving content and attribution), then replace those sections in
.agents/content/distribution/youtube/README.md with brief pointers/links to the
new AGENTS.md entries (leave the "Quick Reference", subagent table, and root
links as a purely referential index).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant