Notion launched the Skills API on September 17, a set of endpoints that exports agent instructions written inside Notion into the standard file format that Claude, ChatGPT, and other agent tools already read. The company also opened a starter kit that syncs those instructions into a GitHub repository, and confirmed that Vercel’s open-source skills CLI now installs skills directly from a Notion page.
The problem Notion is targeting is access, not authoring. Most teams that write reusable agent instructions (“skills,” in the vocabulary Anthropic popularized with Claude) still keep them in a GitHub repo, because that is where engineering-built agent tooling expects to find them. Marketing, sales, and finance staff rarely have GitHub accounts and, per Notion, often struggle to edit files in a code repository even when they do.
Notion’s answer is to let anyone edit a skill the same way they edit any other Notion page, store the supporting files a skill needs in a database alongside it, and let the Skills API translate that page into the plain-file format an agent expects. A GitHub sync then keeps engineering’s copy current without forcing non-technical staff to touch a repository. Notion published the sync tooling as an open-source starter kit rather than a hosted product, so an internal IT team runs and owns it.
“Notion’s skill databases help Pearmill provide the ergonomics for a non-technical team to easily share, collaborate, and manage skills across the whole organization,” said Nima Gardideh, the company’s CEO, adding that his team now shares new skills “multiple times a week” across marketing, design, and operations. That figure comes from a customer Notion chose to quote in its own launch post, not from an independent usage audit, and Notion has not published aggregate numbers on how many teams have adopted the API since launch.
Vercel’s integration is the more concrete distribution proof point. Its skills CLI, one of the more widely used tools for installing agent skills, now supports npx skills add <notion url> for a single page and npx skills add notion to pull an entire workspace of skills at once. Because the Skills API already returns standards-compliant files, Vercel’s tool did not need to write any Notion-specific parsing to support it, according to Notion.
Hillary Helmling, who works in product operations at the fintech company Candidly, said keeping skills in Notion “strengthens our team’s awareness of what’s accessible” when staff work with Claude. Josh Reid, a product engineer at the marketing agency Brainlabs, made a sharper version of the same point: not everyone writing a skill is a developer, so the skill needs to live somewhere the whole team already collaborates, with GitHub as a secondary, synced copy rather than the primary home.
The bet underneath all of this is that “skill” becomes a portable unit that outlives any single agent vendor, the way a spreadsheet outlives any single office suite. If Notion’s export format holds up across Claude, ChatGPT, Grok, and whatever agent runtime ships next, workplace teams gain a reason to standardize their internal knowledge on Notion regardless of which chatbot happens to sit on top of it. That is a stronger lock-in argument for Notion than for any one AI lab, and it is worth watching whether OpenAI or Anthropic build a competing import path of their own rather than simply consuming Notion’s export.
Teams already storing prompts or playbooks in a GitHub repo should test the Skills API’s export against their existing agent stack before migrating anything, since Notion’s own case studies so far describe usage in weeks, not a full quarter of production load.
Notion, “A skills library for every agent,” published September 17, 2026.
