@victortomaili/skill-cli 0.7.0 → 0.7.1

package/CHANGELOG.md

@@ -11,6 +11,17 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Cursor adapter (`.cursor/rules` format) for `init -g` bootstrap.
 - Per-agent hook adapters for automatic `/X` triggering (push model).
 
+## [0.7.1] - 2026-07-08
+
+### Added
+- PARAMETERS (2nd rule, per user direction): when a proposed skill lists activation
+  options in its description (a level, language, mode, format, or strictness), the
+  agent must ask the user to choose them in the SAME proposal and the gate stays up
+  until BOTH the enable decision AND the parameters are given. Don't pick parameters
+  for the user; don't start the task until both are settled. Examples are fully
+  generic (no skill-specific names). Reflected in the AGENTS.md block and the
+  `skill active` footer (new PARAMS row).
+
 ## [0.7.0] - 2026-07-08
 
 ### Changed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@victortomaili/skill-cli",
-  "version": "0.7.0",
+  "version": "0.7.1",
   "description": "Cross-agent skill manager — one global store, clean agent folders, activation via skill.config",
   "license": "MIT",
   "author": "Victor Tomaili <victor@tomaili.com>",

package/src/commands/defaults.js

@@ -47,6 +47,9 @@ export function cmdActive() {
   console.log(c.gray('            The wait is the POINT — a trade-off is the USER') + c.gray("'s decision; it moves an axis") )
   console.log(c.gray('            on EVERY reply, so NEVER skip and NEVER say "not relevant here".'))
   console.log(c.gray('            Mentioning / noting / "available" is NOT asking.'))
+  console.log(c.gray('    PARAMS  if a proposed skill lists activation options (level / language / mode /'), )
+  console.log(c.gray('            format / strictness), ask the user to choose them in the SAME proposal — do not pick'))
+  console.log(c.gray('            for them. Gate stays up until enable decision + parameters are both given.'))
   console.log(c.gray('    SKIP    moves NONE of the above.'))
   console.log(c.yellow('  ⚠ Breaking the gate: starting the task before the user answers,'))
   console.log(c.yellow('    "would delay it", "user has a clear request", "I will just do the task",'))

package/src/lib/agents-md.js

@@ -44,6 +44,12 @@ no discretion and no third option:
   "the user has a clear request", "I'll just do the task first", and "I'll mention it
   and proceed" are FORBIDDEN: each is you deciding for the user. Mentioning / noting /
   "available" is NOT asking — you must ASK a yes/no question and then wait.
+  PARAMETERS (2nd rule): if the skill's description lists activation options to pick
+  from — e.g. a level, a language, a mode, a format, or a strictness — you MUST ask
+  the user to choose them in the SAME proposal (do NOT pick for them), and the gate
+  stays up until they give BOTH the enable decision AND the parameters. Genericize
+  — never assume a particular skill; read its description to see which options (if
+  any) it exposes, and ask for those.
 - moves none of the above → skip.
 When unsure if a skill moves an axis → PROPOSE (ask). LOADED \u2260 LISTED: a skill is
 loaded only if you \`cat\`-ed it this session — listing it, its \u2605, or its \`active\`