B (3:03)

Yeah.

A (3:04)

And agent is, you know, you're giving it, it's a goal. I mean, the best way. Yeah. You're giving it a goal and you're hoping that over time it gets better and closer to that goal.

B (3:15)

Exactly. Yeah, that's exactly it. And I just think that's a nice way to lay down your head. Is chat, is question to answer, agent is goal to result. So when you chat to an agent, you might give it a task like build me a website for xyz. And then it goes away. It does its work and outputs this wonderful website to you. But it's really important to understand what's actually happening in this step here. So inside this agent step we have what's called the agent loop. So you give it your prompt or task and it goes through these three steps here, which is observe, think and act. So let's just say, for example, we're actually going to do this demo after this. But if we gave the agent a simple task like build me a minimalist portfolio site for Greg Eisenberg. It's going to start by like you've loaded in that prompt. It's going to check if there's any files in the workspace that it can work with. Like maybe you've got some information on Greg Eisenberg. And then it's going to think about what to do next, it's going to act, and then it just keeps going through this loop. So for that actual example of building the portfolio site for Greg Eisenberg, let's just say it was a blank agent. We hadn't given it any context. The first thing is it's received this prompt to build the website. And the first thing it's going to be thinking about is, okay, well I need to build this website about Greg. Who the hell is Greg Eisenberg? So it's going to then decide to do some research into Greg Eisenberg. It's going to research everything about Greg and then feed it back into this observe step. So then it's going to think to itself, okay, so I've got this prompt to build a website. I've now got my research here, so I know exactly who Greg Eisenberg is. And then it's going to start thinking, what is the next step? And the next step is probably to write up A plan to build the website. So it might write up that plan, feed that back in. Now it's got the research, the prompt, the plan, and it will think, all right, what next? I should probably write the code. To write the code, feed it back in. And it just keeps going through this loop as many times as it needs until it can conclude that the task is complete. And how it concludes that the task is complete is based on the parameters that you set in your prompt. So, you know, if you're giving it a research task, you might say compile 10 sources and then create a report as a PowerPoint. And then once it's compiled 10 sources and built the report as a PowerPoint, it can conclude that the task is complete and then give you the output as the user. The agent itself is made up of these four components. So it's the LLM which is the brain behind it. So think like Claude Opus 4.6 or GPT 5.4 or Gemini 3. It's the model, it's got the loop, which means it just keeps going until the task is done and doesn't stop after one response. So you're going from ping pong to it continuing to go, rather than you having to sit there babysitting. Connects in all your tools, and then it connects in all the context. And a platform that facilitates this process and basically facilitates this loop to happen is known as an agent harness. And all of the popular AI agent platforms on the market that you'd be familiar with are just agent harnesses. They're just applications where this loop is facilitated. And I want to actually run this little prompt I prepared earlier. I want to open up Codex, Claude code and antigravity, and I'm going to show you this loop actually happening in action. So I've nicely prepared before the episode, these three demo folders which we're going to run in. So I'm going to open up Demo one to work in in Claude code. And the way these folders work is if you've used, if you're familiar with like any of the chat models like Claude and ChatGPT, there's a projects feature which is where if I open it up, actually try not to get dizzy with me switching tabs so much. But you know, if we create a project here, it contains all your chats in one place. It allows you to upload all your sources here, which is your context, and then you can even add custom instructions which tells it how to behave within this project. And that's also known as a system prompt, which we're going to dive into how to do this with agents as well later. But it's a similar concept that you'd be familiar with if you've used projects before. But instead of the project being here on the cloud, we're actually working within projects that are local on our computer. So I've just selected this demo one for now. Then we're going to run build a minimalist portfolio site for Greg Eisenberg. And then this little bit here just tells it to actually spin it up, like to publish it on the web in a preview mode so we can see what it's done. So I'm going to run that. So.

A (8:06)

So this is, this is Claude code.

B (8:10)

Yes. Yeah, Right now we're in Claude code and this is just accessing it through the desktop app for Claude. So I'm just going to run that and then I'm also going to give the same prompt to Codex here. So this is the Codex app and you can see same concept, it says let's build. We can choose a folder on our computer to work in like demo 2. And then we're gonna give that a prompt as well and we're gonna tell it to host it on a different one. And then also in Anti Gravity, so you can see same concept, we're going in, selecting a folder and then we will give it the prompt as well.

A (8:52)

How should people think about security and these different products?

B (8:57)

I like to think of security as in just like scoping what they have access to. So by default, Anti Gravity, Claude Code and Codex, they're very, very secure because they're built by these massive companies that have a lot on the line to protect. And I just, you know, if you, if you're building out these agents to manage different elements of your business, like the other week I built one that does manages meta ads. And obviously that's quite a risky thing to give an agent control over managing ad budgets. So it just comes down to like what you feel comfortable giving the agent. And also you can control what privileges or you control what tool permissions as access to so that if it was compromised for whatever reason, the worst case like isn't that bad. And that means, you know, just giving it like read only access to certain important platforms and stuff like that. Does that make sense?

A (9:50)

Yeah, totally. I mean comparing it to like Open Claw, which is like.

B (9:55)

Yeah. Which I want to touch on at the end as well because that same thing, just another harness, but it's just like the Wild West.

A (10:02)

Cool.

B (10:04)

And one thing like a nice little analogy to think about these harnesses is what we're going to learn today is we're going to learn to drive. So we're going to learn about how to, you know, steer the car, like how the pedals, the brakes work, the accelerator works, the handbrake. But then once you know how to drive, you can kind of jump in any car, whether it's like an old Toyota, a Range Rover, and you inherently sort of know what to do. And that just comes down to understanding all these key concepts that we're going to go through today. And you can think of the agent harnesses like different cars, and some of them will have better features like seat warmers and cruise control. But it's all. Once you know how to drive, you can pretty much jump in any of them and you use them. So we've just got our thing over here building tar, building the website for Greg, and it's going through this agent loop right now. So you can see here it's actually decided that it's going to launch an agent to go and research Greg Eisenberg. And I've connected it up to Perplexity. So it's now using Perplexity to research Greg. So it's going through its first step of the loop. And I imagine that Codex has also done something similar here. You can see it's still working, but it's gone and started to build this out through the loop. I think Claude Code does the best job of actually displaying that loop and allowing you to see what it's thought about compared to anti gravity and codecs. But it's all just going through the same sort of loop process that I described earlier. And I think when you say you

A (11:34)

hooked it up to Perplexity, didn't. It's not like you asked it to hook it up. Right. It just sort of did it.

B (11:42)

Yeah. Because I've. I've given Claude code Perplexity as a tool via mcp, which we're going to get into very, very shortly, all about mcps, which is just connecting tools up. So we can see that in Anti Gravity, it's gone. You can see this thinking process, it's gone. Now examining the current directory to figure out if there's an existing project or I should build one from scratch. It's then going, I'm now going to start to build this thing and then it's built the website and it's given us a little local host preview here. So it's created this nice little portfolio site for you, Greg.

A (12:22)

What's interesting is it's super Minimalist. And I mean it did its job, right? Like it. This is. I would totally launch something like this.

B (12:36)

It actually looks really nice. Did it, did it scrape your email address? Correct?

A (12:39)

That's, that's not my email address and I don't live in Canada anymore, so. But yes, there's a few copy things, but other than that, yeah, it's done

B (12:48)

a pretty good job.

A (12:49)

It did.

B (12:50)

And if we go. So that was anti gravity. If we go into Codex as well, you can see here it's finished doing its website, which is somewhat similar. I think I prefer Gemini's.

A (13:01)

Yeah, I agree.

B (13:03)

If we check out Claude as well, it's still going. You can see this loop, right? It's gone. Okay, first off, who is Greg Eisenberg? It's gone. And researched Greg then fed it back into that observe step and it's gone. All right, what next? Now I need to create the HTML file so it's written the code and then now it's gone. Okay. So he wanted it spun up on this local server. So now I'm going to spin it up on the server and then the last iteration of the loop is to check that it's actually done and can conclude the task is complete. It's opening it up and screenshotting the website and then reviewing the screenshots to check that the website is complete. And you can see here it's done another pretty good job. This one's very similar to the Gemini one. Hey, that's true. But yeah, that's just like demoing how that loop is actually working in real time.

A (13:57)

Yeah, I mean what comes to mind just by watching this is like how many people on the planet would benefit from a very clean website? And like how do you set up these agents so that like, you know, maybe it's like a cold email loop, right? Like you're sending cold emails. Hey, I built you this website so and so business. Do you want it? It's going to cost $250.

B (14:20)

Yeah, yeah, that's actually a great idea. Pre making websites for companies and it's like an off the shelf thing. It's like, hey, I made you this website if you want it. Like if you want to own it, it's $250. You can just do a mass cold email thing. Cool. So I think that's like pretty much illustrated that Agent Loop example. So I'm just going to go back to our trustee board over here. But you can understand that it's just like all these apps are just different flavors of the same thing. And then what we're going to be working up to today is my workspace looks something like this is I have, you know, a big, like a folder for each company or client that I'm working in. And then I'll have folders underneath with all my heads of departments. And then within those heads of departments, I'll have Skills and mcps, which we'll get into and context. And then I've got like an overarching one at the top to just to sort of manage them all. But we're going to be focusing today on building out this Executive Assistant to take care of just your manual day to day tasks and free up at least one to two hours extra per day. Cool. So to build this out like we did with our demos, it's running off your local files. So we're going to create a folder here called Executive Assistant. And also through building out this assistant, it's going to allow us to clearly explain each of the concepts of building an agent in real time. And the way I like to think about building agents is onboarding them like a real employee. So if you took on a real executive assistant, you couldn't expect just for them to come into the office and you give them a task without explaining your business first, your clients, what you do, the tools, because they just would not be a very good executive assistant. So that's the first step that we need to go through when we're building out this agent. So I'm actually going to work in Cowork at the beginning. So Cowork is just another agent harness to do pretty much the same thing as all the others, just that loop connecting in your tools and the context. So you can see here, this was my little previous session where I was building some diagrams. But we can go and you can follow along in Claude code or Codex or Anti gravity or whatever agent harness that you want to work in. But I just think that Cowork has really nice, simple UI for people to just understand really well what's actually going on. So we're going to open up this Executive Assistant folder and you can see here that if we ask it, write me a cold email and send that off.

A (17:05)

So people are going to ask, how did you transcribe? You did like a voice to text. Yeah.

B (17:11)

So that is, I use one called Monologue, but there's a lot out there on the market. Whisper Flow is another popular one and it just allows you to hold a little button on your computer and just yap away and it will just transcribe it neatly into text and I find looks good.

A (17:27)

Monologue looks really good.

B (17:28)

Yeah, I think it's built by the team at every Every. It's a cool product, but so what it's asking, so it's straight away, it's got no context here, so it's working out of that folder here on our computer, but there's nothing in the folder and it has no memory of our previous sessions. And it's asking, like what? Like, what do you even sell? And then we've got to kind of give it, like, who do you target, what tone do you want? This is all things that our executive assistant should know. So I'm going to stop the response there. And one thing that's really important to know, which might be a bit of a shock, moving from chat to agents, is that these agents memory work a little bit different. So if you're used to using chat models like ChatGPT and Claude, if you open up a fresh session in one of these chats, you don't give it any context, you don't upload any files and you just say, who am I and what do I do? It's going to know a scary amount about you. And that's because with these chat models, they have memory built in automatically. So every time you sort of say things that are important, the chat model saves it to its memory in the cloud that you can't see and you can't control. And with agents, you have to set up memory and control exactly what you give it. And I think that's actually a benefit, not a limitation. Because what happens is if you're using ChatGPT and it's got the auto memory, you're having conversations about three different companies, maybe you're asking for relationship advice, and then all of a sudden when you ask it to write a landing page copy, it's pulling in context from all these other places that you don't really want in there. So with these agents, you need to actually set up that context and memory. So as you can see, when we asked it to write a cold email, it just had no idea about anything. So we need to give it a context file. And the way you do this, right, so you can see this example here, it doesn't know anything about us, and that's because we haven't populated what's called an Agents MD file. And an Agents MD file is just like a system prompt, just like if you've created any custom GPTs before, you have that field for custom instructions or in the project, like I just showed before you've got that field for custom instructions and it just gives it this context that's kind of always there, always on and you put in there things like its role context about you, your preferences for working. And then what happens is every new session, before it answers your query or task, it loads in all this context to its brain as part of that observed step in the loop. So I have pre prepared. Pardon me. So I've pre prepared a Agents MD file here. So if we drag this in over here, this when you're working within Claude code it's called a Claude md. When you're working within Gemini it's called a Gemini md. But when you're working within Codex or openclaw it's an Agents md. But it's all the same concept. So we can drag this into our folder here and if we open up this file for a little preview,

A (20:46)

we

B (20:46)

can see here I've got in here all about me, what my business does, my working preferences, like the tools that I use and what for, like notion project management, stripe, we've got, you know, all the information my item, customized, loaded with context here. And I pre prepared this. But if you want to make one of those, you can just use Claude chat or cowork, whatever and you can ask it to help you build out this Agents MD file and to just ask you interview style questions to extract all the context from you and then build the file. So if I jump back in now, if I go to a new task, same folder and we say write me a cold email, it's going to have all that context.

A (21:35)

Yeah, that's what we hope.

B (21:38)

That's what we hope. There we go. And it knows, you can see this files over here. It knows automatically to load in this file if you title it correctly.

A (21:50)

Yeah, it's basically just like a reminder file.

B (21:55)

Yeah, pretty much. It's just like loading it in so it has all this set context before you even start working. And, and one of the other big shifts to make which comes with moving from chat to agents is prompt engineering. Used to be the big thing. It was like here's the ultimate prompt for going viral on social media or use this prompt for this. And now it's all about context engineering. It's about how well can you load up your agent with all the information about your business so that your prompts can be stupidly simple like write me a cold email and you're still gonna get an amazing result. You can see already here it's already asking like is it a brand or sponsor Potential partner or consulting client. So it's already got that context book a call, you know, it's loaded in everything that we've given it from that agent's MD file. And then now we've got a pretty decent cold email there ready to go. So that's basically agents MD files for you and you want to create one of those to onboard your agent with all the context it needs. And if you have lots of context, without getting into too many advanced concepts here, sometimes what I will do is I will create like a folder called context, load that in. And in here it's got different files about me, brand, voice, idle, customer profile, et cetera, et cetera. And then in order to keep this smaller, I will then just say in this clause MD file, before answering any questions or before doing any tasks, read my context folder to understand about myself and my business. Because by default if you just have this context file in here, but no Claude md, it won't load all that into the session by default. But if you tell it in this file that it always loads in. So then check this file, you can start to like string all your context together. And a lot of people have done that with Obsidian, so they'll have like in the Cloud MD file, they'll tell it to go check their Obsidian vault for their second brain to go and find context. So that is agent MD files explained. So that's how you actually, when you're onboarding your agent like our executive assistant, you can train it up on who you are and your business. And then as you can see here, you know, I've got folders for all these different roles roles in my business and in the head of marketing, that Claude MD file would look somewhat similar, but in the top it would say instead, like you are my head of marketing. You speak like this. These are your tasks, these are your roles. And then the second thing here is about memory and the self improving loop. So we've solved the problem. Now try not to get too dizzy with me switching tabs. But we've solved the problem of our executive assistant not knowing anything about us or our business. But now we have a new problem, which is it doesn't really remember the intricate details or your preferences across sessions unless you're manually going and updating that Claude MD file. So you can see here, if we go, my favorite color is lavender. It'll probably say something like got it noted.

A (25:09)

Yeah, that makes sense, right? Because it's. And it's adding. Where, where's that adding it.

B (25:15)

Well, it's not Adding it, that's the thing. So we can tell it. My favorite color is lavender and it's gone. The users just shared. That's that thinking step. It's like the users just shared this. Like no, nothing needed. Good to know. I'll keep that in mind. But then if we go into a new session, same folder, and we go, what is my fave color? Mind my spelling, it's gonna say I have no idea what your favorite color is, even though we just told it. And that is an issue, you know, because if you're working, you know, you've got like a head of sales or something and it keeps. It signs off your emails wrong and you tell it, you correct it and you say never sign off. Emails with cheers, say warm regards and it will go, okay, got it noted. But then the next day you start working and it does the same thing again. It's like, like my agent's broken. But really it's not. It's running off those context files in the back and unless you are manually updating, won't know to save that preference. So what I like to do is I like to add in something like this to my agents nd file. So this is just a little simple thing. You can pause the video and copy it. But I like to. I'm just gonna remove that context file for now. That was just to illustrate that example of adding more. But we're just working with this one file for now. So I'm just gonna open this up so I can edit it and I will quite often add something on the bottom like that little snippet. And this basically just says actually you know what, I might just add it at the top, just so it's there. Top of mind for my agent because I think this is really important. So you can see I've just added this in. It just says read all files in context. Read Memory md. This is what you've learned over time. And then when I correct you or you learn something new, update the relevant section in Memory md. And it's just got a couple little things here and it just says keep Memory MD current. When something changes, update it in place and replace outdated info. So we can do command s to save that. And then I'm gonna add another file here. We can actually just duplicate this and this one I'm going to call Memory md. And then we can open up this one and I'm just gonna remove all this context here. Except I'm just gonna keep those sections.

A (27:56)

So Memory MD is basically, I mean it's Just it's what it sounds like. Right. It's basically like you want to, you know, if the goal is to build, you know, AI employees that do things for us, they're going to need to. Need to remember our preferences. Right. A good employee remembers preferences exactly. And learns over time and not that compounds. So memory MD is just a place that you can just make sure that over time it, you know, your, whatever you're using, Cowork or whatever it ends up, it ends up getting compounded, getting smarter. So ultimately you might be trying things like Cowork and you're not getting good results. And a big part of that is you don't have cloud MD and memory MD sort of set up.

B (28:45)

Exactly, exactly. And now the thing is, some of these agent harnesses have started to add in this memory system that we're doing manually, telling it to update. Some of them have got that built in automatically like Open Claw and I believe like Manus and some of the others have that built in automatically. But it's still important to understand because it's just doing the same thing under the hood, except they've just set this up for you. So we've got this here. Now we've got our Memory md, our Claw md, and then now if we go back into Cowork, if we do a new session in that same folder and we say my favorite color is

A (29:29)

lavender, better remember,

B (29:34)

for the sake of the demo, I hope that it does what it's told.

A (29:38)

It's going to remember it.

B (29:40)

You can see here. Perfect. It's gone. Good, I'll remember that. Let me save it to memory. And now you've got this big memory file that builds up over time and whether, for example, this is your executive assistant. So it might be saving preferences like how to sign off emails or don't connect with clients on Slack. I always want to keep client comms on email. But if you're building out like ahead of marketing, it might be preferences about how you like your ads structured in Facebook Manager. If you're building. If you've got a folder where you're working on a website or an app, it might be things like don't use dark mode. And then it will update so it'll never use dark mode again. And they just compound over time. So as you start to build up these rules, the amount of errors go down and this just compounds and compounds over weeks and months.

A (30:27)

Remy, have you seen some of these memory MD files get so big that at a certain point is just ineffective?

B (30:35)

Great question. I personally haven't had that happen to me yet. I haven't hit that threshold. But a best practice for those claw MD files is to keep it around, like no more than 200 lines. And yeah, I could imagine if you started to build this up over years and years, you'd eventually hit a point where all the rules are stepping on each other's toes and you could probably go through and do a bit of a manual Clear. But I haven't hit that threshold yet. Cool.

A (31:02)

So people don't need to worry about cluttering their memory md.

B (31:08)

I wouldn't worry too much. I mean, if it's saving like this, like the silliest little things, like the tiniest corrections, you can maybe update that, claw that MD to say, only save, like substantial corrections, you know, and then you can have a bit more control about what it's saving. So that's probably what I would do there. But once you've set this up, now when you say something like quit writing so formally, it's gonna do the task, then update its agents md or in this case, Claude MD to keep tone casual, never formal. And then now in any new sessions, it's gonna keep that preference over time, which is pretty cool. So now we've got our executive assistant set up with memory and we've given him his role. We now need to connect our tools. Cause by default, most of these agent harnesses, they just have web search baked in. But if you want to actually start linking it up to your tools, like Gmail, Calendar and everything else, which is where the real productivity gains are made, you need to do so via what's called mcp. And I actually got, Greg, I got this MCP explanation from when you had on. Is it Ross, Mike? Yeah, yeah. So this. He did a great explanation and it just dropped into my head really nicely. And it's basically that before mcps, your agent or your LLM, in order to speak to tools, it had to kind of learn their language because Claude speaks English, Notion speaks Spanish, Gmail French, your browser speaks Japanese and Slack speaks Chinese. And it was capable of connecting to those tools, but it required these extensive custom developments that took a long time. But then Anthropic actually created mcp. Is that right?

A (32:48)

Yep, that's right. Yeah.

B (32:50)

Anthropic built MCP to basically sit as this translator in between your tools so that Claude can still just speak English and your tools can just speak their languages. And this MCP speaks every language and then just translates your calls from your agent to the tool and then from the tool back to Your agent. So just set a really easy standardized way to connect tools up. And that's what we're going to be using to connect all of the tools to our Executive Assistant. So if we go back into cowork here, you can see that Claude make it really, really easy to connect up your tools. You can just go to Connectors, browse Connectors and they've got like hundreds of all the biggest apps that you probably use and you can just, you know, add them, sign in. Pretty self explanatory but I believe codecs would be the exact same. You know, you can go skills or if we go settings they probably have like. And then like Manus is the same for example, if you go into Manus we can see we can go and connect our tools. Very, very similar process. And then same with Perplexity Computer. You know, you've got your connectors and you can connect all your tools in here. It's just all using that model context protocol, mcp. So I've already, before the episode gone and connected all of the tools that I use most like Gmail, Google Calendar, Granola Notion, they're all set up already as mcps. And what I'm going to do now is I'm actually going to open up this Executive Assistant folder in Claude code to sort of demonstrate how these harnesses are all the same and they work off your local files. And the real future proof AI stack is just having those markdown files on your computer. And the reason why I like to work in markdown files is because it's just the easiest sort of format for your LLM for your agent to actually digest and understand compared to if you were to give it your files as like a docs or a PDF file. So I like to use Claude code within Visual Studio code. So you can see here I'm just going to. It looks very similar to Anti Gravity. I'm just going to open up our Executive Assistant folder here. And the way that I see the future of this all going Greg, is I think that everyone's going to have their, what I call an aios like an operating system. And this will just compound over time like you saw with adding the rules and getting less errors, but with adding your tools and then skills which we'll get into, which is basically just training AI on your processes. And I think that everyone's going to have like an AI operating system they work in and everyone will just have personal agents and agents to manage each department of their company and people won't actually use these apps anymore. Like I've connected up Gmail, Google Drive, Calendar, granola for my meeting notes, Stripe for payments, notion for project management. And I don't even enter these tools anymore. I just sit and claude code as one central place. And an example here is I sent myself before the episode, I sent myself an email from a fake prospect and I also entered in granola a fake meeting with this prospect. So now I can say things like summarize my inbox from today.

A (36:07)

You know, someone might ask like, well how important is that really? You know, like is that such a high value task? Like are what are high value tasks that you're actually getting done here?

B (36:22)

So

A (36:24)

or maybe, or, or maybe you get a lot of emails, you know,

B (36:28)

well if, you know emails is a big thing, if you do get a lot of emails. But just having like all those tools connected in one place and not having to switch and copy paste context. So you'll see an example here. Right, so we've got summarize my inbox from today, which is like one of the most basic agent tasks ever. But we can see this is one I sent earlier. We've got this one email here, like our call today, excited after your call, wants next steps. So I might just say here, okay, great, review my meeting notes with Multoshi from today and then draft up the email, sending the proposal and creating the stripe payment link and then go into notion and set up the project. And where this starts to compound even more is when you start to build out skills for each of your processes. Because every time I do a process even like this, manually prompting it and I know I'm going to do it again at some point, I'll then just turn that into a skill. And then you eventually end up, if you automate like three to five tiny manual processes each week with skills, you eventually end up automating like your entire life with these agents.

A (37:35)

Right? So it's not so much in like summarize my emails where it's super, super valuable. It's like that's where the starting point is. And then we want to like manipulate it and use it and go deeper and stuff like that. That's when exactly these tools really, really are valuable.

B (37:54)

And you can see here, it's now connecting all my tools. So it's gone into granola and found the full meeting of what we went through today. It's now going into Stripe to create the product link and then it's going into notion to set up the project and then it will, it should create the draft ready for us. To go to send out that this

A (38:17)

is really like a new way of working, right?

B (38:20)

Yeah, it is, it is. It's so new. And I, and I even this task, it's really simple, right? Just sending an email based on a call with a proposal link and stuff. But like even if you can just do something like seven times faster without having to go into all these tools, copy the meeting notes into the page to give it context on your meeting, it really starts to compound. Then you start to fit like a week in a day and then seven weeks in a week and stack that up over a year and you're going to be miles ahead of everyone else. And when we get into skills you're going to see how this continues to get even better. But you can see here, it's drafted the email, it's pulled in all these insights from our call in granola which is like where I do my meeting notes. Then it's created the stripe payment link here ready to go.

A (39:11)

That's cool.

B (39:12)

And then now I can just go send this email and it will use my Gmail integration to go and send it and then that's really cool. It is. Hey, I think this is the new way of working. And Cody Schneider who had on the pod the other week, I saw a tweet from him and he said that in the future everyone's going to have like an AI operating system like this and you're going to have like the 100x employee because everyone will come into their role with a pre existing AI operating system and then build out skills for all their manual processes similar to how I was describing and just keep building skills each week for anything manual that comes up until eventually their entire life and work life is automated. Great. As you can see here, it's now created the draft here in Gmail ready for us to go. And if we're happy with it in the platform I could also just ask called to send it there and then. But then what like also gets really cool is I'm going to demonstrate now how I actually build out skills for these processes. So I know I've talked a lot about skills so far. I want to just give a little overview on what skills actually are. Yep. So the easiest way to think about skills is SOPs for AI. So standing operated. Standing operated. Oh my God. Standard operating procedures for AI. So it means once you explain something once, you never have to explain it ever again. An example of this is without skills. If you are creating a proposal for a client and you're sitting in your Claude Chat or whatever agent harness you're using, and you ask it to create this proposal, you're probably going to go back and forth a bunch of times. Remove, change the formatting here, use this color blue for this part, put the price at the bottom instead of at the top. And eventually, maybe after 15 minutes, half an hour, you landed a proposal that you're really happy with and you send it. And the next week you want another proposal written. But unless you're going and finding the same session and working in that same session, it's going to have completely forgotten all of these preferences. And even if you have that memory system set up these kind of things, you don't really want clogging up your memory. They're better off as skills, which is basically, it packages up that process into a skill file, and in that skill file, it's basically just a markdown file that explains the exact process that you went through so you could create a proposal skill. And then every time now you need a proposal written. It just takes that skill, knows exactly what to do, and then you can have that proposal the same way every single time.

A (41:50)

So is a skill like a memory file? Like, what's the difference between essentially a memory MD and a skill? Is it just like a memory MD file for a particular job to be done?

B (42:05)

That's pretty much like exactly it. And all of these agent harnesses pretty much now have skills as a feature. So you can see here, like if we go into Codex, for example, they've got skills here. Same with Claude as well. And when you're working with these agent harnesses that operate like, mostly locally off your computer, you can see here, it actually operates out of this hidden file called a Claude folder. Skills. And these are all of the skills that I've created. There's tons of. And if we open one up, for example, like this one here, let's find a good one. For example, I've got this one here for writing viral hooks. And in this skill we have a skill file which is basically like your memory md, which explains the exact process for writing viral hooks. And then it's also got packaged in here, some references like hook formulas.

A (43:06)

Okay, so wait, so how did you create that skill?

B (43:11)

Okay, so there's two ways that I find useful to create skills is one, you can have an idea of a skill you want to create off the bat. So like viral hooks, for example, I had this course on viral hooks, which I transcribed, put it into Claude, and Claude has this by default. It has a skill creator skill added into it. Same with all of these major agent harnesses. They'll have a skill creator skill. So it's kind of like skillception. You use the skill creator skill and you say, hey, take this course on viral hooks and create a viral hook skill. And it can create it like that. That's one way. And then it will package it up nicely with that skill md it'll do the whole thing for you.

A (43:49)

Wait, you asked it to take the course?

B (43:54)

Yeah, I uploaded the course, like the

A (43:57)

full transcript of the course, literally.

B (44:00)

And I said, yeah, based on this course on viral hooks, build me a viral hook skill. And then I use that for my content team. So just like we're building the executive assistant folder, I've got a folder called content team and I've got that, that uses that skill for me. And the second way to create skills is going through a process manually once with Claude. And then if you know you're going to have to do it again, like that proposal example, you can just say, once you've done the task, hey, create a skill for what we just did and it will package up that process you went through. And that's the second main way that you can create skills.

A (44:37)

So in your viral hook example, if you go into that folder again.

B (44:41)

Yeah.

A (44:41)

So you have a references folder.

B (44:44)

Yeah.

A (44:45)

So that is probably like. Was that. Yeah, let's open it up. I'm just curious.

B (44:53)

See here it's got a full thing about like.

A (44:56)

So is this from the force?

B (44:58)

Yeah, this was basically from like a course I put into it.

A (45:02)

And did you ask it to create a reference folder? Like, how should people think about.

B (45:07)

No, it just didn't. It just did it. So I think what would be great is if we could actually demonstrate building a skill live.

A (45:14)

Let's do it.

B (45:16)

And so, for example, like this process here, I might. I could create a skill called like a daily brief skill, you know, that goes through and summarizes like your calendar, your inbox and your projects in notion and plans out your day for you in the morning. And then you can run that on a scheduled task because a lot of these agent harnesses now are starting to introduce scheduled tasks. So you can just run it on 9am every morning. Use my daily brief skill to prepare me for my day. But I think another cool one here, just to show you an example, right. Of how my new, like how intricate I make these skills is, let's just say for this fictional meeting I had with this person, I might say,

A (46:02)

can

B (46:02)

you draft up an email? I want to refer Multoshi to My good friend Sebastian, who has an AI automation agency and can help them out better with their needs. And then we can just go, Sebastian's email is. And we can just say that. Right? And then now it's going to be able to take the notes from Granola, all the context, and then draft an email connecting these two. A prospect with a friend. And you know, I have different like referral things set up like that with people in marketing agencies and that's just like a little manual process. They're tiny. Maybe takes 15 minutes out of my day, but then I can just go, I want you to use your skill, creator skill and create a Sebastian refer skill so that whenever I ask you to refer someone to Sebastian, you know exactly what to do and you know his email address. And then that'll build out that tiny skill for us. Tiny process. But it means I like, I know in the future I'm gonna have to refer someone to Seb again. And even if this skill now saves me 15 minutes, another five or six times they start to compound when you create skills for every single little process in your business.

A (47:28)

Yeah, I guess it's like we should just be asking ourselves like, you know, in our day to day life, like what are all the jobs to be done?

B (47:37)

Yeah.

A (47:37)

And what are all skills that we need? Like what are the repetitive processes or SOPs as you talked about? And then just setting up as many as possible.

B (47:48)

Right.

A (47:48)

To make our lives easier.

B (47:50)

Exactly. And just to give you a little demo here. So I sort of alluded to that folder structure at the start of the video and this is it here. So we've got workspaces AI with Remy and for example, I can open up my content team. And within this folder this is just like a more elaborate version of our executive assistant. But we've got our Claude MD in here which explains you are like the main orchestrator. You have these sub agents. It's just a more elaborate version of that called md. But I've got a skill within this for like a meta ads analysis. So that was a process. For example, if you're a marketing agency owner, this is probably like the kind of stuff that you can get inspiration from, like ads analyzing, you know, taking competitors, ads libraries, breaking down all the creatives and their landing pages. So I built out this ads analyst skill where I literally just do ads analyst and then I paste in like the ads library URL like that and I'll click run. And I did an example yesterday with the Oodie, which is a super large econ brand. And it ran through and basically scraped all of it, took screenshots of all the landing pages. It went and scraped all of the ads that they were running, all, like, 220. It then did a full deep dive here on all the ads. Visual analysis, copy analysis. Why did this work? What could be improved? It basically did a breakdown of all the landing pages with screenshots, and it did a master report here about everything that's going on. So just did a full breakdown. And that was like a manual process that I would have gone through when I used to run, like, my marketing agency. And that probably would have taken me like, three or four hours. And then I went through to build out this skill. I went through the process once with Claude. Like, I started a fresh session, and I was like, all right, go to this ads library URL, scrape this, do this, do this, do this for like, two hours. And then after I'd done the entire process, I just said, use your skill, creator skill to make a skill for ads, analyzing and package up the entire process we just went through as a skill. And then now whenever I want to do that process again, I can just invoke the skill and it knows what to do, which is pretty cool.

A (50:11)

Crazy. Crazy.

B (50:13)

Absolutely crazy. So, so now the Refer Sebastian skill is live. And now whenever I want to refer someone to Sebastian again, I can just say, yeah, refer to Sebastian, and it will just start to use. It will use that skill. That's example, the tiniest process. But you build, like, those up for all these little tasks you do day to day, and then it just compounds and compounds and compounds. And I can already think of an idea here where you could. Then you can change skills together. So you could, example, have like a meeting prep skill that prepares you for a meeting by researching the guest and compiling some talking points. You might have like a podcast research skill, for example, Greg, for a guest that's coming on. And you might also create a morning brief skill. And in the morning brief skill, you can say, if there's any meetings coming up or podcasts in my day, use the podcast research skill to research the guest. And you can chain them together and build some really, really cool workflows.

A (51:21)

Yeah. And you can have it so it sends you an email, right?

B (51:25)

Yeah, exactly. And then now these harnesses are starting to get more and more autonomous. Like, they're starting to add, like, you know, in the car, they're starting to add, like, cruise control and stuff. Like, now within most of these harnesses, you can schedule tasks like in cowork or Claude code now and you can like for example this one here, you can go new task and I could say like run my morning briefing skill and then set that to go every, every morning at 9am and then now it's like an automated workflow that like you've just got running every morning now, which is pretty cool.

A (52:00)

Yeah, I'm, I'm doing this right now. Like for example, I'm, I'm buying a new car right now and it's like a particularly unique like color that I want and feature set and there's just none, none really available. So you know, every three hours I'm scraping all the different car marketplaces. That's great. And then I'm getting a notification that you know when something comes up and it's, it's crazy, right? Like it saves me. I'm one of those people that like, if I didn't have this, I would be spending an hour of my day just like checking religiously every single CarMax and Cars.com and AutoTrader and all these websites and refreshing like a insane person.

B (52:51)

So yeah, the schedule, great example there. But you know this like this is a skill that would be relevant for my executive assistants. Same with that car one that could be a good executive assistant skill. But then I've got those more elaborate skills built out for like you know, my content team, that ads library scraping one and then I've got like you know, a research, weekly research skill for my newsletter team and that runs on a schedule every Thursday morning to go and scrape. Like I've built the skill out so it goes and scrapes Twitter and Reddit to find what's new in AI. Um, but yeah, skills are so, so powerful. Combine them with like your MCP so it can use your tools and then you can start to just train up your agent on all the processes in your business. And I did a, a build out on open Call for a agent to manage meta ads and it went pretty viral. And the, the way I built this was with all these key concepts. So Open Claw functions the exact same way. So I hope it hasn't timed out, but I've remote accessed into my OpenClore dashboard here and you can see it's just operating off an agents MD file in the backend but instead of the Claude folder It's in the OpenClore folder. And then it's got a couple of these other ones here. It's got a memory md, it's got some of these other ones that it's added on like a soul which Tells it its personality and an identity, which tells it who it is. But it's that same concept of markdown, context files, connecting your tools and then creating skills. So that Meta Ads Manager, one that went pretty viral, I just planned it out with Claude. I was like, I want to have this open call, manage my meta ads, help me write the Agents MD file to tell it, you are my Meta Ads media buyer. You do these processes. And then I created skills, so I created a add creative skill so it knew to go look in the Dropbox folder and create creatives. I created a copywriting skill so I knew how to write good copy for the business. And I just built out there's probably maybe 15 different skills. And then I would combine scheduled tasks, which is cron jobs with skills and the context files, and then just give it all the tools it needed and just following the same process as we just went through to build the executive assistant, I had an OpenClaw meta Ads media buyer, which was sick.

A (55:19)

I love it. And for the beginner, did you recommend people use openclaw or should they be using Cowork or Manus and some of the ones you showed?

B (55:29)

So, great question. I would say that openclaw is probably one of the hardest to learn and set up. Of these harnesses, I would say Cowork is probably the easiest. I think Perplexity computer, you did a video on it. It's pretty simple too. Same with manners. But I would definitely learn and get comfortable using like Claude code or one of these other ones before I started to play around with openclaw. And I would also have all the processes built out in Claude code first. So, for example, that executive assistant, over the next two weeks, I might build out a bunch of skills like the Sebastian refer skill, like a daily brief meeting prep, et cetera, et cetera. And then once I'm happy with how it's all functioning in Claude code, then I could look to migrate that into openclaw, where it has that more autonomous nature to it. So that's kind of how I think about using OpenClaw and those other harnesses. Yeah.

A (56:28)

Cool. All right. Anything else you wanted to.

B (56:32)

I mean, like, really, there's no right or wrong way to run these. Like, that was the executive assistant. I've got one built out for all the other departments in my business and then other businesses I work on, I have the same. And you can just kind of build out that structure with what works for you. You've got like. One other thing to mention is global versus project level, which I'LL just go over super quick. So like those skills for example, you can add them at a global level, which means they apply to every single project you work in, whether it's the executive assistant, your head of marketing, and some skills you want globally because you might use them in every chat. Like a truncate skill that I created which just makes whenever I want to make something shorter, it makes it shorter without compressing the sentences, but just removing sentences that don't need to be there. And that's something I want in every session. So I've got that in global. But you can have project level skills like that Sebastian refer skill. I would not want that with my marketing head of marketing because it's just like clogs up the context and you don't need it there. So I would have that as a project level for example. And you can have global skills versus project skills, Global Claw MD versus Project Claude md. And same with mcps. You have global MCPS and Project mcps. That's probably the other concept to go over. But look, other than that, that's pretty much the entire agents crash course. So it's just that loop running in the backend to complete your task and connecting in your tools, your context and the LLM all in one place. And I'll just say to work out what roles you want to start to build out an agent for. Go into Claude or your favorite chat model and get it to help you build out those context files through an interview style process. Just say ask me questions to build this out. I'll connect all the tools that you need and then start building out the skills through daily use. And then pretty soon you're gonna have like pretty powerful AI agents built for every single aspect and department of your business.

A (58:39)

Remy, thank you so much. I'll include links in the show notes in the description where you can go follow him, get to know him a little bit better. And I appreciate you coming on and dropping some sauce. Thank you man.

B (58:52)

Thank you so much for having me on. Greg. It's been a blast.