@victortomaili/skill-cli 0.5.1 → 0.6.1

package/CHANGELOG.md

@@ -11,6 +11,36 @@ 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.1] - 2026-07-07
+
+### Changed
+- Renamed the agent catalog command `skill defaults` → **`skill active`** (`skill
+  status` is an alias; `skill defaults` is kept as a legacy alias so already-bootstrapped
+  agents keep working). It now lists ONLY the skills active in the current project
+  (defaults + project allow, minus deny) with full descriptions — not every installed
+  skill. `skill default <name>` / `skill undefault <name>` (marking) are unchanged.
+- AGENTS.md START GATE updated to run `skill active` and scope the catalog to
+  active skills.
+
+## [0.6.0] - 2026-07-07
+
+### Changed
+- **`skill defaults` is now a description-only catalog.** It lists EVERY installed
+  skill (name + full description + triggers; ★ marks defaults) — never the skill
+  body. The agent reads the catalog and decides per skill: functional for the task
+  → `skill cat <name>`; context-altering (changes HOW the agent responds) → propose
+  and wait for the user's confirmation. This follows the existing SKILL.md standard
+  — no extra frontmatter field is required or expected on any skill.
+- **Context-altering detection is the agent's judgment, from the description.** Any
+  skill can be context-altering (including ones installed later); the agent decides
+  from the description text, with no hardcoded list. (`skill cat` is unchanged — it
+  still loads a full skill on demand.)
+
+### Added
+- AGENTS.md START GATE now enforces **"LOADED ≠ LISTED"**: a skill is loaded only
+  if the agent ran `skill cat <name>` for it this session — listing/cataloging a
+  skill (or its ★ / `active` status) is not loading.
+
 ## [0.5.1] - 2026-07-07
 
 ### Fixed

package/README.md

@@ -83,7 +83,7 @@ short bootstrap block telling it to run `skill` on `/X`.
 | `skill disable <name> [-g]` | Deny in project, or remove global default with `-g` |
 | `skill default <name>` | Mark a default skill (global: active + auto-load) |
 | `skill undefault <name>` | Remove the default flag |
-| `skill defaults` | List default skills (the command your agent runs on start) |
+| `skill active` | List ACTIVE skills + descriptions (the command your agent runs on start; alias: `status`) |
 | `skill list` | Show installed + active skills (cwd-aware, ★ = default) |
 | `skill show <name>` | Skill metadata (path, triggers, version) |
 | `skill cat <name>` | Dump skill content into context |
@@ -181,8 +181,8 @@ with no source also opens it.
 A **default** is a skill that is **active by default in every project** AND
 **auto-loaded on agent session start** — one unified global list in `config.yaml`
 (`defaults:`). Mark one with `skill default <name>`, remove with
-`skill undefault <name>`, list them with `skill defaults`. The AGENTS.md bootstrap
-block tells your agent to run `skill defaults` on start, then `skill cat <name>`
+`skill undefault <name>`, list them with `skill active`. The AGENTS.md bootstrap
+block tells your agent to run `skill active` on start, then `skill cat <name>`
 for each.
 
 Defaults are a **global** concept (never per-project). A project can still turn a
@@ -197,12 +197,15 @@ default; `space` toggles the per-project override.
 instruction file (`CLAUDE.md`, `AGENTS.md`, `GEMINI.md`):
 
 > **START GATE:** on the first user message, your VERY FIRST action — BEFORE
-> ANYTHING ELSE (before thinking, before any tool call) — is `skill defaults` +
-> `skill cat <name>` for each, then `skill list`. Then each
-> message, discover/load relevant skills (`skill cat` / `skill trigger`), once each.
-> A **context-altering** skill (changes HOW you respond — style/mode) is
-> **PROPOSE-ONLY**: propose it, then apply only after the user confirms
-> (`active` ≠ applied; an explicit `/X` counts). `/X` → `skill trigger X`.
+> ANYTHING ELSE (before thinking, before any tool call) — is `skill active`, the
+> skill **catalog** (every skill's name + full description; never the body). Read
+> it and decide per skill from its description: **functional** for the task → load
+> it (`skill cat <name>`); **context-altering** (changes HOW you respond —
+> style/mode) → **propose**, apply only after the user confirms (`/X` = confirm).
+> **LOADED ≠ LISTED**: a skill is loaded only if you `cat`-ed it this session —
+> listing it (or its ★ / `active` status) is not loading. Any skill can be
+> context-altering; the agent judges from the description (no flag, no fixed list).
+> `/X` → `skill trigger X`.
 
 It's wrapped in `<!-- BEGIN skill-cli --> … <!-- END skill-cli -->` markers, never
 duplicates, and preserves your existing file content. Re-run `init -g` any time —

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@victortomaili/skill-cli",
-  "version": "0.5.1",
+  "version": "0.6.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/cli.js

@@ -12,7 +12,7 @@ import { cmdUpdate } from './commands/update.js'
 import { cmdRemove } from './commands/remove.js'
 import { cmdSearch } from './commands/search.js'
 import { cmdManager } from './commands/manager.js'
-import { cmdDefaults, cmdDefault, cmdUndefault } from './commands/defaults.js'
+import { cmdActive, cmdDefault, cmdUndefault } from './commands/defaults.js'
 import { isInteractive } from './lib/interactive.js'
 import { VERSION } from './lib/version.js'
 
@@ -33,11 +33,11 @@ ${c.bold('Activation')}
   ${c.cyan('skill enable')} ${c.gray('<name> [-g]')}  allow in project, or global default (-g)
   ${c.cyan('skill disable')} ${c.gray('<name> [-g]')} deny in project, or remove global default (-g)
   ${c.cyan('skill list')}                  installed + active skills (cwd-aware)
+  ${c.cyan('skill active')}               active skills + descriptions (agent runs on start; alias: status)
 
 ${c.bold('Defaults (active + auto-load)')}
   ${c.cyan('skill default')} ${c.gray('<name>')}    mark a default skill (global: active in every project)
   ${c.cyan('skill undefault')} ${c.gray('<name>')}  remove the default flag
-  ${c.cyan('skill defaults')}                  list default skills (agent runs this on start)
 
 ${c.bold('Usage (agent)')}
   ${c.cyan('skill show')} ${c.gray('<name>')}         metadata + path + triggers
@@ -90,7 +90,7 @@ async function main() {
     case 'enable': cmdEnable(rest); break
     case 'disable': cmdDisable(rest); break
     case 'list': case 'ls': cmdList(rest); break
-    case 'defaults': cmdDefaults(rest); break
+    case 'active': case 'status': case 'defaults': cmdActive(rest); break
     case 'default': case 'def': cmdDefault(rest); break
     case 'undefault': case 'undef': cmdUndefault(rest); break
     case 'show': case 'info': cmdShow(rest); break

package/src/commands/defaults.js

@@ -1,34 +1,46 @@
 import c from 'picocolors'
 import { listStore } from '../lib/store.js'
-import { readGlobalConfig, writeGlobalConfig, computeDefaults } from '../lib/config.js'
-import { trunc } from '../lib/format.js'
+import { readGlobalConfig, writeGlobalConfig, readProjectConfig, computeEffective } from '../lib/config.js'
 
-// `skill defaults` — list the skills marked as defaults. In the unified model a
-// default skill is BOTH active-by-default in every project AND auto-loaded on
-// agent session start (one global `defaults` list). This is the agent-facing
-// command the AGENTS.md block tells the agent to run, then `skill cat <name>`
-// for each. Defaults are a GLOBAL concept (never per-folder).
-export function cmdDefaults() {
+// `skill active` (aliases: `status`, legacy `defaults`) — the description-only
+// catalog of ACTIVE skills in the current project (defaults + project allow,
+// minus deny). The agent runs this at session start: it lists each active skill's
+// name + FULL description (never the body), then the agent itself decides per
+// skill — functional → `skill cat`, context-altering → propose. Detection of
+// context-altering is the agent's judgment from the description (no flag, no fixed
+// list), so it works for any skill, including ones installed later.
+export function cmdActive() {
   const installed = listStore()
   const globalCfg = readGlobalConfig()
-  const eff = computeDefaults(installed, globalCfg)
+  const projCfg = readProjectConfig()
+  const eff = computeEffective(installed, globalCfg, projCfg)
+  const defs = new Set((globalCfg.defaults || []).map(d => String(d).toLowerCase()))
 
-  console.log(c.bold('skill defaults') + c.gray(' — active by default + auto-load on session start (global)'))
+  console.log(c.bold('skill active') + c.gray(' — active skills in this project (descriptions only; functional → `skill cat`, context-altering → propose)'))
   console.log()
 
   if (eff.length === 0) {
-    console.log(c.gray('  No default skills yet. Mark with: ') + c.cyan('skill default <name>'))
+    console.log(c.gray('  No active skills in this project.'))
     return
   }
 
+  // CATALOG of ACTIVE skills only (not all installed): defaults + project allow,
+  // minus deny. Print each one's name + FULL description (one line) + triggers —
+  // never the body. The agent reads descriptions and itself decides per skill:
+  // load (skill cat) if functional for the task, or PROPOSE if context-altering
+  // (changes HOW the agent responds). Detection is the agent's judgment from the
+  // description, so it works for any skill — including ones installed later —
+  // with no hardcoded list or flag.
   for (const name of eff) {
     const s = installed.find(x => x.name === name)
-    const trg = s && s.triggers.length ? '  ' + c.gray('/' + s.triggers.join(', /')) : ''
-    console.log(`  ${c.yellow('★')} ${c.bold(name.padEnd(22))}${trg}`)
-    if (s && s.description) console.log(c.gray('      ' + trunc(s.description, 66)))
+    if (!s) continue
+    const star = defs.has(s.name.toLowerCase()) ? c.yellow('★') + ' ' : '  '
+    const trg = s.triggers.length ? '  ' + c.gray('/' + s.triggers.join(', /')) : ''
+    console.log(`  ${star}${c.bold(s.name)}${trg}`)
+    if (s.description) console.log(c.gray('      ' + String(s.description).replace(/[\r\n]+/g, ' ').trim()))
   }
   console.log()
-  console.log(c.gray('Load each into context: ') + c.cyan('skill cat <name>'))
+  console.log(c.yellow('★') + c.gray(' = default. 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

@@ -6,8 +6,10 @@ const BEGIN = '<!-- BEGIN skill-cli -->'
 const END = '<!-- END skill-cli -->'
 
 // Global instruction block — injected into each agent's global instruction file.
-// Covers usage, defaults (auto-load), per-message discovery, and the
-// propose-then-confirm rule for context-altering skills.
+// `skill active` (alias: `status`) is a description-only CATALOG of ACTIVE skills;
+// decides per skill: functional → `skill cat`, context-altering → propose. No flag
+// or fixed list — detection is the agent's judgment from the description, so it
+// covers any skill (including ones installed later).
 export const AGENTS_BLOCK = `## skill-cli
 
 This machine uses the \`skill\` command to manage skills (instruction / workflow
@@ -23,25 +25,29 @@ Usage:
 
 START GATE (mandatory): On the FIRST user message of a session, your VERY FIRST
 action — BEFORE ANYTHING ELSE: before you start thinking/reasoning about the task
-and before any tool call — MUST be to run \`skill defaults\` then
-\`skill cat <name>\` for each result, then \`skill list\` to learn every skill's
-triggers. Do this even if the task looks trivial: skills shape how you should
-approach the task, so you cannot reason about it correctly until they are loaded.
+and before any tool call — MUST be to run \`skill active\`. It prints the skill
+CATALOG — every ACTIVE skill's name + FULL description (NOT the skill body).
+Read it, then for EACH skill decide FROM ITS DESCRIPTION:
+- Functional / useful for THIS task → load it: \`skill cat <name>\`.
+- Changes HOW you respond (a style, tone, format, or persistent MODE — e.g. a
+  brevity/compression style) → it is CONTEXT-ALTERING: PROPOSE it to the user and
+  apply ONLY after they confirm (\`/X\` = confirm). Do NOT load/apply it yourself.
+LOADED ≠ LISTED. A skill is loaded ONLY if you have run \`skill cat <name>\` for
+it THIS session. Seeing a skill in \`skill active\` / \`skill list\` does NOT load
+it — you then know only its name + description, nothing more. Never infer a skill
+is in your context from its name, the \u2605 marker, or an \`active\` status: if you
+haven't catted it, treat it as NOT loaded (then decide: cat it, or propose it).
+Do not assume a skill is already applied — \`active\`/\u2605-default = AVAILABLE, not
+APPLIED. ANY skill can be context-altering; judge from the description — there is
+no fixed list and no flag. Do this even if the task looks trivial: skills shape
+how you approach it, so you cannot reason about it correctly until you've reviewed
+them.
 
-Discovery (mandatory, every message): On EVERY user message, decide whether a
-skill is relevant by matching the message against the trigger catalog from
-\`skill list\`. If a relevant skill is not yet loaded, load it with \`skill cat
-<name>\` (or \`skill trigger <keyword>\` to resolve a keyword). Load each skill only
-ONCE per session. When you load or re-read ANY skill mid-session, immediately
-re-evaluate the current message and load/propose any newly-relevant skill.
-
-Context-altering skills (HARD RULE): Some skills change HOW you respond — output
-style, tone, format, or a persistent mode (e.g. a terseness/compression style) —
-rather than just adding task knowledge. These are PROPOSE-ONLY. You MUST propose
-such a skill and apply it ONLY after the user confirms; an explicit \`/X\` trigger
-counts as confirmation. \`active\` / \u2605-default means AVAILABLE, not APPLIED —
-propose \u2260 auto-apply. This rule overrides any other skill's "always use" rule for
-context-altering skills.
+Discovery (every message): On EVERY later user message, re-check the catalog
+against the new request; load any newly-relevant functional skill
+(\`skill cat <name>\`), and PROPOSE any newly-relevant context-altering one.
+Load each skill only ONCE per session (\`skill trigger <keyword>\` resolves a
+keyword to a skill).
 
 Triggers: when the user types \`/X\`, run \`skill trigger X\`.
 - Single match → apply the output directly.