FAQ

FAQ

  • Can I contribute a skill or a fix?

    Yes. Issues and pull requests are welcome on the public repository.

    The writing skills page covers the conventions we hold to, which is the fastest way to get a contribution merged without a round of review notes about scope and triggering.

  • Do these work with agents other than Claude Code?

    The skills are plain Markdown, so nothing stops another tool reading them. But the frontmatter format, the loading behaviour and the plugin packaging are Claude Code’s, and that is what these are built and tested against.

    If you are using something else, the instructions themselves will likely still be useful — you will just be responsible for getting them in front of your agent.

  • How are the skills licensed?

    Apache-2.0, all of them. The source lives in a public repository at KensioSoftware/kensio.ai.

    Forking one and adapting it to your own conventions is the intended use. Nothing here is meant to be used unchanged if unchanged does not suit you.

  • How do I install these skills?

    Two ways. Add the marketplace once and install what you want from it:

    Terminal window
    claude plugin marketplace add KensioSoftware/kensio.ai
    claude plugin install hello-world@kensio

    Or install a single skill as an npm package under the @kensio scope. Full instructions are on the installing skills page.

  • How do updates work?

    Explicitly. Claude Code notices a new release only when a plugin’s version changes, and it will not upgrade on its own:

    Terminal window
    claude plugin update hello-world@kensio

    Each plugin is versioned independently, so updating one never quietly moves another.

  • I installed a skill but it never seems to load. Why?

    A skill loads on the strength of its description alone. If it is not loading, the likeliest reason is that what you are asking for does not match the situations that description names — not that the install failed.

    Check the skill’s page on this site: the description is printed there in full, and it is written as a list of the concrete circumstances the skill applies to. If your case genuinely belongs in that list and is not there, that is a bug worth reporting.

  • Should I use the marketplace or npm?

    The marketplace, unless you have a specific reason not to. It makes every skill available, and claude plugin update keeps them current in place.

    npm is there for the case where you want exactly one skill pinned in a repository’s lockfile and reviewed like any other dependency. The content is identical; what differs is who is responsible for putting it where Claude Code will find it.

  • What is a Claude Code skill?

    A skill is a packaged set of instructions that Claude Code loads when the task at hand matches its description. It is plain Markdown — a SKILL.md file with a small frontmatter block — plus whatever supporting files it needs.

    You do not invoke a skill by name. The agent decides to load it based on its description, which is why the wording of that description matters more than anything else in the file.