Botdocs is the agent-skill registry for teams. Author a skill once, share it with your team, and every teammate gets it on every agent — Claude, Cursor, Codex, ChatGPT.
I’ve been a software engineer for over a decade. I tinker for a living and for fun — there’s always a new side project, a new agent, a new workflow I’m pushing a little further than the one before it.
Last year I was setting up an autonomous agent for one of my side businesses. I’d spent months refining a set of skills on my laptop — code review, debugging, deployment, the rituals you only stop noticing once they’re sharp. To get the agent useful, I copy-pasted those skills into a second environment. Then I spun up a third agent and did it again.
And it hit me: every time I refined one of these skills — which I’d do constantly, because that’s how skills get good — I’d have to propagate the update by hand to every machine and every agent that used it. Forever.
I don’t like maintenance work. I like to push forward, learn the next thing, ship something new. The thought of spending the next year of side projects fighting a copy-paste treadmill was unacceptable.
So I bought botdocs.ai. And then I sat on it. The domain lived in my registrar for a year before I wrote a line of code — I had the conviction that this would matter, but I wanted to be sure I wasn’t solving a problem only I had. So I watched. I scrolled X. I lurked on Reddit. Three or four threads later — engineers asking the same question, nobody offering a real answer — I knew. I started building.
Cursor, Claude, ChatGPT, Codex — and whatever launches next month — every one of them is shipping fast, competing on price and quality, and asking you to build your workflow inside their walls. That’s reasonable for them. It’s risky for you.
The waters are still blue. The winners haven’t emerged. Locking your skills, your workflows, and your team’s muscle memory into a single provider today is locking yourself into a maintenance burden tomorrow — and a switching cost when the wave changes. Which it will.
Botdocs is the portable layer above them. A skill you author once, install everywhere, and keep current as the underlying agents evolve. So you can ride whichever wave is working best for you, this month, without rebuilding from scratch.
The right thing to bet on isn’t a provider. It’s a portable layer above them.
Now picture three teammates on three different platforms. One works in Cursor. Another lives in Claude Code. A third is on Codex. You write your team’s code-review style up as a skill and ship it around — pin it in Slack, drop a zip in a Drive folder, email a markdown file to the new hire. Plenty of teams work this way today. It works for about a week.
Then the skill evolves. The senior engineer sharpens the wording. Someone catches an edge case in the debugging ritual. The “always check this before shipping” list grows a new bullet. And now you’re back at the start — re-pinning the new version, re-emailing the new zip, hoping everyone notices, hoping nobody is still running last month’s copy on a build that ships tomorrow.
The first share is the easy part. Keeping everyone on the latest and greatest as the skill keeps improving is the part nobody has solved. Without it, the shared muscle memory that makes a team faster than the sum of its individuals drifts — across people, across providers, across machines, with nobody minding the gap.
Botdocs solves that. Publish a skill to your team and it propagates. A new hire signs in and gets every skill on day one. When you refine the skill — and you will, constantly — a single sync rolls the update out to every teammate’s machine and every agent they run. The unit of distribution is the team, not the machine. The latest version is the version everyone has.
The unit of distribution for agents is the team, not the file. Skills should propagate the way commit messages do — automatically, for everyone with access.
Write a skill in your preferred ecosystem (Claude Code, Cursor, Codex, ChatGPT). The CLI compiles the rest with your own LLM key — your content never touches our servers for inference.
Publish to your team and the skill propagates. New hires get it on day one. Updates land everywhere with a single sync. The team is the unit of distribution, not the individual machine.
Same skill, every agent. Cursor rule on Monday, Claude Code command on Tuesday, Codex agent on Wednesday — all from one source of truth. No more rewriting the same prompt four times.
“It used to be a late-night project to roll out a refined skill across all my agents. Now it’s a single command — and I do it ten times more often. That’s the whole point.”
Browse and review skills in your browser. Install, sync, and publish from your terminal. Every skill exposes a manifest and raw file access over a public REST API.
Find, install, and sync skills onto every machine on your team. One install drops into Claude, Cursor, Codex, or ChatGPT, depending on what you have.
botdocs install @teamco/eng-skillsPublic endpoints back everything. Every skill exposes a manifest and raw file access.
curl -sL https://botdocs.ai/@teamco/eng-skills/manifestSkills are versioned, installable artifacts that live alongside your agent — not snippets you paste into a chat box.
Skills are markdown plus light metadata. There’s no code to host, no build step, no runtime. Just the instructions your agents need.
We don’t run LLMs and we don’t generate skills. We host the registry. You bring the agent — and your own model key when authoring multi-ecosystem skills.
Right now Botdocs is one engineer’s solution to one engineer’s problem, shipped in the open because the engineer is pretty sure it’s everyone’s problem too — whether you’re flying solo, leading a team, or managing a fleet of agents. If it solves yours, that’s the whole point.
Free to browse. Free to publish. Author once, ship to every agent your team uses.