FAQ

• Can I contribute a skill or a fix?

  Issues are welcome on the public repository. The most useful kind is a case where a skill should have loaded and stayed quiet. That is a description problem, and it takes someone hitting it to find.

  Pull requests are limited to collaborators for now, so an issue is the way in. Everything here is Apache-2.0. If you want the change in your own hands today, fork it and adapt it (the intended use anyway).

• Do these work with agents other than Claude Code?

  Yes. They follow the Agent Skills specification, which Codex CLI, Cursor, VS Code, GitHub Copilot, Gemini CLI and many other tools implement. A skill directory installs into any of them.

  npx @kensio/skills add <skill-name>

  That copies the directory into .agents/skills/, the path those agents read. Pass --agent claude for .claude/skills/, --agent copilot for .github/skills/, or --to <dir> for anywhere else. The installing skills page lists the directory each agent looks in.

  The Claude Code plugin packaging is still there and still worth using where it applies, because a marketplace install stays updatable in place.

• 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. Take a skill, change the parts that clash with the way your team works, and keep the result.

• How do I install these skills?

  The short way, for any agent:

  npx @kensio/skills add <skill-name>

  That puts the skill directory in .agents/skills/, where Codex, Cursor, VS Code and Gemini CLI look for one. Claude Code takes the same skills from a marketplace:

  claude plugin marketplace add KensioSoftware/kensio.ai
  claude plugin install <skill-name>@kensio

  Each skill is also an npm package under the @kensio scope, and every release carries zips for a machine with no npm reach. Full instructions are on the installing skills page.

• How do updates work?

  Explicitly, whichever way you installed. Nothing here updates itself.

  A skill you copied in is a directory you own. Replace it when you want the new version:

  npx @kensio/skills add <skill-name> --force

  Claude Code notices a new release only when a plugin’s version changes:

  claude plugin update <skill-name>@kensio

  The version a skill carries is in metadata.version in its SKILL.md, so a directory sitting in .agents/skills/ still says which release it came from.

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

  A skill loads on the strength of its description alone. When one stays quiet, the likeliest reason is a mismatch between the way you phrased the request and the situations that description names. The install is rarely the problem.

  Check the skill’s page on this site, under When it loads. That box prints the description in full, written as a list of the concrete circumstances the skill applies to. If your case belongs in that list and is missing from it, that is a bug worth reporting.

• Installer, marketplace, npm or zip?

  The installer, unless you have a reason not to. npx @kensio/skills add <skill-name> works for every agent, and it is a directory copy you can inspect.

  The Claude Code marketplace is worth the extra step if Claude Code is what you use, because claude plugin update keeps the skills 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 zips on each release cover a machine with neither git nor npm reach.

  The content is identical in all four. What differs is who puts it where an agent will find it.

• What is an agent skill?

  A skill is a packaged set of instructions an agent loads when the task at hand matches its description. It is a directory holding a SKILL.md (plain Markdown with a small frontmatter block) plus whatever supporting files it needs.

  The format is the Agent Skills specification, which Claude Code, Codex CLI, Cursor, GitHub Copilot, Gemini CLI and a long list of other tools read.

  You do not invoke a skill by name. The agent decides to load it from the description. That wording matters more than anything else in the file.

• Which directory does a skill go in?

  .agents/skills/<skill-name>/ in your project, for most agents. Codex CLI, Cursor, VS Code and Gemini CLI all read it, and ~/.agents/skills/ is the same thing for every project at once.

  Two agents have their own as well. Claude Code reads .claude/skills/, and VS Code with Copilot also reads .github/skills/ and ~/.copilot/skills/.

  The specification settles what a skill directory contains and leaves discovery to each implementation, so check your agent’s own documentation if it is not one of those. The installing skills page has the full table.

No questions match your search.