What’s up engineers? Indie Dev Dan here. As you go from base agents to better agents to more agents to custom agents all the way up to orchestrator agents and even give your agents their own devices to operate, you’ll quickly approach a problem. Where did you put that notion CLI skill? Where did you put that cracked review agent? Where is your new cloud code multi-agent planning command? If you’re an engineer working on one to two repos, what I’m about to show you doesn’t matter at all. If you install skills or plugins from the public internet without reviewing them, this video is not for you either. But if you’re an engineer working on 10 plus code bases with agents, and you’re building specialized private skills, agents, and prompts, this video was made for you. I have run into this problem as well. I’ve got skills everywhere. I’ve got prompts everywhere. I’ve got agents everywhere. I want to share a simple meta skill you can adopt to coordinate
[00:01:02] sharing your private skills, agents, and prompts across your codebases, teams, and agents. So, let me concisely define the problem. Us, the developer, we’re deploying skills, agents, and commands all over the place. We have duplicates all over the place in our 10 plus code bases. The problem is simple. We have endless skills everywhere. They’re out of sync. They’re duplicated and they’re hard to coordinate across your engineering team. For example, you might have a deploy skill that works similarly across your codebases, but you’ve been losing track. You’ve been copying them. You’ve been just sharing them with your engineering co-workers and your agents, and they’re just getting out of date. And this problem is exacerbated when you have multiple developers working across your team with multiple agents of their own. We’re just copying skills. We’re copying agents. And there’s no real shared access. Now again, if you’re working in a single codebase, this isn’t really a problem. All your prompts, all your agentics, your prompts, skills, and agents, they’re all just right there.
[00:02:01] But once you start operating in many code bases, you run into a serious problem. How can we solve this? We can solve this with a meta skill, a skill that unlocks other skills, agents, and prompts. I’m calling this the library. Call it whatever you want. In our previous video, we looked at how Stripe handles this problem. They use a meta tool called the tool shed. Here we’re going to focus on a meta-skill and broaden this solution a little bit to cover skills, agents, and prompts. So we have one skill to unlock them all. I want a coordinated solution to distribute my agentics over and over and over across my devices, teams, and agents. All right, so that’s the idea here. So what does this give us? This allows us to stack our skills, our agents, our prompts, and then if you want to, like I like to, you can put a just file on top. And so this is how I think about building with agents right now. This is how I think about agentic engineering. Everything starts with these four pieces and specifically these three pieces, right? These are the most
[00:03:00] important pieces. I think of skills as raw capabilities. Agents allow us to attain scale and parallelism. And our prompts, just one-off single file prompts, let you orchestrate these two levels below. A lot of people are overkilling skills doing everything inside the skill when you really have several other key primitives that you can work with. So this solution taps into that. The great part about the library is that we have a single reference point. So you can think about this like a package.json file or a pyproject file where we basically are storing references. As you’re going to see in a second here, the library file actually just points to existing GitHub repositories or local files. And that means staying synced between all of your projects is super simple. And this means when you have a single source of truth, you have yourself, you have your agents and your co-workers can just sync and manage this one library file. So that means that all you need to do is have this library file and the meta skill and you’re good to go because the library file is just going to reference the GitHub repository. So this is exactly
[00:04:01] how this solution works. We have a reference to private GitHub repository. Very important. When you’re building specialized solutions and you’re getting paid for it, you’re not putting this stuff out in public. Your top-notch skills, agents, and prompts should absolutely be private. I know a lot of vibe coders, you think that everything is just out there in the public. Trust me, it’s not. We need a way to distribute this privately. Of course, we can also touch public repos. And with this system that you’ll see in a moment here, we can also just reference local file paths. Something super critical to mention here, this is an agent-first solution / library. It is a skill. There is no code associated with this. You can see here that is how it’s kicked off. No matter who is using it. All right, and that gives us a lot of very powerful capabilities. I’m predicting we’re going to see a lot of pure agentic solutions as we move through this year. Just another benefit to mention with a system like this, you of course get syncing across all of your devices. We’re going to walk through a clear example of this between myself here and my Mac Mini
[00:05:01] agent that I showcased in our previous video. I’ve run into this problem over and over as I’m spinning up agents on my device and I’m spinning up agents on my Mac Mini device. I’ve also got more devices coming in. There’s a big trend going on right now that’s been unlocked or should I say revealed by the whole open claw and claw movement. It’s not having an agent run rampant on your device. It’s having a team of agents that can operate very very well against your specific domain problems. That’s where all the value is. More on that later, but you can see how this solution aids that. We need a way to distribute all of our powerful prompts, agents, and skills. That’s exactly what we’re doing here. And so here’s the full workflow. Just a couple more slides here. I just really want to nail the point home of why this is so important. And again, if you’re an engineer that just operates on a couple code bases, this isn’t for you, okay? You don’t need this. Just use cloud code plugins. Just install from wherever. This is about private agentic distribution. So, here’s what it looks like. And here’s exactly what we’re going to do in just a moment here. We’re going to build first. We’re then going to catalog with the library.add command.
[00:06:01] And this is going to update our catalog. This gives us pointers, references to existing code. Because the big idea here is that you don’t want to interrupt the flow of when you’re natively building out your prompt, skills, and agents inside of the actual value generating repository. And then you can, of course, reuse them. All right. So on your agent, your team and onto your Mac Mini or whatever your devices are. And this includes, you know, cloud sandboxes as well. So this is the full workflow. Build, catalog, distribute, use. And here’s what the API looks like. It’s all based on this single YAML file. So we can add items to the catalog, we can use items from the catalog, we can push back updates to the source repositories, we can list, we can search, and then we can sync. And so sync is super important here. This is not just syncing your catalog. This is syncing the actual code bases to make sure that you have the latest version. In essence, this is very very simple, but I needed to build out a concrete solution for this because I
[00:07:00] kept running into this problem and kept doing things the sloppy fast way, which is to just copy things and then they go out of sync, out of date very, very quickly. So, let’s manage our agentics the right way. Our prompts, agents, and skills.
[Walkthrough demo: 00:07:30 - 00:24:00]
Dan walks through a Mac Mini screenshare demo of the library skill. He demonstrates: (1) cloning the public ID library template repo. (2) Creating a private library file pointing to private GitHub repos containing meta-agentics (meta-agent, meta-prime, meta-prompt, meta-skill). (3) Running /library list to see catalog contents. (4) /library add meta-agent meta-prime meta-prompt meta-skill from
The library skill itself is 100% agent-first — there is no compiled code, no CLI binary. It is a SKILL.md plus a library.yaml plus a cookbook directory with one markdown file per command (add, use, push, list, search, sync). The skill instructs the agent on how to interpret the YAML and execute git operations.
[00:25:00] All right, remember the agentic path for all of us now is base agent, better agent, more agents, custom agents and then we start orchestrating things with our orchestrator agent and the orchestrator agent is a big big trend right now. Calling it a trend is frankly stupid. It’s a really really important conceptual idea for agentic engineering. Once you get to certain levels of scale, the only way to continue is to create a leader. Is to create a co-worker, is to create an orchestrator that can operate entire devices for you and entire systems for you, entire domains for you. And in order to really build that out and scale that and to reuse your grade a Gentics across all your devices, you’re going to
[00:26:00] want something like the library so that you can quickly organize all of your capabilities into one location. All right, so that’s all I’ve done here. This is the idea. I wanted to sit down and communicate with you today. This is the library meta skill. The skill to unlock and redistribute your private skills, agents, and prompts to help you maintain your advantage in the age of agents. You know where to find me every single Monday. Stay focused and keep building.