@kensio/skill-template 1.3.0

package/.claude-plugin/plugin.json

@@ -0,0 +1,14 @@
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "skill-template",
+  "version": "1.3.0",
+  "description": "A copy-and-edit starting point for writing a new Claude Code skill, covering SKILL.md frontmatter, description wording, and progressive disclosure.",
+  "author": {
+    "name": "Kensio Software",
+    "email": "hugh@kensiosoftware.co.uk"
+  },
+  "homepage": "https://kensio.ai",
+  "repository": "https://github.com/KensioSoftware/kensio.ai",
+  "license": "Apache-2.0",
+  "keywords": ["example", "template", "authoring"]
+}

package/README.md

@@ -0,0 +1,14 @@
+# @kensio/skill-template
+
+A copy-and-edit starting point for writing a new Claude Code skill: the folder layout, `SKILL.md`
+frontmatter, how to word a description so the skill actually triggers, and how to release a version
+bump.
+
+```
+/plugin marketplace add KensioSoftware/kensio.ai
+/plugin install skill-template@kensio
+```
+
+Part of [kensio.ai](https://github.com/KensioSoftware/kensio.ai). Licensed under the Apache License
+2.0 — see the [LICENSE](https://github.com/KensioSoftware/kensio.ai/blob/main/LICENSE) in the
+repository root.

package/package.json

@@ -0,0 +1,28 @@
+{
+  "name": "@kensio/skill-template",
+  "version": "1.3.0",
+  "description": "A copy-and-edit starting point for writing a new Claude Code skill, covering SKILL.md frontmatter, description wording, and progressive disclosure.",
+  "keywords": [
+    "claude",
+    "claude-code",
+    "claude-code-plugin",
+    "kensio",
+    "skill"
+  ],
+  "homepage": "https://kensio.ai",
+  "license": "Apache-2.0",
+  "author": "Kensio Software <hugh@kensiosoftware.co.uk>",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/KensioSoftware/kensio.ai.git",
+    "directory": "plugins/skill-template"
+  },
+  "files": [
+    ".claude-plugin",
+    "skills",
+    "README.md"
+  ],
+  "publishConfig": {
+    "access": "public"
+  }
+}

package/skills/skill-template/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: skill-template
+description: Scaffold a new Claude Code skill in this repo — creates the plugin folder, package.json, plugin.json and SKILL.md, and registers it in the marketplace. Use when the user asks to "add a new skill", "create a skill", or "start a new plugin" in the kensio.ai repo.
+---
+
+# Skill Template
+
+A starting point for adding a new skill to this repo. Copy the structure below, replace the
+placeholders, then run the validation scripts.
+
+## Layout
+
+Every skill lives in its own self-contained plugin folder:
+
+```
+plugins/<skill-name>/
+├── package.json                        # npm package: @kensio/<skill-name>
+├── .claude-plugin/
+│   └── plugin.json                     # name, version, description, author
+└── skills/
+    └── <skill-name>/
+        └── SKILL.md
+```
+
+**A plugin folder must be self-contained.** Never reference files outside it with `../` — plugins
+are copied, zipped, and installed standalone, so those paths will not resolve.
+
+## Steps
+
+1. Create `plugins/<skill-name>/` following the layout above.
+2. Copy `package.json` from an existing plugin; set `name` to `@kensio/<skill-name>` and the
+   `repository.directory` to `plugins/<skill-name>`.
+3. Copy `.claude-plugin/plugin.json`; set `name` and `description`.
+4. Set the `version` in both files to whatever the other plugins currently carry. Versions move in
+   lockstep across the whole repo, and the release workflow is what changes them — never pick a new
+   number by hand.
+5. Write `skills/<skill-name>/SKILL.md` (see frontmatter below).
+6. Add an entry to `.claude-plugin/marketplace.json` with a matching `name`, a `source` of
+   `"./plugins/<skill-name>"`, and a description.
+7. Run `pnpm check`.
+
+## SKILL.md frontmatter
+
+```markdown
+---
+name: <skill-name>
+description: <what it does, then when to use it — include the words and phrases a user would actually type>
+---
+```
+
+- `name` must be kebab-case and match the containing directory.
+- `description` is the _only_ thing Claude sees when deciding whether to load the skill, so it
+  carries the whole triggering burden. State what the skill does, then when to use it, in third
+  person. Concrete trigger phrases beat abstract summaries.
+- Optional frontmatter worth knowing: `allowed-tools` (restrict the tools the skill may use) and
+  `disable-model-invocation: true` (user-invocable only, via `/<skill-name>`).
+
+## Writing the body
+
+Keep `SKILL.md` short and imperative — it is instructions for Claude, not documentation for a human.
+Push detail into sibling files (`reference.md`, `examples/`) and link to them, so the body stays
+cheap to load and the details are read only when needed.
+
+## Releasing
+
+There is nothing to do. Merging to `main` releases, and the version comes from the pull request
+title: `fix:` for a patch, `feat:` for a minor, `feat!:` or a `BREAKING CHANGE` footer for a major.
+A `docs:` or `chore:` title releases nothing.
+
+Every plugin is set to the new version together, so a released version means the same commit
+wherever it was installed from.