@victortomaili/skill-cli 0.6.4 → 0.6.5

package/CHANGELOG.md

@@ -11,6 +11,18 @@ 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.5] - 2026-07-08
+
+### Changed
+- AGENTS.md START GATE: **ENFORCEMENT** block — for EVERY active skill the agent
+  MUST state a decision out loud (LOAD or PROPOSE); staying silent or "not needed
+  for this task" is not valid. A ★ default is NEVER silently skipped: style/cost/
+  shortcut skills are candidates for every task type, "the user didn't ask" is not a
+  reason to stay quiet, and the only valid silence is the user already declining it
+  this session. Proposing is proactive — don't wait to be asked.
+- `skill active` now prints a bold footer: "For EACH ★ skill above: PROPOSE it now.
+  Task type is irrelevant; 'not needed' is not a skip reason."
+
 ## [0.6.4] - 2026-07-08
 
 ### Added

package/package.json

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

@@ -40,7 +40,8 @@ export function cmdActive() {
     if (s.description) console.log(c.gray('      ' + String(s.description).replace(/[\r\n]+/g, ' ').trim()))
   }
   console.log()
-  console.log(c.yellow('★') + c.gray(' = default. Load a skill: ') + c.cyan('skill cat <name>'))
+  console.log(c.bold(c.yellow('→ For EACH ★ skill above: PROPOSE it now.')) + c.gray(' Task type is irrelevant — \"not needed for this task\" is NOT a reason to skip. The user decides, not you.'))
+  console.log(c.gray('  Load a skill: ') + c.cyan('skill cat <name>'))
 }
 
 // `skill default <name>` — mark a skill as a default (active by default in every

package/src/lib/agents-md.js

@@ -37,7 +37,18 @@ Read it, then for EACH skill decide FROM ITS DESCRIPTION:
   • response STYLE / tone / format / a persistent mode (e.g. a brevity style);
   • CONTEXT-COST / token optimization;
   • an optional ACCELERATOR / shortcut (easier or faster, but not about correctness).
-When unsure → PROPOSE (proposing is the safe default; loading is silent).
+ENFORCEMENT — for EVERY active skill you MUST state a decision OUT LOUD: LOAD it
+or PROPOSE it to the user. Staying silent, or "not needed for this task", is NOT
+a valid decision. In particular:
+- A ★ default is NEVER silently skipped. STYLE / COST / shortcut skills are
+  candidates for EVERY task type — review, debugging, refactor, anything; the task
+  type does NOT disqualify them, and "the user didn't ask" is NOT a reason to stay
+  quiet. If you are not loading a ★ default, you MUST propose it. The ONLY valid
+  reason to stay silent about a ★ is: the user already declined it this session.
+- Do NOT wait for the user to ask — proposing happens HERE, proactively, every turn
+  until the user decides.
+When unsure whether to load or propose → PROPOSE (proposing is the safe default;
+loading is silent).
 PRIORITIES — when trading off how to do the work, rank: CORRECTNESS first, then
 QUALITY, then COST (cheap / token-efficient), then SPEED (fast). Never sacrifice
 correctness or quality for speed or cost.