Every company needs killer Skills library. Not a folder in GitHub that 10% of the company knows how to use. A living library the whole company benefits from. The best deal review skill gets better every time a sales rep uses it. A great research skill gets discovered instead... of rebuilt 50 times. Creating a skill should be as easy as asking to create something useful from based on the context of your work. And the top skills (and skill creators) should rise to the top. Create, share, collaborate on, discover and understand usage of skills, organize them into databases by team or use case, then use them across any of your agents. Still early, but the idea is to make Notion the best home for your company’s collective AI skills. Made a quick demo (all available now)!show more

nah. we still have notion in our company (for now) but looking to get rid of it asap. just have a skills repo for your company + make simple html for said skills where people can see them. the agents shud be going through it. barely any human is gonna manually read what those skills do. will turn into graveyard for 99% of companies

Agent going thru skills and burying bad and duplicate skills! What would get you to stay?

we've had notion probably 5+ years and it was great for us pre-ai. i just dont know if an "everything" app is the right move for us anymore. for long time it was our central hub for everything. its like it does a lot but not quite what we need specific to our business (short term rental industry is my main business atm)

Wonder if you pair it back to just a few specific, high value use cases, rather than try everything. For example, just use it for self-updating knowledge base/docs, enterprise search across apps, meeting notes, and core task tracking with some agents to help triage (and ability to assign takes to Claude/chatgpt/cursor). For new customers, these are the 4 main use cases we recommend and help implement.

big final act @piamishra

Looks great and notion ui is beautiful for viewing skills. Is it possible to have them sync to local rather than download? What if you or agent want to update skill? Need to download, update locally and use notion mcp to rewrite all blocks back to location? Needing to press download skill feels like unnecessary friction

Coming very soon!

good stuff finally having a clean space to org my skills btw, nice ui update for the add comment text field

This is how using notion feels like. It has everything and nothing

any plans on making the skills library more usable within claude/codex environments? Something like packaging the latest skills from the repo into a plugin for use? Seems to only benefit me if I use notion agents currently, which are very credit intensive

+1 more to do but easy to add skills hosted in Notion to other agents

people store skills in their local folders, and should rightfully sync from there, not just hosted on the cloud

the next layer on top of this is a scoreboard. nobody runs one model on one harness. i run weekly golden checks across my skill library so i know where each skill holds up, per harness, per model. that's what lets me hand a job to a smaller model and trust it.

Need a way to directly point Claude/codex at these!

Easy!

Thanks! Would be great if it was a local file that syncs and Claude/codex/cursor could be pointed at so that I don’t have to download and reinstall after updates. Want living skills inside my brain!

+1. And on roadmap. We got you.

just use @memco_ai - much easier.

A living library for skills, needed this

this is amazing! hope to see a integration soon!

I've been using to manage my teams skills and track their usage (and also self improves based on usage)

Does Linear have this? @linear

smart

is built exactly for this. Self evolving skills

This is exactly what I am looking for

Chatting w you guys @runlayer

Great stuff!

Notion isn’t my human wiki — it’s the substrate my ~12 agents run on. SSOT page per agent, one DB as the agent queue, a separate one as the human queue, a daily context DB so sessions hand memory to each other. Humans read ~10% of it. The agents read all of it.

@NotionHQ @LironAvineri as per our lest convo

notion actually cooking with this one

Notion’s throwing up 100 shots and hoping something hits, but this might be it

@NotionHQ So Notion is now taking credit for merely naming a common notion use case? Is that like excel calling tic tac toe a new feature?

On this topic, there is where agents can learn new skills similar to how humans learn. I found that quite interesting.

sounds great in theory but I feel like if everybody uses the same skills you just neutralize creativity, also not everybody works the same way just give people tasks let them configure their own skills and judge the output not the configuration

watched skill libraries decay without evals and clear owners because usage alone teaches nothing

How does Notion Skill Library work with Claude Desktop Enterprise. Does the MCP allow for people to update skills in the library

This is dope! Reminds me of

a company with an agentic mind can’t rely on notion. they took away mcp capabilities and broke many users’ workflows for the sake of pushing them to a higher plan. so even in theory you are telling sth valuable, you are basing it on the wrong medium.

this is interesting -- any plans to have the skills DB auto sync with a Github repo? It seems this could be more friendly for non devs company wide but version history is useful for skills

Notion as a front-end is ok. GitHub or similar version control, CI/CD, PR reviews, security checks on commits, etc are all critical for skills as a primitive that get injected into an agent session.

@linear what say you

Running about 40 of these in house. Read skills compound like you describe. Write skills do not. One bad edit to a skill that files PRs propagates to everyone on the next run, so those need version pinning and a review step the read ones never need.

been thinking about this