@ericrisco/rsc 3.3.0 → 3.3.1

package/README.md

@@ -405,6 +405,9 @@ file, and `rsc agents reset <name>` takes rsc's version back after a backup.
 
 ## CLI
 
+`rsc` below is short for `npx @ericrisco/rsc`. Without a global install (`npm i -g @ericrisco/rsc`),
+the bare `rsc` answers `command not found`: type the `npx` form.
+
 ```bash
 # Setup
 rsc onboard                          # plain-language onboarding; writes nothing until you accept
@@ -429,7 +432,7 @@ rsc ingest notas.md --topic crm      # move a file into 02-DOCS/raw/ (verified c
 rsc copy rules | check ad.txt        # the phrases this project forbids, and a check before publishing
 
 # Memory and diagnostics
-rsc memory status | off | resume
+rsc memory status | off | resume     # session continuity; «recuerda esto» goes to 02-DOCS/wiki/
 rsc doctor                           # harness health and onboarding readiness
 rsc repair                           # put the harness back to what is declared
 rsc backups | restore latest         # project-local snapshots

package/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "3.3.0",
+  "version": "3.3.1",
   "counts": {
     "skills": 269,
     "agents": 34,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ericrisco/rsc",
-  "version": "3.3.0",
+  "version": "3.3.1",
   "description": "A guided harness builder that turns your goal into a minimal, verified AI-agent setup using strict best practices.",
   "type": "module",
   "bin": {

package/skills/suggest/SKILL.md

@@ -55,13 +55,12 @@ name it and offer it. This runs mid-conversation, not only at project start.
 1. `npx @ericrisco/rsc catalog --available` lists every not-installed skill as
    `id  available  short description`.
 2. Pick the single best fit **by meaning**, the way you would match a request to a teammate's
-   expertise — "mandar emails de bienvenida" → an email/outreach skill, though not one keyword
-   overlaps. If nothing genuinely fits, say so
-   and move on: a tangential suggestion is worse than none.
+   expertise, even when no keyword overlaps. If nothing genuinely fits, say so and move on: a
+   tangential suggestion is worse than none.
 3. Ask once, plainly: "Para esto instalaría `<id>`, que aún no tienes. ¿La instalo? (sí/no)".
 4. On yes, run `npx @ericrisco/rsc add <id>`, then continue the original task.
 
-Installing changes the user's environment, so it is always their call. One suggestion at a time,
+One suggestion at a time,
 and never to interrupt a flow with a nice-to-have. Never recommend something already installed
 (`npx @ericrisco/rsc list`).
 
@@ -78,9 +77,8 @@ Not covered → one line, skill or agent. Rules: `skill-scout`.
 
 ## 3. A harness that is broken fixes itself
 
-You are injected into every session, so you are the only thing that can notice a broken
-harness before its owner does — and its owner usually cannot, because the symptoms name
-nothing they recognise. When any of these is true, act on it **once** in the session:
+Its owner rarely notices: the symptoms name nothing they know. When any of these
+is true, act on it **once** in the session:
 
 - `.rsc.json` exists and what it declares is not what is installed;
 - the same hook seems to run several times;
@@ -100,7 +98,7 @@ a cause. Then:
   teammate added, disarming a gate — **ask first**. A `git pull` never rewrites someone's
   machine.
 
-Offer once per session. Never mention any of it when the harness is healthy.
+Offer once per session; say nothing when the harness is healthy.
 
 ## 4. First contact
 
@@ -114,6 +112,12 @@ Before handling the first request of a session, check the workspace:
   `.rsc/.no-harness`, confirm in one line, and never auto-start `init` in this repo again.
 - With a profile, this gate is inert. Never re-onboard.
 
+## 5. «Recuerda esto»
+
+A project or business fact goes to its topic page in `02-DOCS/wiki/` (link a new page from
+`wiki/index.md`); say the path. Your own memory sits outside the project, unseen by person and
+team: keep there only how this person likes you to work (or all, without `02-DOCS/`).
+
 ## Explain without assuming
 
 Define a term at first use; never give a command, flag or path without saying what it does.

package/skills/suggest/evals/cases.yaml

@@ -76,3 +76,9 @@ capability:
       - "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"
+
+  - scenario: "In a workspace with `02-DOCS/wiki/`, the user says 'recuerda que toda la actividad, también la de Andorra, va por una sola sociedad, Nadsan 2006 S.L.'. Show where rsc-suggest puts it."
+    must_include:
+      - "Writes the fact into the `02-DOCS/wiki/` page of its topic (creating it and linking it from `wiki/index.md` if none exists), not only into the assistant's own memory under `~/.claude/projects/`"
+      - "Tells the person the path where it was saved"
+      - "Opens no FTD document and asks no lane question for it"