This is a submission for the Notion MCP Challenge
What I Built
I built Notion Skills Registry, a lightweight package-registry-style sys...
For further actions, you may consider blocking this person and/or reporting abuse
Template is submitted to the marketplace:
Will update the link when approved
I've been looking for that!
Happy you find it useful! Let me know how it goes for you!
Appreciate your feedback.
Same here. I use notion everyday, and started using claude code few months, and skills are overwhelming, this makes it easier! will try out tonight. if everything like on the video, then it's amazing! let me try though...
This is a fantastic pattern for managing agentic 'bloat.' I really appreciate the focus on turning a Notion workspace into a versioned registry. It moves Notion from a 'notes app' to a piece of programmable infrastructure.
I've been exploring a similar theme of Technical Governance for my submission (Archival Intelligence), but from the forensic side of high-value assets. It's interesting to see how we both landed on using Notion as a 'Source of Truth' to prevent AI hallucinations. Yours for skill distribution, mine for physical provenance.
Great to see such a hardened implementation of the MCP! Good luck with the challenge.
Thanks for the feedback :)
If you see any path this could be improved, please let me know!
This is actually a solid idea — treating AI skills like versioned packages instead of messy prompt files just makes sense. Using Notion as the source of truth + MCP for distribution is a clean combo.
Curious though: how do you handle breaking changes across teams when a “latest approved” version isn’t backward compatible? That’s where things usually get painful.
There are no backward compatibility issues, really.
Agents' skills are usually not long-running processes; it's one-off tasks that you ask AI to do.
If, for any reason, the updated skill changes the folder structure or removes files, you can include a migration guide in the skill so that, when you or a team member updates to the new version, the AI agent receives a migration task within the same /notion-update process.
UPDATE:
This Template now available on Notion Marketplace:
notion.com/templates/skills-regist...
how are you handling version conflicts when two different agents need different versions of the same skill registered in notion, does the registry track that or is it first-write-wins?
there are really no "version conflicts" since:
1) Every project/repo can have it's own version installed
2) It's still text-based and AI agent processed rather than piece of software that needs to be 100% accurate, AI agents will understand your plain language and some imperfections/extra tasks you give like
Will still work :)
But I believe this is less than 1% usecases when you need multiple versions of skill in the same project in different agent sessions.
That's what I needed and was looking for! Thanks!