The bait, then the rug-pull.
A self-taught engineer who reads AI research papers for fun and works inside a platform used by hundreds of AI applications sits down to explain the one thing most beginner guides get backwards: simplicity is not a limitation, it is the only approach that actually works.
Who's talking.
Where the time goes.
01 · Hook
Cold open clip plus subscribe ask, then host frames the problem: most people using AI agents are not getting more productive.
02 · Why simple agents beat complicated ones
Complexity is a content strategy, not a productivity strategy. Boring workflows finish. The extravagant ones get clicks.
03 · Why your first agent failed
Models predict tokens, not intent. They have no agency, no relationship context, no common sense. Understanding this is the prerequisite to building anything useful.
04 · Good vs bad prompts
The agency spectrum analogy: a model responds the same way a low-agency employee does to a vague ask. Step-by-step instructions produce step-by-step results.
05 · Why Codex beats Claude Code right now
Rate limit generosity and compute subsidy math. Not loyalty; whoever gives the most compute for the price wins today.
06 · Real use cases
Sponsor email filter, bookkeeper replacement, receipt aggregator, weekly analytics reports. Anywhere data is scattered, an agent can aggregate it.
07 · Live Codex demo: connecting tools
Full walkthrough of Composio as tool router, connecting YouTube, Dubb analytics, cal.com, Linear. Shows how to fix expired auth links by screenshotting the error and prompting the agent.
08 · How to identify what to automate
Two categories: anything repeated often, and discovery mode. Connect all tools and ask the agent what it notices. Both start by documenting your weekly tasks.
09 · Why the lazy prompt works
The sponsor report is built incrementally. By the time the final prompt is sent, the agent already has YouTube stats and Dubb analytics in context.
10 · What is a skill?
Skill files store name plus description in active context; steps are only loaded when called. Analogy: knowing chapter titles vs reading every page. Reduces memory bloat and improves performance.
11 · Recursive improvement and closing
How to fix bad outputs via recursive prompting. Personal story of going from failed startup exit to credibility by sticking with it. Final message: consume and do, not just consume.
Lines you could clip.
"There is what looks cool and there is what works. And what works oftentimes is boring."
"The quality of input has to be good because when the quality of input is good, the quality of output will be good."
"Information is no longer a blocker."
"The best skills are the ones you generate after a successful run."
Things they pointed at.
Word for word.
The four steps between an idea and a working automation.
Building a useful AI agent is a coaching job, not a configuration job, and the order of operations matters more than the tool you pick.
- AI models have no agency and no relationship context; they respond to the literal quality of instructions the same way a junior employee with no initiative responds to a vague task.
- Starting with someone else workflow is a mistake because you inherit their context: their tools, their data sources, their edge cases. Your workflow has to start from your own repeated tasks.
- The context window is a resource: building toward a complex output in small confirmed steps means the final prompt can be brief because all the prior steps have already loaded what the model needs.
- A skill only earns its place after a successful run. Saving a failed session as a skill just encodes the failure into a repeatable process.
- Discovery mode, connecting your tools and asking the agent what patterns it sees, surfaces blind spots you would not have thought to automate because you did not know they were problems.
- Recursive prompting is the fix for bad outputs: tell the agent what was wrong, ask it to try again, repeat until one run succeeds, then immediately save that run as a skill.
- The gap between what you pay for an AI subscription and what the compute actually costs is the hidden variable in platform comparisons; generous rate limits mean more practice iterations per dollar.
- Consuming information without acting on it is a different kind of procrastination; the dopamine of learning new things substitutes for the friction of doing them.




































































