skills CLI 1.7.0 installs agent skills straight from Notion pages

skills CLI adds Notion as an install source

Vercel has shipped version 1.7.0 of the skills CLI, which can now pull agent skills from Notion skills databases. According to the Vercel changelog, a Notion skill is a reusable agent capability authored as an ordinary Notion page: teams write, review and revise it in the workspace they already use, then install it into any agent the CLI supports. The entire flow works without a Git repository.

How installing works

The CLI gives teams two entry points. A browse command lists the skill packs shared with the person running it and installs all the skills contained in whichever packs they select. For individual items, the CLI accepts a page link directly: npx skills add <NOTION_PAGE_URL> fetches a single skill from its Notion URL.

Both commands authenticate through the Notion CLI, invoked as ntn. Setup involves installing that tool and running ntn login, which depends on a Notion personal access token. Vercel cautions that the workspace has to permit those tokens, so some organizations may need a settings change before the integration will function.

Permissions mirror page sharing

There is no separate access system to administer. The changelog explains that visibility follows Notion's page-level permissions: you only see the skills shared with you, which means deciding who can install a skill is identical to deciding who can view its page. Teams can therefore lean on the sharing conventions they already understand rather than defining a new policy layer for agent tooling.

A standard format underneath

The integration is built on Notion's new Agent Skills API, which presents skills stored in Notion as standard Agent Skills folders. Vercel emphasizes that because the format is the standard one, the same skill works in any agent capable of reading it. In effect, Notion serves as an authoring and distribution channel rather than a proprietary silo, and Vercel's suggested starting point is simply creating a Notion skill.

Why it matters

Distributing reusable agent tooling has generally assumed a Git repository, code review and repository-level access rules — workable for platform teams, heavier for everyone else. Hosting skills in Notion moves authoring, review and upkeep into software many organizations already use for documentation, and it borrows Notion's sharing model instead of adding another permissions system to maintain.

The portability angle matters as much as the convenience. Because Notion serves the standard Agent Skills folder format, a page written once becomes installable across every compatible agent, turning internal documentation into a plausible distribution channel for agent capabilities.

The trade-off worth noting is authentication: the flow runs on personal access tokens, which workspaces must explicitly allow. Teams with stricter token policies should verify that setting before adopting the workflow. Taken together, the release lowers the cost of converting institutional knowledge — which already lives in Notion at most companies — into tooling their agents can actually use.