docs(readme): correct Hermes invocation — slash loads bundles, not skills (EN/ES)

Verified against the local hermes CLI: /<name> routes bundles and
quick/plugin commands only. Documented the three working paths: a
`hermes bundles create workflow` slash entry point, `chat -s <skill>`
preload, and description-matched natural language.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: gtrabanco

README.es.md

@@ -436,12 +436,25 @@ se ignoran en silencio.) Elige el modelo de sesión según la
 [tabla de equivalencia](#equivalencia-de-modelos-modelos-no-claude--de-libre-inferencia)
 — en NaN.builders, según los picks de arriba.
 
-**Invocación:** Hermes soporta la misma sintaxis slash — `/execute-phase 14 P1`,
-`/review-change` — **pero solo en sesiones arrancadas después del install**. Si
-ves `error: not a quick/plugin/skill command`, la sesión es anterior al
-install: `/reset` (terminal) o reinicia la app de escritorio, y comprueba con
-`/bundles` o "What skills do you have?". El lenguaje natural también funciona
-siempre: "use the execute-phase skill to implement fix #243".
+**Invocación:** en Hermes, `/<nombre>` carga **bundles**, no skills
+individuales — `/execute-phase` devuelve `error: not a quick/plugin/skill
+command` aunque la skill aparezca como enabled. Tres vías que funcionan:
+
+```sh
+# 1. Una vez: crea un bundle → /workflow pasa a ser el punto de entrada slash
+hermes bundles create workflow \
+  -s init-workspace -s plan-feature -s plan-fix -s execute-phase \
+  -s review-change -s audit-pr -s product-audit -s audit-docs \
+  -s triage-issue -s log-session -s ship-roadmap \
+  -d "agentic-workflow: plan → execute → review → audit → merge"
+#    después, en cualquier sesión:  /workflow execute-phase --fix #243
+
+# 2. Terminal: precarga skills para una sesión
+hermes chat -s execute-phase
+
+# 3. Cualquier sesión, sin setup: lenguaje natural — las skills se seleccionan
+#    por descripción: "use the execute-phase skill to implement fix #243"
+```
 
 Sin publicar en npm, sin registro, sin paso de build — `skills` clona el repo y
 copia (o enlaza con symlink) las carpetas de skills en el sitio correcto para

README.md

@@ -421,12 +421,25 @@ skills:
 skipped.) Pick your session model per the [model-equivalence table](#model-equivalence-non-claude--free-inference-models)
 — on NaN.builders, per the picks above.
 
-**Invoking:** Hermes supports the same slash syntax — `/execute-phase 14 P1`,
-`/review-change` — **but only in sessions started after the install**. If you
-get `error: not a quick/plugin/skill command`, the session predates the
-install: `/reset` (terminal) or restart the desktop app, then check with
-`/bundles` or "What skills do you have?". Natural language always works too:
-"use the execute-phase skill to implement fix #243".
+**Invoking:** in Hermes, `/<name>` loads **bundles**, not individual skills —
+`/execute-phase` returns `error: not a quick/plugin/skill command` even when
+the skill shows as enabled. Three working ways:
+
+```sh
+# 1. One-time: create a bundle → /workflow becomes the slash entry point
+hermes bundles create workflow \
+  -s init-workspace -s plan-feature -s plan-fix -s execute-phase \
+  -s review-change -s audit-pr -s product-audit -s audit-docs \
+  -s triage-issue -s log-session -s ship-roadmap \
+  -d "agentic-workflow: plan → execute → review → audit → merge"
+#    then, in any session:  /workflow execute-phase --fix #243
+
+# 2. Terminal: preload skills for a session
+hermes chat -s execute-phase
+
+# 3. Any session, no setup: natural language — skills are matched by description
+#    "use the execute-phase skill to implement fix #243"
+```
 
 No npm publish, no registry, no build step — `skills` clones the repo and copies
 (or symlinks) the skill folders into the right place for each agent. The skills