Codex: Build Your Full AI Marketing Team (Agents + Skills)
Riley Brown walks through the seven-plus skills he runs daily inside Codex, OpenAI's super app, to do 95% of his content and marketing work, covering grounding agents in real examples via a YouTube researcher skill, an Excalidraw diagram skill, a Readwise second-brain skill, and Gmail/calendar email-manager skills, all turnable into scheduled automations.
Riley BrownWatchTranscript found
Quick learning frame
Read this before watching.
Coding-agent workflow is the loop of inspect, route, plan, edit, verify, summarize, and decide what should be automated next.
New playlist item from Riley Brown; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to build and stack a personal layer of repeatable skills and plugins around a coding agent so it handles most of your marketing workflow, grounding its output in your own references and automating the recurring parts.
Watch for the shift from claim to mechanism. The learning value is the point where the transcript reveals a repeatable action, tool boundary, context move, review habit, or artifact.
Concept diagram
Where this video fits.
01Inspect context
02Route tool
03Plan work
04Edit safely
05Verify behavior
06Report next step
Deep lesson
Turn this video into working knowledge.
9,300 cleaned transcript words reviewed across 2,473 timed caption segments.
Thesis
Codex: Build Your Full AI Marketing Team (Agents + Skills) teaches a practical coding-agent workflow move: Riley Brown walks through the seven-plus skills he runs daily inside Codex, OpenAI's super app, to do 95% of his content and marketing work, covering grounding agents in real examples via a YouTube researcher skill, an Excalidraw diagram skill, a Readwise second-brain skill, and Gmail/calendar email-manager skills, all turnable into scheduled automations.
The goal is not to remember the video. The goal is to extract the operating principle, tie it to timestamped evidence, test how far the claim transfers, and make something reusable.
0:00
Skills vs plugins
“Yesterday I was working on my laptop and I realized that 95% of the tasks that I do on my computer for content and marketing is inside Codeex. And Codeex is OpenAI's brand new super app. And the...”
In Codex you access a saved skill with slash and a plugin with the at sign; plugins are bundles of skills and abilities (the Vercel plugin, for example, contains many skills) while a skill is an instruction file for the agent, so at-mentioning a plugin lets it pick the right skill and slash targets a specific one. Open the plugins panel in Codex or Claude Code and write down which of your tools are plugins (bundles) versus individual skills, and note the slash versus at-sign trigger for each.
18:34
Ground your agent
“video and as we go along I'm going to use these skills together. Right? So I I wanted to create an excalad diagrams. Please do it in my voice and you can use the YouTube researcher skill to...”
Grounding means pointing the agent at a useful reference instead of relying on OpenAI's generic training; the YouTube researcher skill pulls real transcripts so the agent can, for example, write an intro in Theo's voice or explain skills in Karpathy's style, giving output shaped by examples you actually like rather than a generic model opinion. Use a YouTube-researcher-style skill to pull a creator's transcripts and have the agent draft five hooks grounded in their real examples, then compare them to an ungrounded draft.
43:35
Skills to automations
“that work done just with an AI agent. And then this is how you kind of like skill stack here. And we're able to just like schedule all the meetings. I can say, "Okay, I want to schedule...”
An email manager built from the Gmail and calendar plugins searches the inbox, filters and dedupes paid brand offers, researches fit using the YouTube skill, and builds a priority table of companies, then suggests open calendar times; once a workflow produces output you like, you tell Codex to turn it into a skill and then a daily automation. Take one email or research task you repeat, run it once to a good output, then prompt the agent to save it as a named skill and schedule it as a daily automation.
01
Inspect context
Start with this video's job: Riley Brown walks through the seven-plus skills he runs daily inside Codex, OpenAI's super app, to do 95% of his content and marketing work, covering grounding agents in real examples via a YouTube researcher skill, an Excalidraw diagram skill, a Readwise second-brain skill, and Gmail/calendar email-manager skills, all turnable into scheduled automations. Treat "Inspect context" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:00, where the video says: “Yesterday I was working on my laptop and I realized that 95% of the tasks that I do on my computer for content and marketing is inside Codeex. And Codeex is OpenAI's brand new super app. And the...”
02
Route tool
Use "Route tool" to locate the part of the coding-agent workflow mechanism the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 18:34, where the video says: “video and as we go along I'm going to use these skills together. Right? So I I wanted to create an excalad diagrams. Please do it in my voice and you can use the YouTube researcher skill to...”
03
Plan work
Turn "Plan work" into the reusable artifact for this lesson: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal. This is where watching becomes something you can inspect and reuse.
04
Edit safely
Use "Edit safely" as the application surface. Decide whether the idea touches a browser flow, a local file, a model choice, a source document, a UI, or a review step.
05
Verify behavior
Use "Verify behavior" to prove the lesson. The evidence should connect back to the video title, transcript anchors, and a concrete output, not a generic best-practice claim.
06
Report next step
Use "Report next step" to carry the idea forward: save the prompt, checklist, diagram, or operating rule that would make the next agent run better.
Example
Source-backed artifact packet
Convert the video into a scoped artifact request that includes the transcript claim, mechanism, acceptance criteria, and proof. The output should be a coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal..
Example
Coding-agent workflow proof brief
Separate what the speaker claims, what the demo actually proves, and what still needs outside verification before you adopt the coding-agent workflow pattern.
Example
Teach-back module
Transform the lesson into a definition, a Inspect context -> Route tool -> Plan work -> Edit safely -> Verify behavior -> Report next step diagram, one misconception, one practice exercise, and a check-for-understanding question.
Do not learn it wrong
Treating the title as the lesson without checking what the transcript actually says.
choosing tools by hype
losing context across agents
letting parallel sessions become invisible
Letting the lesson drift into generic Codex vs Claude comparison.
Letting the lesson drift into feature lists without task routing.
Letting the lesson drift into claims that ignore limits or recovery.
Do not count this as learned until these are true.
01
State the transcript-backed claim in your own words: Riley Brown walks through the seven-plus skills he runs daily inside Codex, OpenAI's super app, to do 95% of his content and marketing work, covering grounding agents in real examples via a YouTube researcher skill, an Excalidraw diagram skill, a Readwise second-brain skill, and Gmail/calendar email-manager skills, all turnable into scheduled automations.
02
Explain the practical stakes without hype: New playlist item from Riley Brown; queued for transcript-backed review, topic mapping, and a practical learning artifact.
03
Map the idea onto the Inspect context -> Route tool -> Plan work -> Edit safely -> Verify behavior -> Report next step sequence and name the weakest link.
04
Produce the artifact and include the evidence that proves it: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal.
Put it into practice
Give this grounded prompt to Codex or Claude after watching.
You are helping me turn one specific YouTube video into real, durable learning.
Source video:
- Title: Codex: Build Your Full AI Marketing Team (Agents + Skills)
- URL: https://www.youtube.com/watch?v=sL_KBnYB17I
- Topic: Codex + Claude Workflows
- My current learning frame: Pick one recurring marketing task, ground it in your own YouTube or Readwise references to get an output you like, then have Codex save it as a skill and schedule it as a daily automation.
- Why this matters: New playlist item from Riley Brown; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:00 / Evidence 1: "Yesterday I was working on my laptop and I realized that 95% of the tasks that I do on my computer for content and marketing is inside Codeex. And Codeex is OpenAI's brand new super app. And the..."
- 1:55 / Evidence 2: "page. When you use codeex, you're basically prompting an AI agent and you can select your model. And this AI model has full control over your computer. It can edit, delete, and create files on your computer. Basic..."
- 6:54 / Evidence 3: "depending on your niche or depending on who you are, you might have a specific taste that you like. And so what you want to do is you want to actually ground the model or point your AI..."
- 10:07 / Evidence 4: "karpathy style for skills. And this sounds exactly like him. Think of Codex as a little operating system around a language model. At the center there is the model. The model can read text, write text, reason, and..."
- 18:34 / Evidence 5: "video and as we go along I'm going to use these skills together. Right? So I I wanted to create an excalad diagrams. Please do it in my voice and you can use the YouTube researcher skill to..."
- 43:35 / Evidence 6: "that work done just with an AI agent. And then this is how you kind of like skill stack here. And we're able to just like schedule all the meetings. I can say, "Okay, I want to schedule..."
- 47:33 / Evidence 7: "I will have all of those skills updated and you can try them in codeex or claude code. If you want to test them out for free, you can test them in our new experimental AI agent product..."
Video-aware target:
- Prompt lane: Coding-agent workflow
- Mechanism to extract: Find the workflow rule that explains when and how to use Codex, Claude Code, browser control, dashboards, or manual review.
- Artifact to produce: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal.
- Artifact must include: task class; agent/tool choice; context packet; verification step; handoff/recovery rule
Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, transcript support, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable mechanism from the video: Find the workflow rule that explains when and how to use Codex, Claude Code, browser control, dashboards, or manual review. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal.
5. Include:
- a plain-English definition of the core idea
- a diagram or structured model using this sequence: Inspect context -> Route tool -> Plan work -> Edit safely -> Verify behavior -> Report next step
- answers to these source questions: What workflow pain is being solved? | What exact coordination mechanism is shown? | What evidence proves it changes the work?
- 3 concrete examples that apply the video idea to real agentic work, such as rate-limit routing; browser verification after a UI edit; long-running /goal session review
- 2 failure modes the video helps prevent, chosen from the transcript evidence and these likely risks: choosing tools by hype; losing context across agents; letting parallel sessions become invisible
- a checklist for the next real workflow, focused on: routing decision, context portability, verification, handoff summary
- one practical exercise with a clear done signal: Route three recent tasks across Codex, Claude, browser checks, and manual review with a reason for each.
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.
Quality bar:
- Make this specific to "Codex: Build Your Full AI Marketing Team (Agents + Skills)", not a generic Codex + Claude Workflows essay.
- Each workflow rule must point to a timestamped claim or demo moment, then state what remains unproven.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- Avoid these generic drifts: generic Codex vs Claude comparison; feature lists without task routing; claims that ignore limits or recovery.
- If evidence is weak or missing, stop and say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.
Misconceptions
What to stop believing.
One agent should do every task.
Different tools have different strengths. Routing is part of the workflow.
More context is always better.
Relevant context helps; stale context causes drift and cost.
Practice studio
Learning only counts when you make something.
01
Transcript evidence map
Separate what the video actually says from what you already believe about the topic.
3 source-backed takeaways with timestamps, confidence, and a transfer note.02
One useful artifact
Apply the video to a real workflow and produce a coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal..
A reusable artifact with a done signal and one verification step.03
Coding-agent workflow teach-back card
Explain the coding-agent workflow mechanism to someone who has not watched the video yet.
A 90-second explanation, one diagram, one example, and one misconception to avoid.
Recall check
Answer first, then reveal — without rewatching.
In Codex, how do plugins and skills differ, and how do you trigger each?
What is 'grounding' and how does the YouTube researcher skill provide it?
How does Riley turn a useful workflow like the email manager into something recurring?
Source shelf
Use the video as a doorway, then verify with primary sources.
