@ericrisco/rsc 3.0.14 → 3.0.15

package/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "3.0.14",
+  "version": "3.0.15",
   "counts": {
     "skills": 271,
     "agents": 34,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ericrisco/rsc",
-  "version": "3.0.14",
+  "version": "3.0.15",
   "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/connect-tool/SKILL.md

@@ -27,8 +27,6 @@ Ask only what the docs cannot answer, in plain words (`technical_level` in
   server in the office.
 - **Read or write?** Reports and questions need reading. Entering invoices needs writing, and
   writing is a separate, explicit decision (below).
-- **Who administers it?** Themselves, an IT person, an accounting firm, the vendor's distributor.
-  That person often holds the keys, and step 5 writes the message for them.
 
 ## 1. Research: the docs decide, never memory
 
@@ -128,20 +126,12 @@ Most small-business software was never meant to be connected. The safe pattern:
 
 4. **Reach it privately.** Same network, or a private mesh (the `TAILSCALE` tool). Never open the
    database port to the internet.
-5. **Ask first.** Many vendors and distributors restrict direct database access in their support
-   terms. The message in step 5 asks before anyone touches anything.
+5. **Check the support terms.** Many vendors restrict direct database access. If they do, use
+   their export or their API instead.
 
 ## 5. Guide the user, in their words
 
-Say what you found, which route you chose and why, and what happens next, in short sentences. When
-the next step belongs to someone else, write the message for them, ready to send:
-
-```text
-Hi <name>, we want our assistant to READ <data> from <program> for <purpose>.
-Could you create a read-only user (SELECT only, no write permissions) on <database or a copy of
-it>, and tell us the server name and port? We will not modify anything. If your support terms
-prefer another method (an export, an official API), we are happy to use that instead.
-```
+Say what you found, which route you chose and why, and what happens next, in short sentences.
 
 ## 6. Leave it written down
 

package/skills/connect-tool/evals/cases.yaml

@@ -17,8 +17,8 @@ should_trigger:
   - prompt: "Hook up our WhatsApp Business number so the agent can see incoming orders."
     why: "A named tool where the route is not obvious (the Business app versus the Cloud API). Research decides, and reading orders is the first, read-only step."
 
-  - prompt: "Mi TPV no tiene API. ¿Qué le pido al informático para que el agente vea las ventas?"
-    why: "Non-obvious trigger: no connection yet, the deliverable is the route choice plus the ready-to-send message for the IT person asking for an export or a read-only user."
+  - prompt: "Mi TPV no tiene API. ¿Cómo hago que el agente vea las ventas?"
+    why: "Non-obvious trigger: no API is not the end. The route comes from the product's export features or a read-only copy of its database, found in the vendor's docs."
 
   - prompt: "Connect the agent to our Access database, the one the old stock program uses."
     why: "A legacy file database. Copy the .mdb/.accdb, read it with mdbtools or convert it, and never write into the program's file."
@@ -55,4 +55,4 @@ capability:
       - "Chooses a read-only route and never proposes writing into the program's database; if writing comes up, it goes through the official import format"
       - "Proposes reading a nightly copy with a SELECT-only user, reached privately, never the live database exposed to the internet"
       - "Builds 01-TOOLS/<TOOL>/ from the template with a test_connection that proves reading works AND that a write is refused, telling a permission error apart from any other failure"
-      - "Writes the ready-to-send message for the accounting firm asking for a read-only user or an export, and records the connection in 02-DOCS"
+      - "Explains the chosen route in plain words and records the connection in 02-DOCS"