Installing skills

Installing skills

There are two ways to get a Kensio skill into a project. The marketplace is the one to reach for: it makes every skill available and keeps them updatable in place. npm is there for the case where you want exactly one skill vendored into a repository alongside its other dependencies.

Recommended

Install from the marketplace

Add the marketplace

Once per machine. Claude Code remembers it across projects and sessions.

Add the Kensio marketplace
/plugin marketplace add KensioSoftware/kensio.ai

Install the skills you want

Every skill on the skills page lists its own install command. The @kensio suffix names the marketplace, not the npm scope.

Install a skill
/plugin install hello-world@kensio

Check it loaded

The skill is now available to the session, and Claude Code will load it when a task matches its description. You do not invoke it by name.

Updates are explicit

Claude Code only notices a new release when a plugin's version changes, and it will not upgrade on its own. Pick up a release with claude plugin update hello-world@kensio.

Install from npm

Each skill is also published as a package under the @kensio scope. This suits a repository that wants the skill pinned in its lockfile and reviewed like any other dependency.

Install a single skill
npm install @kensio/hello-world

The package is the same content

The npm package ships the same SKILL.md the marketplace does. What differs is who is responsible for putting it where Claude Code will find it - with npm, that is you.

Licensing

Every skill is Apache-2.0. Forking one and changing the parts that do not match your conventions is the intended use. The source for all of them lives in the public repository.