@ericrisco/rsc 0.1.26 → 0.1.28

package/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.1.26",
+  "version": "0.1.28",
   "counts": {
     "skills": 231
   },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ericrisco/rsc",
-  "version": "0.1.26",
+  "version": "0.1.28",
   "description": "Eric Risco's agent-skills catalog as a granular, self-recommending CLI installer.",
   "type": "module",
   "bin": {

package/scripts/install-apply.js

@@ -14,22 +14,37 @@ const CLI_VERSION = JSON.parse(readFileSync(join(ROOT, 'package.json'), 'utf8'))
 // materialized at — the single, target-agnostic source of truth for "installed
 // skills version" (read by the SessionStart update check too).
 const versionFile = (cwd) => join(cwd, '.rsc', '.version');
-function readBaseVersion(cwd) {
-  try { return readFileSync(versionFile(cwd), 'utf8').trim(); } catch { return undefined; }
+
+// Per-skill base version. A single global `.rsc/.version` cannot represent a
+// partially-refreshed base set, which broke multi-target sync: the first target's pass
+// bumped `.rsc/.version`, so later targets saw "current" and skipped refreshing their
+// exclusive skills' bases. Tracking the version each base was materialized at makes the
+// refresh decision per skill, independent of target ordering. (Absent file → every base
+// is treated as stale and refreshed once, which self-heals installs from before this.)
+const baseVersionsFile = (cwd) => join(cwd, '.rsc', '.base-versions.json');
+function readBaseVersions(cwd) {
+  try { return JSON.parse(readFileSync(baseVersionsFile(cwd), 'utf8')); } catch { return {}; }
+}
+function writeBaseVersions(cwd, versions) {
+  mkdirSync(dirname(baseVersionsFile(cwd)), { recursive: true });
+  writeFileSync(baseVersionsFile(cwd), JSON.stringify(versions, null, 2) + '\n');
 }
 
-// Materialize the real skill files into the project-local base. Normally copied
-// once and reused; when `refresh` is set (a different CLI version than the base was
-// materialized at) the base is re-copied so a reinstall actually updates content.
-// Skills are read-only catalog (user customization lives in 02-DOCS/CLAUDE.md), so
-// overwriting on a version change is safe.
-function ensureBase(id, cwd, refresh) {
+// Materialize the real skill files into the project-local base. Copied once and reused;
+// when the recorded base version for THIS skill differs from the CLI version, the base is
+// re-copied so a reinstall/sync actually updates content. Tracked per skill (see
+// baseVersionsFile) so a multi-target sync refreshes every target's bases, not just the
+// first target's. Skills are read-only catalog (user customization lives in 02-DOCS), so
+// overwriting on a version change is safe. Mutates `baseVersions` with the new mark.
+function ensureBase(id, cwd, baseVersions) {
   const dest = baseDir(id, cwd);
-  if (refresh && existsSync(dest)) rmSync(dest, { recursive: true, force: true });
+  const stale = baseVersions[id] !== CLI_VERSION;
+  if (stale && existsSync(dest)) rmSync(dest, { recursive: true, force: true });
   if (!existsSync(dest)) {
     mkdirSync(dirname(dest), { recursive: true });
     cpSync(join(ROOT, 'skills', id), dest, { recursive: true });
   }
+  baseVersions[id] = CLI_VERSION;
   return dest;
 }
 
@@ -46,7 +61,7 @@ function generatedHookFiles({ target, cwd }) {
 function managedPathsForInstall({ skillIds, target, home, cwd }) {
   const paths = targetPaths(target, home, cwd);
   const plan = planInstall({ skillIds, target, home, cwd });
-  const out = [paths.stateFile, versionFile(cwd)];
+  const out = [paths.stateFile, versionFile(cwd), baseVersionsFile(cwd)];
   for (const step of plan) {
     if (step.kind === 'skill') {
       out.push(step.to, baseDir(step.id, cwd));
@@ -64,18 +79,21 @@ export async function applyInstall({ skillIds, target, home, cwd = process.cwd()
   if (dryRun) return { dryRun: true, skills: skillIds, paths: managedPaths };
   const state = readState(paths.stateFile);
   const backup = createBackup({ cwd, operation, target, paths: managedPaths, cliVersion: CLI_VERSION });
-  // Refresh bases when installing a different version than they were materialized at
-  // (or a pre-versioning install where the marker is absent). Same version → no-op.
-  const refresh = readBaseVersion(cwd) !== CLI_VERSION;
+  // Decide base refresh per skill (see baseVersionsFile): a base is re-materialized when
+  // its recorded version differs from the CLI version. Robust to multi-target installs/
+  // syncs — a single global marker would be bumped by the first target and make later
+  // targets skip refreshing their exclusive skills' bases.
+  const baseVersions = readBaseVersions(cwd);
   for (const step of plan) {
     if (step.kind === 'skill') {
-      const base = ensureBase(step.id, cwd, refresh);
+      const base = ensureBase(step.id, cwd, baseVersions);
       const files = await writeSkill(target, step.id, base, step.to);
       state.skills[step.id] = { files, base };
     } else if (step.kind === 'hook') {
-      await wireHook(target, paths, join(ensureBase('suggest', cwd, refresh), 'SKILL.md'));
+      await wireHook(target, paths, join(ensureBase('suggest', cwd, baseVersions), 'SKILL.md'));
     }
   }
+  writeBaseVersions(cwd, baseVersions);
   state.version = CLI_VERSION;
   writeState(paths.stateFile, state);
   mkdirSync(dirname(versionFile(cwd)), { recursive: true });

package/scripts/rsc.js

@@ -187,6 +187,26 @@ async function main() {
       for (const o of toOutcomes(ids)) say(`${o.id}\t${o.label}`);
       return;
     }
+    case 'catalog': {
+      // Full catalog dump for SEMANTIC in-agent discovery: every skill as
+      // `id  <installed|available>  short description`, unranked. `consult` ranks
+      // lexically and returns nothing for natural-language / Catalan intent; `catalog`
+      // hands the agent the whole candidate set so the MODEL picks the best-fit missing
+      // skill by meaning. `--available` drops what's already installed for this target.
+      const m = loadManifest();
+      const installed = new Set(listInstalled({ target }));
+      const onlyAvailable = argv.includes('--available');
+      const short = (d) => {
+        const s = String(d || '').split('. ')[0].replace(/\s+/g, ' ').trim();
+        return s.length > 160 ? `${s.slice(0, 159)}…` : s;
+      };
+      for (const sk of [...m.skills].sort((a, b) => a.id.localeCompare(b.id))) {
+        const state = installed.has(sk.id) ? 'installed' : 'available';
+        if (onlyAvailable && state === 'installed') continue;
+        say(`${sk.id}\t${state}\t${short(sk.description)}`);
+      }
+      return;
+    }
     case 'audit': {
       const report = audit();
       const written = writeAuditReport(report);

package/skills/suggest/SKILL.md

@@ -56,8 +56,8 @@ When the current task would clearly benefit from an rsc skill that is **not inst
 Rules:
 
 - Installing changes the user's environment — always confirm first.
-- To know what exists, run `npx @ericrisco/rsc consult "<the task>"` instead of guessing.
-- For a project-level view, prefer `.rsc/skill-registry.json` when present; if it is missing or stale, suggest `npx @ericrisco/rsc registry refresh`. This is a cheap index, not a reason to load every skill.
+- To know what exists, run `npx @ericrisco/rsc catalog --available` (every NOT-installed skill as `id  available  short description`) and **pick the best fit yourself, by meaning** — see the detector below. Don't guess from memory.
+- `npx @ericrisco/rsc consult "<task>"` is only a cheap **lexical** hint: it keyword-matches and silently returns nothing for natural-language or non-English/Catalan intent (e.g. it finds no email skill for "mandar emails"). Never let it be the decider; if it's empty, scan `catalog` and judge semantically.
 - Never recommend something already installed (`npx @ericrisco/rsc list`).
 - One suggestion at a time. Don't interrupt the flow for nice-to-haves.
 
@@ -78,24 +78,29 @@ This is broader than "start a project". It includes mid-conversation requests su
 - Knowledge and research: "documenta cómo funciona esto", "crea una wiki", "procesa este inbox", "research competitors", "turn this into SOPs".
 - Other languages: any equivalent phrasing. Match the user's intent, not exact words.
 
-When a capability intent appears:
-
-1. Run `npx @ericrisco/rsc list` to know what is already installed.
-2. Run `npx @ericrisco/rsc consult "<the user's exact intent>"`.
-3. Read the ordered result as the install queue, but pick only the **first missing**
-   skill that is useful right now. Skip `suggest` and any installed skill.
+When a capability intent appears, **you** make the match semantically — do not delegate the decision to a keyword ranker:
+
+1. Run `npx @ericrisco/rsc catalog --available` to get every NOT-installed skill as
+   `id  available  short description`. (It already excludes what's installed.)
+2. **Read the catalog and pick the single best-fit skill by MEANING** — match the user's
+   intent to a skill's *purpose*, semantically, in any language (CA/ES/EN/…), the way you'd
+   match a request to a teammate's expertise. Judge meaning, not shared keywords:
+   "mandar emails de bienvenida" → `email-connector` even though no words overlap its tags;
+   "login con Google" → an auth/security skill, not `flutter`; "transcripció de veu" → a
+   speech/audio skill *if one exists*.
+3. If nothing in the catalog genuinely fits, **say so and move on** — don't force a weak
+   match, and don't propose a tangential skill just to have an answer. (`npx @ericrisco/rsc
+   consult "<intent>"` is available as a lexical hint, but it misses natural-language and
+   Catalan intent and is silent for many real needs — never read its silence as "no skill
+   exists." The catalog + your judgment is the source of truth.)
 4. Ask before installing: "Para esto instalaría `<id>`, que aún no tienes. ¿La instalo? (sí/no)".
-5. On yes, run `npx @ericrisco/rsc add <id>` and then continue the original request.
-
-Example: if the user says "quiero montar una pagina web para vender cursos online",
-do not just start building. Check the installed list, consult that exact phrase, and
-recommend the first missing skill from the returned queue. In a base install, `init`
-and `harness` may already exist, so the first missing skill is usually `nextjs`. In a
-bare install, `init` may be first. Install one skill at a time.
+5. On yes, run `npx @ericrisco/rsc add <id>` and continue the original request. One at a time.
 
-Example: if the user says "hazme una secuencia de cold emails para vender mi SaaS",
-consult that exact phrase and recommend the first missing email/marketing skill rather
-than writing generic copy with no specialist loaded.
+Example: "quiero montar una pagina web para vender cursos online" → scan the catalog and
+pick the web stack skill (usually `nextjs`) by meaning; don't start building before offering it.
+Example: "hazme una secuencia de cold emails para vender mi SaaS" → pick the email/outreach
+skill (`cold-outreach` / `email-connector`) because it *means* email outreach — not because
+the keywords happen to match (they often won't).
 
 ## Onboarding gate (first contact)
 

package/skills/suggest/evals/cases.yaml

@@ -62,17 +62,17 @@ capability:
   - scenario: "Mid-conversation, after base install, the user says 'quiero montar una pagina web para vender cursos online'. `init`, `harness`, `orient`, and `suggest` are already installed; `nextjs` is not. Show how rsc-suggest behaves."
     must_include:
       - "Treats the message as in-agent capability intent, not as a CLI-only consult task"
-      - "Runs `npx @ericrisco/rsc list` before recommending so installed `init`/`harness` are skipped"
-      - "Runs `npx @ericrisco/rsc consult \"quiero montar una pagina web para vender cursos online\"` or equivalent exact-intent consult"
-      - "Names `nextjs` as the first missing useful skill for the website work"
+      - "Runs `npx @ericrisco/rsc catalog --available` to see the not-installed skills (already excludes installed `init`/`harness`)"
+      - "Picks the best-fit skill by MEANING from the catalog, not by relying on lexical `consult` ranking"
+      - "Names `nextjs` as the missing useful skill for the website work"
       - "Asks one short confirmation before installing and does not auto-install"
       - "On confirmation, runs `npx @ericrisco/rsc add nextjs`, then resumes the original website task"
 
   - scenario: "Mid-conversation, the user says 'Automatiza el flujo de leads desde el formulario hasta mi CRM'. The base skills are installed, but `automation-flows` and CRM/connector skills are not. Show how rsc-suggest behaves."
     must_include:
       - "Treats the message as in-agent capability intent for automation/integration, not only as a coding task"
-      - "Runs `npx @ericrisco/rsc list` before recommending"
-      - "Runs `npx @ericrisco/rsc consult \"Automatiza el flujo de leads desde el formulario hasta mi CRM\"` or equivalent exact-intent consult"
-      - "Names the first missing useful automation/connector skill from the consult results"
+      - "Runs `npx @ericrisco/rsc catalog --available` to see the not-installed skills"
+      - "Picks the best-fit missing automation/connector skill by MEANING (not by lexical `consult` ranking, which may return nothing)"
+      - "Names that one missing automation/connector skill"
       - "Asks one short confirmation before installing and does not auto-install"
       - "On confirmation, runs `npx @ericrisco/rsc add <id>` for that one missing skill, then resumes the automation task"