Skills CLI now supports Notion hosted skills
The skills CLI now accepts Notion-hosted skills databases as an install source, allowing teams to author, review, and manage reusable agent skills directly in their Notion workspace without requiring a Git repository. Access and installation permissions follow Notion's built-in page sharing model.
adds as an install source for agent skills .skills@1.7.0Notion skills databases
Notion skills are reusable agent skills written as Notion pages. Teams author, review, and update them in the workspace they already use, then install them into any agent the skills CLI supports. No Git repository required.
To browse your Notion workspace's skills, run:
The CLI lists the skill packs shared with you and installs every skill in the packs you select.
To install a single skill, pass its Notion page URL:
Both commands use the Notion CLI () to authenticate. To set it up:ntn
requires a Notion personal access token, so your workspace must allow them.ntn login
Access follows Notion's page permissions. You only see skills shared with you, so controlling who can install a skill is the same as controlling who can view the page.
This integration is built on Notion's new Agent Skills API, which exposes skills stored in Notion as standard Agent Skills folders. Because the format is standard, the same skills work in any agent that reads them.
Get started by .creating a Notion skill
Source: original entry ↗
More from Vercel
Follow Vercel to get its new changes in your feed and email digest.
Muse Wonder now available on AI Gateway
Meta's Muse Wonder model is now accessible through Vercel's AI Gateway, supporting coding tasks, multi-step agent workflows, and computer use with a 1M-token context window. Users can access the model via a single API key without creating a separate Meta account and use it for text, image, PDF processing, tool calling, and structured outputs.
Agents can now buy domains with the Vercel CLI
Vercel CLI now enables agents to discover, check availability, and initiate domain purchases through structured commands, with purchase confirmation remaining under user control via interactive terminal or dashboard approval.
New Pro teams default to 30-day deployment retention
Pro teams now default to a 30-day deployment retention period to balance keeping recent history available while reducing storage costs. You can configure a longer retention period in team settings if needed.