Built with Astro, hosted on Amazon CloudFront. Domain registered in 2026.
kensio.ai is built with Astro, hosted on Amazon CloudFront.
| Technology | Version | First seen |
|---|---|---|
| JavaScript Frameworks & Libraries1 | ||
| – | 9 Nov 2026 | |
| Frontend Build Tools & CSS1 | ||
| 4.3.3 | 9 Nov 2026 | |
| CDN & Hosting3 | ||
| – | 9 Nov 2026 | |
| Accessibility1 | ||
| – | 9 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 9 Nov 2026 | |
| Translation & Localization1 | ||
| – | 9 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
ns-1088.awsdns-08.orgns-184.awsdns-23.comns-873.awsdns-45.netns-1590.awsdns-06.co.ukUser-agent: * Content-signal: search=yes, ai-train=yes Allow: / Sitemap: https://kensio.ai/sitemap-index.xml
# kensio.ai - open-source agent skills > Kensio Software publishes agent skills — packaged instructions that give a coding agent a repeatable way to do a particular kind of work. They follow the Agent Skills specification, so Claude Code, Codex, Cursor, Copilot, Gemini CLI and anything else that reads SKILL.md can use them. They install with npx @kensio/skills, from the Claude Code plugin marketplace, from npm under the @kensio scope, or by copying a directory. This site lists what is available and how to install it. Last updated on: 2026-09-05T10:43:04.649Z ## Languages - [English](/): default ## Pages - [kensio.ai - open-source agent skills](/): Agent skills from Kensio Software. Each one is a packaged set of instructions an agent loads when the task calls for it. Apache-2.0, and installable into Claude Code, Codex, Cursor, Copilot or anything else that reads SKILL.md. - [Installing skills](/docs): Copy a skill into any agent, add the marketplace to Claude Code, or install one as an npm package. - [Writing skills](/docs/writing-skills): How the skills published here are structured, and what makes one trigger reliably. - [Skills](/skills): Every agent skill Kensio publishes, what each one is for, and how to install it. - [DynamoDB single table](/skills/dynamodb-single-table): Data modelling for Amazon DynamoDB, starting from one table. - [GitHub issue drafting](/skills/github-issue-drafting): A way of drafting GitHub issues that checks every claim against the repository first. - [Isolated testing style](/skills/isolated-testing-style): An opinionated testing style built on simulated collaborators and randomised data. - [Pangram check](/skills/pangram-check): Check finished writing against the Pangram AI-text detector. - [Part factory test data](/skills/part-factory-test-data): How to build typed test data with @kensio/part-factory factories. - [Skill template](/skills/skill-template): A copy-and-edit starting point for a new agent skill. - [Technical prose style](/skills/technical-prose-style): A measured prose style for documentation, with a checker calibrated on human technical writing. - [Yulin AWS simulation](/skills/yulin-aws-simulation): How to test AWS code well with the @kensio/yulin in-process simulator. ## FAQ - [Can I contribute a skill or a fix?](/faq#can-i-contribute): Issues are welcome on the [public repository](https://github.com/KensioSoftware/kensio.ai). 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?](/faq#do-they-work-with-other-agents): Yes. They follow the [Agent Skills specification](https://agentskills.io/specification), which Codex CLI, Cursor, VS Code, GitHub Copilot, Gemini CLI and many other tools implement. A skill directory installs into any of them. ```bash 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](/docs) 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?](/faq#how-are-they-licensed): Apache-2.0, all of them. The source lives in a public repository at [KensioSoftware/kensio.ai](https://github.com/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?](/faq#how-do-i-install-them): The short way, for any agent: ```bash 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: ```bash 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](/docs) page. - [How do updates work?](/faq#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: ```bash npx @kensio/skills add <skill-name> --force ``` Claude Code notices a new release only when a plugin's `version` changes: ```bash 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. - [Installer, marketplace, npm or zip?](/faq#marketplace-or-npm): 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](https://github.com/KensioSoftware/kensio.ai/releases) 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?](/faq#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](https://agentskills.io/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?](/faq#where-do-skills-go): `.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](https://agentskills.io/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](/docs) page has the full table. - [I installed a skill but it never seems to load. Why?](/faq#why-is-the-skill-not-loading): 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.
| – |
| 9 Nov 2026 |
| – | 9 Nov 2026 |