Nufar Gaspar

And you can think about it the following.

You can standardize the way work gets done.

You can get a lot of the work done autonomously or to some extent, and you can bundle that also with organizational knowledge.

So everything can be bundled into a single portable artifact that both the humans can read and new employees can onboard using that, as well as

the agentic tools that will be using them and doing the work for you.

So what I've seen happening in some organizations, they do skill hackathon where they create skills for their relevant teams.

They are maintaining skills in shared libraries like they would maintain code.

They make sure the skills are having clear ownership and use across various people.

And those organizations are seeing massive uplift with the quality and results that they're getting.

And the ones that are still not there, their people are kind of reinventing the wheel every time that they have a conversation with AI or even if they create skills just for themselves.

Eventually, and we're already seeing that with the Cloud Cowork, most organizations will have the set of plugins.

So in Cloud Cowork, we're seeing plugins for specific professions, but you can create a plugin which is comprised of

Typically skills and connections and perhaps some context for each and every department or each and every group in your organization.

And all of a sudden, everybody enjoys the same worldview and the same goodness.

So to be a little bit more prescriptive here, what I would recommend that you do at the org level, you will start with discovery, running work audits or understanding where people work.

do repeating work or where people are not getting optimal value from AI and where there are wishlists that are not being covered.

So you'll have a list of opportunities to create skill.

And then you will curate them and build skills using the best possible methods, maybe with Claude's skill creator or just some of the best practices that we discussed here.

I then want to encourage you to do a lot of validation, especially if those are going to be shared across many people.

Then perhaps the person who created the skill will replace with another person who created another skill and they will stress test each other.