Building a second brain for your business isn't enough. And it's not because they don't work, they do. But it's because you're missing the layer that turns your company context into action. A second brain that actually runs your business has two layers, and most people are only talking about one. That's the context layer. Hundreds, sometimes thousands of interconnected docs holding every piece of your context across your business. But pointing Claude at that context layer doesn't solve for actually doing the work. For that, you need the second part, and that's the execution layer. The execution layer takes that context, runs your playbooks and SOPs over the top, and returns your finished work, and almost nobody is talking about it. In this video, I wanna show you what that looks like, how to build one without locking yourself into Claude or OpenAI forever, and how to share it across your team so every new hire and every agent works at your level on day one. And the best part is I'm giving this away for free as a template so you can set it up yourself. I'm inside of my company brain in Obsidian, and here, every single meeting transcript,
Slack thread, and email lands as a markdown file automatically. In fact, there's so much context in here that with the right execution layer, I can start to automate real work, like generating proposals from sales calls. So I built a skill exactly for that. It's called slash generate proposal, and it pulls the prospect's call transcript, our pricing playbook, and past proposals to tailor a document straight from the live data. That brain holds the context, but the skill is what ships the work. And that works great for me, but the second I need anyone else on my team to run it, things start to fall apart. I have some options. I could Slack the folder around, drop it into drive, and if we're on a clawed team plan, I could publish it as an org skill. But the thing is half of my team live in codecs on OpenAI, so that's out of the question as well. And the second one of them updates their copy, everyone starts to drift. So you can see it just doesn't really scale. Instead, I have a private team skills marketplace. It's one install command and every skill I've ever built shows up on their machine. Any update from me or anyone else pushes to the whole team automatically,
and it works across whatever AI tool they're using, which, by the way, is the part that most people are getting wrong because every week, there's a new AI tool. Today, Claude Code is out in front. Next week, it might be Codex. And in a few years' time, who knows? The way I've built this, the marketplace doesn't care which one your team is on, and I'll show you why in a second. A skill is how you encode your standards, your processes, and your taste into one portable file that anyone can run. And it doesn't matter whether that's an agent or a person. You can drop them into a shared marketplace and the same skill that made you faster now makes the whole team faster. That's how a five person team starts shipping like a 50 person team. It's because the leverage is in the context layer and the execution layer working together,
not in the additional headcount. An execution layer also fixes two other things you're probably struggling with, your team's baseline quality and whether your documentation actually gets used. I'll come back to both in a second. But first, I wanna show you the piece that
marketplace into your brain because skip this and you've really just built yourself a fancier version of copy and paste. Inside every skill, you get two ways to handle context. Option one is that you hard code the context in. You can copy your brand voice, your pricing, or your customer avatar data straight into the skill file or create a references folder. Option two is that you reference it from somewhere else. The skill points to your brain and pulls the live version when it runs. Hard coding is fine when it's just you using the skill, but it ends up being a bit of a trap as time goes on. Because the moment some of the context changes, you've now gotta go find every skill that copied it and rewrite each one. It's a pain. Referencing is better because it makes the context layer the single source of truth for that type of information. A file gets updated, and every skill that points at it gets the new version automatically. So you don't have to worry about stout context in your execution lab. This is the move that turns your skills into living business methodology.
The brain evolves, and every skill evolves with it. One update to the brain, and that information is leveraged everywhere. Most people's skills are stuck on one machine. You build them, and they make you faster. But every teammate ends up rebuilding the same skill from scratch on their laptop. And personal productivity goes up, but team output stays about the same. Your team marketplace fixes that. Now I said earlier that this marketplace doesn't care which AI tool your team is on, and here's why. The whole thing is just a private GitHub repo. There's nothing else to it. And the reason that it works is that agent skills are an open standard. Claude code reads them natively. Codex reads them natively, and whatever ships next week will read them natively too because the format is the format. You own the layer, which means the tools you run it in are replaceable. I built a free GitHub template for it. The link is in the description below. You click use this template, set it to private, name it after your company, and there's two plugins that ship inside. One holds your team skills, and one is the admin plugin that handles the setup, importing skills, and publishing. Then clone the repo locally. The easiest way to do this is just to ask to do it for you. But once it is cloned, open the folder in Claude code, either in your IDE or the desktop app, and ask Claude to read the read me and run the setup. It'll scan all the files and walk you through it. The important thing here is your license because my template is MIT license, meaning you can use it for free in your business. But for your own skills, you wanna stay unlicensed. When Claude's done, ask it to push the changes up to GitHub. That'll update the read me again with the new install commands you need for Claude code and codex. Now you can just copy them in and the marketplace is installed. Now if I run slash plugins and head to marketplaces,
Acme is there. I can browse plugins and you'll see the two ship five default, team skills and marketplace admin. You wanna install both and then start fresh Claude session so the new skills load in. Now I need to push some of my skills into team skills. So I've opened my main Claude repo where I keep the ones that I use daily, Instagram carousel, lead magnet, YouTube scripting, and thumbnails. I wanna ship these to the rest of my team, so I use the marketplace manager skill to add them into the marketplace. And the nice thing is you can add a skill from anywhere on your machine. Just point at it and say, add this to the team marketplace. It copies it in and bumps the plug in version. And when team skills starts feeling a bit too broad, you can scaffold this further. A sales skill plugin, an ops one, a customer success plugin, all in the same marketplace but separate plugins. That way teammates only install what's relevant to their role. The marketplace scales the same way your org does. Your local skills will decay. You build one, you get busy, and the file goes stale. And that's the end of it really. Team skills are different though, and here's why. Say your marketing lead notices an issue and corrects their version of the skill. That correction goes back into the skill dot m d, and they can push that to the marketplace. Next time anyone on the team runs that skill, the correction is baked in. You can even have permissions set up in GitHub, which allow you to control who can and cannot update those skills. That one move sorts out both of the problems I mentioned earlier. The skill doesn't rot because it's the thing actually doing the work, and every run is a chance to sharpen it. And the quality lottery is gone too because the new hire who just joined yesterday is now running on the back of every lesson your team has ever taught it. One floor going up every week. Multiply that across six skills, then 60, then across departments,
and the marketplace becomes the operating system of the business. Every new hire inherits every lesson learned. Every agent runs at the same level as your best operator. The brain holds the context, and the marketplace runs the work. Both keep getting smarter over time. If you don't have the brain side built out yet, that should be your next watch. I walk through exactly how I run mine, including how Claude watches every piece of content I touch and feeds it straight in. If you wanna build the marketplace, the template is free and at the link in the description below. And if you want a stream of vetted production ready skills, you can drop straight into that marketplace.
That's what I'm building next. The skills marketplace waitlist is in the description below.