@victortomaili/skill-cli 0.6.7 → 0.6.8

package/CHANGELOG.md

@@ -11,6 +11,16 @@ 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.6.8] - 2026-07-08
+
+### Changed
+- AGENTS.md + `skill active`: reframed cost/style/speed skills as USER TRADE-OFFS
+  the agent must never pre-judge. The agent kept skipping proposals with "not
+  relevant to this task"; the new wording forbids deciding a trade-off for the
+  user ("not relevant here" = stealing the user's decision). Made the `skill active`
+  footer mechanical (LOAD/PROPOSE/SKIP grid) with an explicit callout: "cost/style
+  but not relevant here → that is the bug. Ask instead."
+
 ## [0.6.7] - 2026-07-08
 
 ### Changed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@victortomaili/skill-cli",
-  "version": "0.6.7",
+  "version": "0.6.8",
   "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

@@ -16,7 +16,7 @@ export function cmdActive() {
   const eff = computeEffective(installed, globalCfg, projCfg)
   const defs = new Set((globalCfg.defaults || []).map(d => String(d).toLowerCase()))
 
-  console.log(c.bold('skill active') + c.gray(' — active skills (descriptions only). AUTO-LOAD what is necessary or quality-improving; PROPOSE style/cost/shortcut skills and wait for confirmation.'))
+  console.log(c.bold('skill active') + c.gray(' — active skills (descriptions only). LOAD correctness/quality ones; PROPOSE every cost/style/speed one (a trade-off is the USER') + c.gray("'s call — never skip it)."))
   console.log()
 
   if (eff.length === 0) {
@@ -40,7 +40,13 @@ export function cmdActive() {
     if (s.description) console.log(c.gray('      ' + String(s.description).replace(/[\r\n]+/g, ' ').trim()))
   }
   console.log()
-  console.log(c.bold('→ Decide each skill by the criteria:') + c.gray(' affects ') + c.cyan('CORRECTNESS/QUALITY') + c.gray(' → load (') + c.cyan('skill cat <name>') + c.gray('); affects ') + c.cyan('COST/SPEED') + c.gray(' → propose; affects none → skip. Task type is irrelevant; when unsure → propose.'))
+  console.log(c.bold('→ For EACH skill above, decide in your reply:'))
+  console.log(c.gray('    LOAD    moves CORRECTNESS/QUALITY → run ') + c.cyan('skill cat <name>') + c.gray(' now.'))
+  console.log(c.gray('    PROPOSE moves COST, STYLE, or SPEED  → you MUST ASK "enable <name>?". A trade-off is the'))
+  console.log(c.gray('            USER') + c.gray("'s decision — these move an axis on EVERY reply, so NEVER skip one and"))
+  console.log(c.gray('            NEVER say "not relevant to this task" (that = you deciding for the user).'))
+  console.log(c.gray('    SKIP    moves NONE of the above.'))
+  console.log(c.yellow('  ⚠ If you wrote "cost/style but not relevant here" → that is the bug. Ask instead.'))
 }
 
 // `skill default <name>` — mark a skill as a default (active by default in every

package/src/lib/agents-md.js

@@ -29,12 +29,14 @@ run \`skill active\`. It lists each ACTIVE skill's name + FULL description (neve
 body). Read it, then for EACH skill classify which axis it moves and ACT — there is
 no discretion and no third option:
 - moves CORRECTNESS or QUALITY → load it now: \`skill cat <name>\`.
-- moves COST, SPEED, or response STYLE → PROPOSE it: in THIS reply, ask the user
-  "Enable <name>? It <one-line benefit>." and apply only on yes. These three axes
-  apply to EVERY task by definition (every reply costs tokens and time), so the
-  thoughts "not needed for this task", "the user didn't request it", and "skip
-  unless needed" are FORBIDDEN — they are the exact error. Listing the skill in a
-  table is NOT proposing; you must actually ask.
+- moves COST, SPEED, or response STYLE → PROPOSE it. These are TRADE-OFFS — the
+  USER decides them, NEVER you. Even if you are SURE one would hurt THIS task, you
+  still ASK: "Enable <name>? It <one-line benefit>." (apply only on yes). They move
+  an axis on EVERY task by definition (every reply has a token cost, a length, a
+  style, a speed), so the thoughts "not relevant to this task", "not needed here",
+  "the user didn't request it", and "skip unless needed" are FORBIDDEN — each one
+  is you STEALING the user's decision. Deciding a trade-off is not your role;
+  surfacing it is. A line in a table is NOT proposing — you must actually ask.
 - 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\`