Alright. So take a look at this. This is a web page that Claude's new dynamic workflows built for me in under an hour. And, no, these aren't some generic release notes or a summary from someone else's perspective on how to use Opus 4.8. This workflow spun up tens of agents to go through all 1,500
conversations that I've ever had with Cloud Code to tailor a full report on exactly how I should use this brand new model and what it should change around my approach. In addition to the report, it also created a full length two minute tutorial walking through every single feature that I should care about, how it works under the hood so I never have to go and rely on some generic tutorial that's pretty much a summary of the documentation.
And this is just one of three different use cases that I'm gonna walk through in this video to show you where dynamic workflows can really help move the needle in your day to day. So if you wanna learn the use cases, especially the last one, which I think you'll really like, then you wanna stick with me till the end of the video, and I'll save you from having to burn those tokens yourself.
Let's dive in. Alright. So like I said, this report walks through how I should alter my shift to using this model, how I should change my prompting patterns, what should stay the same, and what should differ or be slightly adjusted for this new model and the way it behaves. So one of the key things was being more literal with it. It's better at dealing with direct prompts without having to beat around the bush. And if I just wanted a overall summary of every single thing that I should do in my day to day based on all the conversations it's gone through and what it's seen in terms of patterns,
this would be my checklist. And before I walk you through the exact prompt that led to that report and the video, it's important to understand what we're solving for in this first use case. So if you're like me, you will see a brand new model come out and you'll be curious. What's different? And then you'll go on YouTube and you will inevitably see the parade of thumbnails and titles that say, this brand new thing is insane. Even though this model could be one incremental step change, which 90% are, where there are some pros and cons, but overall, it's not a night and day difference. So instead of clicking on Opus 4.8 is insane, Opus seven, or Opus 492,
what if you could just create your own tutorials
that are tailored to what you care about? So the way this works is that you ask Cloud Code to go through all the JSONL
files that have all your conversations,
and all of these are stored on your local computer if you use Cloud Code on your personal laptop.
And then you can have all of these agents
spin up and mind through all of the sessions and look for all the patterns.
And once it understands the patterns of how you use ClaudeCode,
how you prompt it, then you'll get tailored advice whether it's 4.8
or five or even you can use this for codex or Gemini. You can really tailor your own education and your own upskilling to the things that actually move the needle forward. When it comes to the prompt, you could send over something like this to generate a very similar report. So you would say, would like you to build a workflow.
These would be the magic words. Again, when you write the word workflow, you'll get a multicolored
name for the workflow, which means you're using the function that analyzes all JSONL
files. A JSONL file is a fancy JSON file, basically, restructured in a different way in folder path here. Now if you don't know the path, then one, you can ask Claude code. If I show you a little preview here, if we go to this folder, this has every single conversation that I've had in my YouTube folder. So you'll see that they are JSONL files, like I said, and you can use something like Sublime Text or Notepad plus plus to take a look at them. The TLDR is you will see a combination of assistant and you. Assistant and you. So that basically summarizes all the tool calls. It's very token heavy.
Having all these agents spin up outside of your context window using dynamic workflows will help them not bloat your existing conversation.
Then I give it the overall goal, which is to help me understand how to extract maximum value from this new model. Again, you can change this to whatever model you want. Then I walk through all the criteria. So step one is data analysis. So going through every single JSONL file and looking for my token usage patterns.
Then for number two, model comparison.
I like to invoke this Claude code guide agent. This is a sub agent that is native to Claude code. So its entire role
is to be the PhD scientist in the latest documents from Anthropic. So when you ask this a question, it's a glorified help desk. They'll go and double check everything that is on the website. So we'll be able to see the release notes and then compare it to step one's output, which is analyzing your core workflow. And then in step three, I basically walk through all the core synthesis and analysis that I want. So number one is some form of executive summary. Number two, a usage profile analysis, then a direct comparison of both competencies,
then prompting patterns, then skill and tool recommendations,
and then dynamic workflows that I could put together based on this new feature and advanced opportunities.
And in terms of the video that I put together, all I did was hook up something called Hyperframes,
which is an open source library that is created by Heygen
and then linked it to Claude code and told it to take this HTML page it put together and convert it to a short two minute video on two x speed. And the best part of this is once all of these agents that have been fanned out go and figure out how to accomplish the task, you can always materialize
this entire path and pattern by creating a skill. So in this case, I created something called model migration.
So in the future, when we have 4.9,
five, six, etcetera,
I can now run this every single time and quickly get my explainer HTML
and my video so I can quickly get up to speed with what matters to me. And by the way, if you want access to exclusive skills just like this one, along with all the exclusive content that we keep adding to our Claude Code Living course, then you'll wanna check out the first link down below. As these agentic systems mature, you're gonna want to mature your skill set as well. So if you're done sitting on the sidelines and just passively watching YouTube videos and you wanna go hands on and become a master in a matter of weeks, then check out the link down below, and I'll see you inside. Alright. Back to video. And for use case number two, I found that using dynamic workflows for deep research where you actually want all the agents to spin up and check each other's work versus spending $10.15,
30 minutes having an individual agent go and check a series of sources. Many times it tells you 200 or 300 sources, But in reality, it doesn't actually fact check itself.
There is no devil's advocate outside of that one running session. So running deep research, especially to look into how to leverage these features like dynamic workflows becomes really handy. This is a full report on every single claim it found on x on what dynamic workflows
seem to be able to do and not do. And with each one, it has either a link to a GitHub repo
or a link to an existing x post or a link to a report. So I can scan through all of this and see you can see right here, it says the word survives,
meaning it had a series of agents double check and fact check these claims from x to make sure that by the time it comes to us, it's distilled and validated. And then you have things like this, where obviously on x, people will make some bold claims on what something can or can't do. And then you have other posts that are unconfirmed.
So now you can look at this with a second set of eyes and double check and see if you can trust any of these claims that you see. Then you can see every single claim that seems to be cut. So this is amazing for double checking and basically peer reviewing via agents different types of research claims and information in general. This is the prompt that I used to execute this. So I said, I want you to research all the findings on dynamic workflows associated with Opus 4.8,
pull together everything that people are actually reporting about it, the real results, the claims, what holds up, and what is just hype. And then I go through and I tell it to use the Apify x scraper. So you can use all kinds of means to scrape tweets or go through tweets. They have their own API on x now, but I like to use Apify for all kinds of things including pulling YouTube analytics. So I just tell it to go and use the skill to find this what's called an actor, basically an app that you can use on Apify. Once it pulls all of those, then it goes through and it spins up all of these agents. And as it calibrated how it's going to execute the task, what angles it will look at, it asked me how deep do you wanna go. So one thing that most people are not talking about is if you use something like workflows or ultra code, you can intervene and tell it, I don't want you to go to the level of depth of having 60 or 70 agents. So this feature does burn tokens, at a a huge rate for big tasks. But you can also measure the task and scope it down if you need to. And twenty minutes later, it came back with the full response that linked to the very web page that I showed you, walked through the fact that it went through a 170 claims, spun up almost 200 agents to go through and adversarially
verify
all the passes on the features that seem to be legitimate versus the ones that seem to be more hype. And for the last use case, you can also use workflows to audit your existing Claude code ecosystem
to look for opportunities where you can use it better.
Specifically, you could have it take a look and audit your dot Claude usage.
And these are basically folders that have all the core assets at the project level and the global level. And these are things like your agents, your skills, your rules, your hooks, and commands.
So as you keep building and as you keep adding more skills, over time, things will go stale. And inevitably you'll have some inefficiencies.
So you can have these agents spin up and then tell you exactly what are the core things you should fix and why. Then as you go through, you could see if you have overlapping skills,
duplicate skills, and ideally what you should do about them. So this one here is telling me that I have 10 stock anthropic skills that seem to be duplicated. So perhaps during a demo for a client, I copy pasted it more than once. So now that is bloating my context against my will. If I scroll the bottom, here's another one where I seem to create this designer designer skill specifically for a YouTube video as a demo, but I never use it again. And these are the things that you don't have time to revisit.
So if you're building things up like your agentic OS, having the way to look at your low, medium, and high level issues or repeated contradictory rules is a great way to keep on optimizing maybe once a month. Because like I said before, this is not something designed to be used every single day. This is something you can use sporadically every couple weeks, maybe once a month. And there are only a handful of tasks that really deserve the level of token burn that you'll get by spinning up all these agents.
So the goal here is that you're able to constantly audit things like your clot MD, your rules and skills, etcetera, to look for ways that you can keep stepping up your game and making sure they don't have these areas of bloat or isolated folders where you spin something up, use it a couple times, and then you completely forget about it. And that's pretty much it. It's just three of multiple ways that I've been using dynamic workflows,
especially for personal usage for day to day tasks. So hopefully, gives you some inspiration for the different types of things you can use workflows for. Beyond just the business use cases, there are different things that I've tried with workflows like booking travel, looking through bookings and hotel sites and travel prices for airlines.
You can apply this to all kinds of very large meaty problems that need a lot of research and validation. If you wanna grab all the prompts that I showed you in this video, you'll find them in the second link down below. And if you wanna go much deeper on things like Claude code and become a master of it in just a couple weeks, then you'll wanna check out the first link down below for my early adopters community. I drop at least one new module a week, and I'm gonna walk through how I built the hyperframes
workflow and skill that I alluded to earlier in this video exclusively in there. So if you wanna check it out, then maybe I'll see you inside. And for the rest of you, if you found this video helpful, useful, and novel, then I'd super appreciate a like on the video and a comment if you so choose. I'll see you in the next one.