YouTube Automation Agent

Build an AI production assistant for YouTube automation. Daily briefings, script writing, multi-channel management.

A complete agentic workflow for running faceless YouTube channels. It knows your channels, writes in each channel’s voice, tracks what you’ve published, and tells you what to work on next. One vault, unlimited channels, zero context loss between sessions.

The vault structure

youtube-agent/
├── Channels/
│   ├── channel-one/
│   │   ├── config.md       # voice, audience, pillars, format rules
│   │   ├── calendar.md     # content calendar and publishing schedule
│   │   └── analytics.md    # what's working, what's not, observations
│   └── channel-two/
│       ├── config.md
│       ├── calendar.md
│       └── analytics.md
├── Scripts/                 # finished scripts, organized by channel
├── Ideas/                   # raw ideas, each as a separate note
├── Knowledge/               # reference material the agent draws from
├── Notes/                   # general notes and observations
└── Logs/                    # daily session logs written by the agent

Each channel has its own config.md that acts as a creative brief: channel identity, target audience, content pillars, tone, format, length. When Claude writes a script for that channel, it reads that config first. Three channels with three different voices, three different outputs.

How augent supercharges this

The Knowledge folder is where this gets powerful. Instead of manually copy-pasting articles and transcripts, augent feeds it automatically:

take_notes with url: "https://youtube.com/watch?v=expert-breakdown"

A top creator breaks down what makes thumbnails convert. Augent transcribes it, structures it with frontmatter and tags, and drops it in your vault. When Claude writes your next script, it draws from that knowledge.

search_memory with query: "hook strategies that increase retention" and mode: "semantic"

Six months of ingested expert content, instantly searchable. Claude pulls the best techniques into your scripts without you digging through notes.

The daily commands

Save these as Claude Code slash commands in ~/.claude/commands/:

/good-morning

Read my Logs folder for the most recent entry. Read the content calendar
for each channel in Channels/. Check the Ideas folder and Scripts folder.
Give me a short briefing: what I did yesterday, what's still open, and
your top recommendation for what to work on today.

/write-script [channel] [topic]

Read the config.md for the specified channel. Read the content calendar
to check what's been published recently. Search the Knowledge folder for
relevant reference material on the topic. Write a script that matches
the channel's voice, format, and length rules. Save to Scripts/.

/research [topic]

Search my Knowledge folder for existing material on this topic.
Summarize what I already have and identify gaps. If I provide URLs,
use take_notes to ingest them into Knowledge.

/wrap-up

Review everything I worked on today. Write a log entry in Logs/ with:
what was accomplished, what's still open, and exactly where to pick up
tomorrow. Update the content calendars if any scripts were completed.

Setting up the channel config

Each channel’s config.md is the creative brief Claude follows. Example:

# Channel: Stoic Shorts

## Identity
60-second philosophical shorts for men 18-35.

## Voice
Direct. No filler. Speak like you're giving advice to a friend, not
lecturing. Use second person. Short sentences. End with a question
or a reframe.

## Format
- Hook in the first 3 seconds (pattern interrupt or bold claim)
- One core idea per video
- 150-180 words total (60 second read time)
- Close with a callback to the hook

## Content pillars
Discipline, focus, money mindset, relationships, self-improvement

## What NOT to do
- No "in this video" openings
- No listicles
- No generic motivation ("believe in yourself")

Add as many channels as you want. Each gets its own folder, its own config, its own calendar.

The compound effect

Day one, Claude writes decent scripts from your config. By month two, your Knowledge folder has 50 ingested expert breakdowns, your Logs show patterns in what you struggle with, and your analytics notes tell Claude what actually performs. The scripts get sharper because the context gets deeper.

This is the difference between prompting a generic AI and having an agentic workflow that knows your brand.

Build Your First Workflow

The general pattern behind this workflow.

More Examples

Content, research, copywriting, scriptwriting, and operations workflow templates.