Build Once, Deploy Everywhere: Turn Notion Skills into an AI Agent Marketplace

Notion AI is powerful and gives you access to all the leading models, but for many companies it isn't the only AI agent in the picture. You might have developers on the team working in Claude Code or Codex, other users running scheduled tasks in Claude Cowork, or folks using newer agent tools like Grok Bot. All of these benefit in the same way from AI skills, the reusable instructions that teach an agent how your team works, but having to recreate your skills for every tool your team uses can be a huge pain.

Notion has now solved that problem for us with the the new Agent Skills API. In a nutshell, it allows you to sync a Notion database of skills into a GitHub repository, which can then in turn serve as a skills marketplace for Claude, ChatGPT, or other AI tools.

Here's how it works, and how to set up the same thing for your team.

The Skills API is a set of endpoints for loading skills from Notion into spec-compliant file formats that other AI tools can read. In practice, your skills stay ordinary Notion pages, and the API serves them to other tools in the format those tools need: a folder containing an instruction file, a manifest, and any supporting assets. Any tool that reads skills from a GitHub repository can therefore consume your Notion skills, because the output follows the open skills spec rather than a Notion-specific format.

The API documentation is live on Notion's developer site, along with an open-source sample repo for syncing skills into GitHub. That sample repo helped me get our skills repo set up and connected to Claude in under an hour.

Until now, running skills across several agents meant creating and maintaining copies in each tool, e.g., one version for Notion AI, another for Claude, etc. I took the time to do this for some of my more heavily used skills, but definitely not for all of them, and I was absolutely guilty of making updates to a skill in one tool and forgetting to update its counterpart in the other.

The standard fix is to store skills in a GitHub repository, since most agent tools can be configured to sync in skills from there. That's fine for developers, and vibe coders who are used to working in GitHub by now, but it’s not great for everyone else. (I myself admit to only understanding ~40% of how Git works, even after finishing a 400-page book about it the other day).

One of my clients is currently helping subject-matter experts across the business build company-wide skills for Claude, which in practice means talking non-developers into editing markdown in GitHub. It’s working, but we could scale skill-building across the company much more rapidly if the process wasn’t dependent on training everyone on GitHub.

With the Agent Skills API, you can have the arrangement in reverse: keep every skill in Notion, where the whole team already works and where permissions, comments and version history come for free, and leave the technical plumbing in the background where most users don’t have to worry about it.

Our skills live in a Skills database in Notion. Each skill is a single page with a description, any supporting files, and Notion's version history tracking every change. That database is the single source of truth; we never edit skills anywhere else.

A small script running hourly in a GitHub Action pulls the skills through the API and writes them into a GitHub repository (ours is work-flowers/synced-skills). Each skill lands as its own folder, in exactly the format agent tools expect. Whenever someone edits a skill page in Notion, the next sync pushes the updated version to the repo. If you point a coding agent at Notion's starter kit, you can have this basic loop running in an afternoon.

Once your skills are synced into the GitHub repo, getting them into Claude is easy. On a Team or Enterprise plan, you simply go into Organization settings → Plugins & skills, and from there you can select your GitHub repo to serve as a plugin marketplace.

The skills will be be organised into plugins, which you can think of as folders. The Agent Skills API assigns the plugins based on the Tags property of your skills database in Notion, and any skills that don’t have that property filled out will appear in Claude as a stand-alone plugin with one skill inside it.

The same repository can serve as a skills source for other agents, including ChatGPT and Grok Bot, according to Notion's announcement. I've only tried it in Claude myself, so treat that part as reported rather than tested. Either way, the repo gives you a single distribution layer that any spec-compliant agent can read from.

The setup works because it lets Notion serve as the user-friendly, collaborative front end where technical and non-technical teammates alike write and refine skills, while also leveraging GitHub as the back end that ports the same skills to your other AI agents.

It also removes the lock-in worry. The AI market is evolving faster than any phase of technology I’ve seen before. Many companies are now considerations migrations to cheaper, open-weight models, or switching between the top-tier model providers as they leap frog each other in the AI arms race. Your skills library is one of the critical assets that should move with you.

Teams building their operating system in Notion can start a free trial through our partner link. (Referral link; we earn a small commission if you sign up.)

If you'd like help turning the way your team works into a skills library that serves every AI tool you use, book a discovery call or drop us a message.

Book a discovery call Message us on WhatsApp