notion-skills-registry

Use Notion as a versioned skill registry for OpenCode, Claude Code, and other AI agent workflows.

Instead of copying prompts across repos or stuffing everything into a global skills folder, this project lets you keep skills in one centralized Notion workspace and install them into projects as local wrappers.

Think of it like a lightweight package registry for AI skills, powered by Notion MCP.

Managing AI skills across projects gets messy fast:

• prompts get duplicated across repos
• global skills folders become cluttered
• teams lose track of the latest approved version
• sharing reliable workflows turns into copy-paste chaos
• updating a skill in one place does not propagate cleanly

Notion Skills Registry solves that by giving you:

• one source of truth for your skills
• clear versioning such as content-research-writer@v1 and content-research-writer@v2
• approved releases that projects can safely install
• project-level isolation, so each repo keeps only the skills it needs
• a simple update flow for rolling out newer approved versions

At a high level:

1. You keep the real skill content in Notion.
2. Each skill version lives on its own Notion page.
3. A page called Skill Versions acts as the registry index.
4. You install the management skills from SETUP.md.
5. In each repo, you run /notion-init once.
6. You install skills with /notion-install <slug> or /notion-install <slug@version>.
7. The repo gets a local wrapper skill plus a local manifest.
8. Later, you run /notion-check-updates and /notion-update to stay in sync.

The important idea is simple:

• Notion stores the source skill content
• Each repo stores only a small local wrapper and manifest

This project provides four management skills:

• notion-init
• notion-install
• notion-update
• notion-check-updates

These management skills let a