@ssheleg/make-skill 0.15.0 → 0.17.0

package/CHANGELOG.md

@@ -1,5 +1,42 @@
 # Changelog
 
+## v0.17.0
+
+Following `task-pipeline` v1.53.0, which renamed the artifact root's default from
+`docs/superpowers/` to `docs/evidence/` and made the root resolvable (`paths.artifacts`
+in `pipeline.json`, else an existing `docs/evidence/`, else an existing
+`docs/superpowers/` — **the legacy name stays supported and no run warns about it**).
+
+Shipped surfaces name the new default now, which is why this is a minor rather than a
+patch. This project's own records moved with the directory and were not rewritten: a
+brief describes where things were when it was written.
+
+## v0.16.0
+
+### Changed
+
+- **The installer now offers the family's routing block** (closing B-06 in the
+  umbrella). Until now only `super-ux` delegated: install this skill on its own
+  and no router was written at all, so an agent had the skill and no rule saying
+  when to reach for it. The bundle installer wrote all eight, which is why
+  nothing looked broken — the gap only opened for someone installing one member.
+
+  Delegated to `npx sshlg-skills routers --member make-skill` rather than
+  reimplemented, for three reasons:
+
+  - The block describes what the machine actually has. A lone member rendering
+    the whole thing would print a table for routers nobody installed.
+  - `--member` scopes the write to this skill's own section. Verified by damaging
+    two sections of a real block and running this installer: its own was
+    repaired, the other left exactly as it was.
+  - The launcher is the only writer that copies the operator's global instruction
+    file before touching it. That file has no version control behind it.
+
+  `--no-install` keeps it from silently downloading a package nobody asked for.
+  When the launcher is absent the command is printed instead of failing: ending
+  an install in an error over an optional follow-up reads as a failed install.
+  Both paths were exercised.
+
 ## v0.15.0
 
 ### Fixed

package/README.md

@@ -258,7 +258,7 @@ test/validate.py                      # structural validator
 test/evals/                           # trigger set + behavioral scenarios (data)
 .github/workflows/{validate,release}.yml
 install.sh  README.md  CHANGELOG.md  CONTRIBUTING.md  SECURITY.md  SKILL-CARD.md  LICENSE
-docs/superpowers/{specs,plans}/       # historical design records
+docs/evidence/{specs,plans}/       # historical design records
 ```
 
 ## Contributing

package/bin/make-skill.js

@@ -63,6 +63,38 @@ function installOne(label, src, dest, isDir, force) {
   console.log(`Installed ${label} -> ${dest}`);
 }
 
+/**
+ * Ask the family launcher to write the routing block, for this member only.
+ *
+ * Delegated rather than reimplemented, for three reasons. The block describes
+ * what the machine actually has, so a lone member rendering the whole thing
+ * would produce a table for routers nobody installed. `--member` limits the
+ * write to the `make-skill` section and leaves everyone else's alone, which is
+ * what lets the bundle and a single installer both write. And the launcher is
+ * the only writer that copies the operator's global instruction file before
+ * touching it — that file has no version control behind it.
+ *
+ * `--no-install` keeps this from silently downloading a package nobody asked
+ * for. When the launcher is absent, print the command rather than fail: ending
+ * an install in an error because an OPTIONAL follow-up is missing reads as a
+ * failed install.
+ */
+function offerRouters() {
+  const { spawnSync } = require('child_process');
+  const r = spawnSync(
+    'npx',
+    ['--no-install', 'sshlg-skills', 'routers', '--member', 'make-skill'],
+    { stdio: 'inherit', shell: process.platform === 'win32' }
+  );
+  if (r.status !== 0) {
+    console.log(
+      '\nTo have this skill apply by default in every project, add the\n' +
+      "family's routing block to your agent's global instructions:\n\n" +
+      '  npx --yes sshlg-skills routers --member make-skill\n'
+    );
+  }
+}
+
 function main(argv) {
   const args = argv.slice(2);
   if (args.includes('--help') || args.includes('-h')) {
@@ -103,6 +135,11 @@ function main(argv) {
       '         claude plugin update make-skill@make-skill\n' +
       '       Pass --force if you really want both.'
     );
+    // Offered here too. The skill IS present on this machine — as the plugin —
+    // so the routing block is exactly as wanted as on the install path. Two
+    // doors into one install that behave differently is how a feature comes to
+    // exist for half its users.
+    offerRouters();
     return 0;
   }
 
@@ -113,6 +150,7 @@ function main(argv) {
     true,
     force
   );
+  offerRouters();
   return 0;
 }
 

package/cursor/rules/make-skill.mdc

@@ -82,7 +82,7 @@ test/evals/                                # triggers.json + scenarios.json (dat
 .github/workflows/validate.yml (+ release.yml, off by default)
 install.sh, README.md (English-first), CHANGELOG.md, LICENSE (MIT)
 CONTRIBUTING.md + SECURITY.md              # required once the repo is public
-docs/superpowers/{specs,plans}/
+docs/evidence/{specs,plans}/
 ```
 
 ## Claude Code plugin conformance (Anthropic's own reference)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ssheleg/make-skill",
-  "version": "0.15.0",
+  "version": "0.17.0",
   "description": "Create, retrofit, audit, and ship agent skills & Claude Code plugins the proven ssheleg way — conformance to the Agent Skills open standard AND Anthropic's platform rules (front-matter limits, disclosure budgets, per-surface runtime limits, the Skills API, evals) plus the Claude Code plugin reference (manifest schemas, component layout, claude plugin validate --strict), marketplace repo layout, version sync, validator + CI, multi-channel distribution (plugin, vercel skills CLI, npx, Cursor), npm gotchas, the review checklist for third-party skills, and MCP / A2A rules for protocol-connected skills. This package is the installer CLI.",
   "keywords": [
     "skill",

package/plugins/make-skill/.claude-plugin/plugin.json

@@ -3,7 +3,7 @@
   "name": "make-skill",
   "displayName": "Make Skill",
   "description": "Create, retrofit, audit, and ship agent skills & Claude Code plugins the proven ssheleg way: conformance to the Agent Skills open standard, Anthropic's platform rules (surfaces, Skills API, evals) and the Claude Code plugin reference, marketplace repo layout, version sync, validator + CI, multi-channel distribution (plugin, vercel skills CLI, npx, Cursor), npm gotchas, end-to-end first publish, the review checklist for third-party skills, plus MCP / A2A references for protocol-connected skills.",
-  "version": "0.15.0",
+  "version": "0.17.0",
   "author": {
     "name": "ssheleg",
     "url": "https://x.com/sshlg93"

package/plugins/make-skill/skills/make-skill/SKILL.md

@@ -5,7 +5,7 @@ license: MIT
 compatibility: Authoring works on any agent. The bundled scripts/ need python3. Publishing steps need git, gh, node and npm; the plugin gates need the claude CLI. Not usable on the Claude API surface, which has no network and no runtime package install.
 metadata:
   author: ssheleg
-  version: "0.15.0"
+  version: "0.17.0"
   homepage: https://github.com/ssheleg/make-skill
 ---
 
@@ -49,7 +49,7 @@ or `plugins/*/skills/*/` in the current directory → run the Retrofit audit and
 report the gap table plus ONE next action. Nothing to detect → ask in one line
 what to create.
 
-Distributable work is a real project: spec (`docs/superpowers/specs/`) before
+Distributable work is a real project: spec (`docs/evidence/specs/`) before
 code, and the spec locks target-project file contracts FIRST — skills are
 written against that contract, never ad hoc.
 

package/plugins/make-skill/skills/make-skill/references/distribution.md

@@ -66,7 +66,7 @@ the shape from `ssheleg/super-ux`:
 ├── README.md (English-first), CHANGELOG.md, LICENSE (MIT)
 ├── CONTRIBUTING.md + SECURITY.md       # public repo: how to check work, where to report
 ├── SKILL-CARD.md                       # the enterprise registry entry + risk-table pass
-└── docs/superpowers/{specs,plans}/
+└── docs/evidence/{specs,plans}/
 ```
 
 **Public-repo floor** (validator-enforced): a README saying what it does before