By submitting this form, you agree to our 

Answer twenty questions about your artifact and supply chain practices. Get a custom report card showing your maturity score against key regulatory and compliance frameworks.

Artifact Security Maturity Assessment

Someone on your team writes a skill that automates a tedious task. It works well, so they share it in Slack. Within a few weeks, dozens of people have installed a copy of it, and their agents run it. Which version is current? Who wrote it? Has anyone reviewed it?

This is happening well beyond engineering. Analysts, operations staff, and other citizen developers now write skills to automate their own work, and useful tools spread faster than anyone can track. If that sounds like shadow IT in the early days of cloud computing, it is the same pattern with a new kind of artifact.

manage agent skills and Claude plugins as artifact types in Cloudsmith

, alongside your packages and containers. Host the skills your teams write so everyone can discover them, bring in public ones from the GitHub repositories you trust, and block the skills you don't want.

Skills are spreading faster than anyone can govern

Skills spread because they work. Teams share them by email, Slack, and Google Drive, and pull others from Git repositories, community catalogs, and standalone registries. Each source has its own way to publish, version, and control access, so many teams can’t say which skills their agents pull, or which versions. It’s the early days of cloud again: useful tools spread team by team, and IT often spends years catching up on what’s running where.

A skill is a bundle of instructions and resources that an agent loads for a specific job, such as following your team's review process. It's a 

 file plus the scripts, references, and templates it needs. A Claude plugin bundles skills so teams can install them as one unit.

That makes skills a software supply chain question. Agents act on those instructions and run those scripts, sometimes with access to sensitive systems and data. A skill pulled from a public source carries the same unknowns as other third-party open source packages: you don't know who wrote it, what changed, or whether anyone reviewed it.

A skill that is malicious, changed, or simply wrong can cause an agent to leak data, run harmful commands, or take actions no one intended, using the access the agent already has.

A registry is the natural control plane for skills

A skill is a bundle of files, so a registry can treat it like a package and give it a version like any other. Registries exist to manage packages, so they're the natural place to manage skills. The right registry for skills should:

Host the skills your teams write, versioned, alongside packages, containers, and other artifacts

Bring in public skills from sources you trust

Let you control which skills and versions your teams can pull

Show which skills and versions get pulled

Cloudsmith supports more than 30 artifact formats, so skills sit in the same system of record as packages and containers.

Cloudsmith gives developers approved skills in the repositories they already use, while giving security the visibility and control to decide which skills agents can use. Four capabilities make that work.

Host skills and plugins as a package type

Host versioned skills and Claude plugins in a governed control plane, right next to packages and containers. Each release gets a semantic version or a git commit SHA, plus a SHA-256 checksum. Keep your Cloudsmith repositories private, or share them publicly. Developers discover skills in the same repositories as every other artifact.

GitHub is where we built first, because it's the source our customers told us they use. Add a GitHub repository as an upstream with a token, and Cloudsmith caches its skills and plugins so your teams pull from the sources you chose. Private repositories work too, as long as the token has access.

Through Cloudsmith, your teams only get skills from the publishers you add to your GitHub upstreams. Add deny rules to block a specific skill or version by name without giving up the rest of the repository. A blocked skill doesn't show up when developers pull or list, and they get a "nothing found" error, just like other formats.

Skills use the same audit logging as every other format in Cloudsmith, so security can see which skills and versions get pulled, in the same trail as the rest of your software supply chain.

Keep teams moving while you govern skills

Governance works when developers keep using it, so we kept the workflow familiar. Publish a skill once to your Cloudsmith repository, and every team can discover and use the same version. Upload through the web app or the API, or use the CLI. Repository privileges decide who can publish. Security chooses the sources and rules once. Teams use approved skills without waiting on sign-off for each one.

Your Cloudsmith repository also works as a Claude Code plugin marketplace. Developers add it once, then install plugins right in their session with 

Platform engineering controls which skills teams use. Security extends software supply chain governance to agent skills. Developers publish once and discover what their teams have already published. And citizen developers can upload a skill in the web app.

Skills deserve the same management as every other artifact

Early access is open now. Add a GitHub upstream, check out the 

, read the documentation, and start hosting and pulling skills.

This is where we start with AI artifacts, and we'll build from here. We're beginning with Claude Code. Skills belong in a universal artifact management platform, alongside your packages and containers, with the same policies and the same audit trail. See how 

Extending supply chain governance to AI artifacts

Cloudsmith Blog

Give your agent skills a trusted control plane