@ericrisco/rsc 3.0.12 → 3.0.13

package/README.md

@@ -6,7 +6,7 @@
 
 [![npm](https://img.shields.io/npm/v/@ericrisco/rsc?color=63d68a&labelColor=12161c&label=npm)](https://www.npmjs.com/package/@ericrisco/rsc)
 [![downloads](https://img.shields.io/npm/dm/@ericrisco/rsc?color=63d68a&labelColor=12161c&label=downloads)](https://www.npmjs.com/package/@ericrisco/rsc)
-[![skills](https://img.shields.io/badge/skills-270-63d68a?labelColor=12161c)](#the-catalog)
+[![skills](https://img.shields.io/badge/skills-271-63d68a?labelColor=12161c)](#the-catalog)
 [![license](https://img.shields.io/badge/license-MIT-63d68a?labelColor=12161c)](LICENSE)
 [![stars](https://img.shields.io/github/stars/ericrisco/rsc-harness?color=63d68a&labelColor=12161c)](https://github.com/ericrisco/rsc-harness/stargazers)
 
@@ -376,7 +376,7 @@ $ rsc onboard
  ██████╗ ███████╗ ██████╗     ← animated gradient wordmark
  ██╔══██╗██╔════╝██╔════╝
  ██████╔╝███████╗██║
-  270 skills · one CLI · zero bloat
+  271 skills · one CLI · zero bloat
 
 How should I talk to you?
 What are you building or running?
@@ -698,7 +698,7 @@ just asks in plain language.
 
 ## The catalog
 
-270 skills, grouped by what you're trying to do. Click any skill to read its
+271 skills, grouped by what you're trying to do. Click any skill to read its
 `SKILL.md`. It fires on its own when a task matches.
 
 ### 🧭 Core & control plane
@@ -770,7 +770,7 @@ Each with a `02-DOCS` feedback loop that learns from your own results. `remotion
 
 ### 🔌 Connect & automate
 
-[stripe](skills/stripe/) · [email-connector](skills/email-connector/) · [google-workspace](skills/google-workspace/) · [notion-connector](skills/notion-connector/) · [whatsapp-telegram](skills/whatsapp-telegram/) · [automation-flows](skills/automation-flows/) · [api-connector-builder](skills/api-connector-builder/) · [webhooks](skills/webhooks/) · [data-scraper](skills/data-scraper/) · [spreadsheet-ops](skills/spreadsheet-ops/) · [calendar-scheduling](skills/calendar-scheduling/) · [document-processing](skills/document-processing/) · [e-signature](skills/e-signature/)
+[connect-tool](skills/connect-tool/) · [stripe](skills/stripe/) · [email-connector](skills/email-connector/) · [google-workspace](skills/google-workspace/) · [notion-connector](skills/notion-connector/) · [whatsapp-telegram](skills/whatsapp-telegram/) · [automation-flows](skills/automation-flows/) · [api-connector-builder](skills/api-connector-builder/) · [webhooks](skills/webhooks/) · [data-scraper](skills/data-scraper/) · [spreadsheet-ops](skills/spreadsheet-ops/) · [calendar-scheduling](skills/calendar-scheduling/) · [document-processing](skills/document-processing/) · [e-signature](skills/e-signature/)
 
 ### ⚙️ Automation
 

package/manifest.json

@@ -1,7 +1,7 @@
 {
-  "version": "3.0.12",
+  "version": "3.0.13",
   "counts": {
-    "skills": 270,
+    "skills": 271,
     "agents": 34,
     "commands": 53,
     "fixedCommands": 20
@@ -810,6 +810,35 @@
       ],
       "profiles": []
     },
+    {
+      "id": "connect-tool",
+      "description": "Use when the user names a specific tool to connect to the agent (an ERP, accounting or desktop program, CRM, WhatsApp, a spreadsheet, a database): research its real docs, choose the safest route, build `01-TOOLS/<TOOL>/` with a test that proves it, and guide the user. NOT a full typed API client (that is `api-connector-builder`), NOT a whole-workspace tooling scan (that is `harness`).",
+      "tags": [
+        "connect",
+        "integration",
+        "erp",
+        "legacy",
+        "desktop",
+        "database",
+        "read-only",
+        "mcp",
+        "api",
+        "export",
+        "least-privilege",
+        "onboarding"
+      ],
+      "recommends": [
+        "harness",
+        "api-connector-builder",
+        "automation-strategy",
+        "automation-flows"
+      ],
+      "profiles": [
+        "minimal",
+        "core",
+        "full"
+      ]
+    },
     {
       "id": "constitution",
       "description": "Use when setting or amending a project's non-negotiables — stack canon, quality bars, conventions, security/a11y floors — as numbered, testable rules later phases obey. First rsc-sdd phase; writes 02-DOCS/wiki/sdd/constitution.md. NOT a feature spec (that is `specify`), NOT the technical plan (that is `plan`), NOT the wiki itself (that is `harness`).",
@@ -2293,7 +2322,8 @@
         "knowledge"
       ],
       "recommends": [
-        "init"
+        "init",
+        "connect-tool"
       ],
       "profiles": [
         "minimal",

package/package.json

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

package/scripts/lib/default-skill-floor.js

@@ -10,7 +10,11 @@
 // routes ordinary work to `../ftd/SKILL.md`, so a harness without it has a default
 // lane that points at nothing. Membership of every profile was not enough — a
 // declaration written before the skill existed never gains it (see `syncInstalled`).
-export const DEFAULT_SKILL_FLOOR = Object.freeze(['orient', 'suggest', 'unslop', 'ftd']);
+//
+// `connect-tool` joined in 3.0.13 (issue #303): rsc ships no ready-made connections, so "connect my
+// Holded" is answered by a method, not a list, and that method has to be there the first time the
+// user asks, in any kind of project. Like `unslop`, only its description is paid for on other turns.
+export const DEFAULT_SKILL_FLOOR = Object.freeze(['orient', 'suggest', 'unslop', 'ftd', 'connect-tool']);
 
 export function withDefaultSkillFloor(skillIds = []) {
   return [...new Set([...DEFAULT_SKILL_FLOOR, ...skillIds])];

package/scripts/lib/domains.js

@@ -11,7 +11,7 @@ export const DOMAINS = [
   { title: 'Legal, privacy & compliance', ids: ['gdpr-privacy', 'terms-conditions', 'compliance', 'data-policy', 'ip-trademark'] },
   { title: 'Market & brand', ids: ['marketing', 'seo-geo', 'content-engine', 'social-publisher', 'brand-voice', 'brand-identity', 'newsletter', 'landing-copy', 'ads', 'article-writing', 'case-studies', 'video-shorts', 'podcast', 'market-research', 'competitor-watch', 'press-kit', 'community', 'webinar', 'review-management'] },
   { title: 'Grow a channel (YouTube / TikTok / Reels / LinkedIn / Medium)', ids: ['youtube-api', 'youtube-strategy', 'youtube-ideation', 'youtube-thumbnails', 'youtube-packaging', 'remotion-video', 'tiktok-api', 'instagram-api', 'shortform-strategy', 'shortform-ideation', 'shortform-packaging', 'shortform-editing', 'viral-score', 'linkedin-api', 'linkedin-strategy', 'linkedin-content', 'linkedin-carousels', 'linkedin-outreach', 'medium-writing', 'medium-publishing', 'medium-strategy'] },
-  { title: 'Connect & automate', ids: ['stripe', 'email-connector', 'google-workspace', 'notion-connector', 'whatsapp-telegram', 'automation-flows', 'api-connector-builder', 'webhooks', 'data-scraper', 'spreadsheet-ops', 'calendar-scheduling', 'document-processing', 'e-signature'] },
+  { title: 'Connect & automate', ids: ['connect-tool', 'stripe', 'email-connector', 'google-workspace', 'notion-connector', 'whatsapp-telegram', 'automation-flows', 'api-connector-builder', 'webhooks', 'data-scraper', 'spreadsheet-ops', 'calendar-scheduling', 'document-processing', 'e-signature'] },
   { title: 'Automation platforms', ids: ['automation-strategy', 'n8n', 'make', 'zapier', 'power-automate'] },
   { title: 'Data & analytics', ids: ['analytics', 'dashboard', 'kpi-framework', 'reporting', 'ab-testing', 'forecasting', 'data-cleaning', 'business-intelligence'] },
   { title: 'AI — build it in', ids: ['building-agents', 'rag', 'embeddings-search', 'prompt-engineering', 'llm-pipeline', 'agent-eval', 'chatbot', 'ai-media', 'replicate-images', 'structured-extraction', 'agent-safety', 'cost-tracking'] },

package/skills/connect-tool/SKILL.md

@@ -0,0 +1,173 @@
+---
+name: connect-tool
+description: "Use when the user names a specific tool to connect to the agent (an ERP, accounting or desktop program, CRM, WhatsApp, a spreadsheet, a database): research its real docs, choose the safest route, build `01-TOOLS/<TOOL>/` with a test that proves it, and guide the user. NOT a full typed API client (that is `api-connector-builder`), NOT a whole-workspace tooling scan (that is `harness`)."
+tags: [connect, integration, erp, legacy, desktop, database, read-only, mcp, api, export, least-privilege, onboarding]
+recommends: [harness, api-connector-builder, automation-strategy, automation-flows]
+profiles: [minimal, core, full]
+origin: risco
+---
+
+# Connect a tool: research it, pick the safe route, prove it works
+
+The user said *"connect my Holded"*, *"can the agent read our Sage?"*, *"hook up WhatsApp"*. This
+skill turns that sentence into a working, documented connection in `01-TOOLS/<TOOL>/`, for **any**
+tool: the ones with a modern API, and the program installed on an office PC fifteen years ago.
+
+rsc ships no ready-made connections. Every project builds only the ones its user asks for, so the
+method matters more than any list of vendors: **find the truth, take the least dangerous route,
+prove it, leave it written down.**
+
+## Before anything: what does the user want to do?
+
+Ask only what the docs cannot answer, in plain words (`technical_level` in
+`02-DOCS/wiki/harness/user-profile.md` sets the register):
+
+- **Which product, exactly?** Name, edition, version. "Sage" is five different products.
+- **Where does it run?** In the cloud (a website they log into) or installed on a computer or
+  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
+
+Look it up every time, even for a tool you "know": plans, endpoints and MCP servers change monthly.
+In this order, stopping when the route is clear:
+
+1. **The vendor's own developer docs**: search `<product> API`, `<product> developers`,
+   `<product> MCP`. Prefer the vendor domain over blog posts.
+2. **The official MCP registry** (`registry.modelcontextprotocol.io`) and the vendor's docs for an
+   official MCP server. An official, read-only MCP is often the fastest safe route.
+3. **Library docs** through Context7 when the route is an SDK.
+4. **Export and import features** in the product's user manual: scheduled CSV/Excel exports, FTP
+   drops, official import file formats.
+5. **Where the data lives** for installed software: the vendor's installation guide, the database
+   engine it installs (often SQL Server Express, sometimes Access, Firebird or MySQL).
+
+Write every source into the tool's `README.md` with its URL and the date you read it. **If you find
+nothing reliable, say so** and stop at a question for the vendor; an invented endpoint costs the
+user a week.
+
+## 2. Choose the route: the least dangerous one that does the job
+
+| Route | Use when | Watch for |
+|---|---|---|
+| Official MCP server | The vendor publishes one | Start it read-only if it offers the mode |
+| Official API | Documented REST/GraphQL with scoped tokens | Request read scopes only; full client work goes to `api-connector-builder` |
+| Built-in integration (OAuth app, Zapier/Make/n8n connector) | No API for you, but a supported integration exists | The integration's permissions, not yours, are the ceiling |
+| Scheduled export | The program can export CSV/Excel or drop files to a folder | Freshness is the export schedule, say so |
+| Read-only copy of the database | Installed software with no API and no export | See *Desktop programs* below; never the live database |
+| Screen automation (RPA) | Nothing else exists | Last resort: fragile and breaks on every update |
+
+**Connect, or migrate?** If every route above is poor and the program is near end-of-life, or new
+legal requirements (Spanish e-invoicing, Veri\*factu) will force a change anyway, say so plainly
+and hand the decision to `automation-strategy`. Check the current dates at the tax authority's
+site: they have moved before.
+
+## 3. Least privilege, always
+
+- **Read first.** Every connection starts read-only, even when the goal is writing.
+- **Writing is explicit.** Only when the user asks for it, only through the vendor's API or its
+  official import format, and only for the objects named.
+- **Never write directly into a desktop program's database.** It bypasses the program's own
+  rules, voids support contracts, and can corrupt accounting. Generate the program's official
+  import file instead, and a person imports it.
+- **Secrets stay in `.env`** (gitignored, `chmod 600`). Never in the repo, never in `02-DOCS`.
+
+## 4. Build it in `01-TOOLS/<TOOL>/`
+
+Copy `01-TOOLS/_TEMPLATE/` to `01-TOOLS/<TOOL>/` (uppercase id, e.g. `HOLDED`, `SAGE_50`) and fill
+every file: `.env.example` with the real variable names, `CREDENTIALS.md` with where each one is
+generated and how to rotate it, `README.md` with the route, the sources and their dates, and the
+permissions granted. Add a row to `01-TOOLS/README.md`.
+
+**`test_connection` is the proof, not a formality.** It makes one cheap read and prints
+`OK — …`. When the connection is meant to be read-only, it must also **prove that writing fails**,
+because a read-only promise nobody tested is not one:
+
+```bash
+# PostgreSQL: a write must fail with a PERMISSION error. Any other error (wrong host, bad password)
+# proves nothing, so it fails the test too instead of passing as "refused".
+out=$(psql "$DATABASE_URL" -v ON_ERROR_STOP=1 -c "BEGIN; CREATE TABLE rsc_write_probe(i int); ROLLBACK;" 2>&1) \
+  && { echo "FAIL — this user can write" >&2; exit 1; }
+grep -qiE "permission denied|read-only transaction" <<<"$out" \
+  && echo "OK — writes refused" || { echo "FAIL — unexpected error: $out" >&2; exit 1; }
+```
+
+```bash
+# SQL Server: insert into one of the views you exposed; only error 229 (permission denied) passes.
+out=$(sqlcmd -S "$MSSQL_HOST" -U "$MSSQL_USER" -P "$MSSQL_PASSWORD" -d "$MSSQL_DB" -b \
+  -Q "BEGIN TRAN; INSERT INTO rsc_views.customers DEFAULT VALUES; ROLLBACK;" 2>&1) \
+  && { echo "FAIL — this user can write" >&2; exit 1; }
+grep -q "Msg 229" <<<"$out" && echo "OK — writes refused" || { echo "FAIL — unexpected error: $out" >&2; exit 1; }
+```
+
+For an API, prove it through the token itself: list its scopes from the vendor's token endpoint
+or dashboard and fail when a write scope is present. Never fire a real write to "see what happens".
+
+## Desktop programs and old ERPs
+
+Most small-business software was never meant to be connected. The safe pattern:
+
+1. **Find the data.** The vendor's install guide, the Windows ODBC data sources, or the SQL Server
+   instance the program installed (often `.\SQLEXPRESS`). Access files are `.mdb`/`.accdb`.
+2. **Work on a copy, never the live database.** A nightly copy, off business hours. SQL Server
+   Express has no Agent: schedule `sqlcmd` with a `BACKUP DATABASE` from the Windows Task
+   Scheduler and restore it where the agent reads. Access: copy the file, then convert or read it
+   with `mdbtools` (`mdb-tables`, `mdb-export`).
+3. **A dedicated reader.** A login that can only `SELECT`, ideally only on a schema of views that
+   expose what is needed:
+
+   ```sql
+   CREATE LOGIN ia_reader WITH PASSWORD = '<from .env>';
+   CREATE USER ia_reader FOR LOGIN ia_reader;
+   GRANT SELECT ON SCHEMA::rsc_views TO ia_reader;
+   ALTER ROLE db_denydatawriter ADD MEMBER ia_reader;
+   ```
+
+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. 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.
+```
+
+## 6. Leave it written down
+
+Record the connection in `02-DOCS` following the `harness` wiki protocol: what is connected, the
+route, the permissions, who owns the credentials, and the date. The next session, or a colleague,
+reads it instead of starting over.
+
+## Anti-patterns
+
+| If you are about to… | Do instead |
+|---|---|
+| Write the endpoint from memory | Read the vendor docs now and cite them with a date |
+| Connect with an admin account "to get started" | Create the read-only user first; it costs ten minutes |
+| Write into the program's database because it is quicker | Generate its official import file |
+| Point the agent at the live database | Read a nightly copy |
+| Call the connection done because it authenticates | Run the test; for read-only, watch the write fail |
+| Promise the vendor has an API or MCP | Say what you found, with links, or that you found nothing |
+| Build the whole typed client here | Hand it to `api-connector-builder` once the route is chosen |
+
+## See also
+
+- `../harness/SKILL.md`: owns `01-TOOLS/` and `02-DOCS/` as a whole.
+- `../api-connector-builder/SKILL.md`: auth, pagination and retries once an API is the route.
+- `../automation-strategy/SKILL.md`: whether to connect, migrate or automate at all.
+- `../automation-flows/SKILL.md`: chaining the connected tool into a workflow.
+
+## Orientación (siempre)
+
+Habla con la voz de `orient`: frases cortas, una idea por frase, y cada respuesta se entiende sola. Registro técnico o con analogías según `technical_level` en `02-DOCS/wiki/harness/user-profile.md`. Cierra cada turno con el **bloque-brújula** (📍 dónde estás · ➡️ siguiente, terminando en pregunta; ✅ y 🧭 cuando hay algo hecho o decidido). **Nunca termines en seco.** Protocolo completo: skill `orient` → `skills/orient/references/orientation-contract.md`. (Defiere a `suggest` el "¿instalo la skill que falta?".)

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

@@ -0,0 +1,58 @@
+skill: connect-tool
+
+# Cases for connect-tool: the user names ONE tool to connect to the agent. The skill researches the
+# vendor's real docs, picks the least dangerous route (MCP, API, integration, export, read-only copy
+# of the database, RPA last), builds 01-TOOLS/<TOOL>/ with a test that proves it (and proves writes
+# fail when read-only), guides the user and records it in 02-DOCS. It is NOT the typed API client
+# (api-connector-builder), NOT the whole-workspace scan (harness), NOT whether to automate a process
+# (automation-strategy), NOT chaining services (automation-flows).
+
+should_trigger:
+  - prompt: "Quiero que el agente lea las facturas de Holded para hacerme un resumen de cobros cada lunes."
+    why: "A named cloud tool and a read goal. The route (official API with read scopes, or an MCP if the vendor has one) must come from Holded's current docs, then a 01-TOOLS/HOLDED/ folder with a read test."
+
+  - prompt: "Tenemos Sage 50 instalado en el ordenador de la oficina. ¿Puede el agente leer los clientes?"
+    why: "Desktop software with no public API: the legacy pattern, find where the data lives, read a nightly copy with a SELECT-only login, never the live database, and ask the distributor first."
+
+  - 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: "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."
+
+  - prompt: "¿Se puede conectar InstalWin? No sé ni por dónde empezar."
+    why: "An obscure vertical program nobody has catalogued: the method (search vendor docs, export features, the database it installs) works for it, and if nothing reliable exists the skill says so."
+
+should_not_trigger:
+  - prompt: "Write a TypeScript client for the Holded API with pagination, retries and token refresh."
+    route_to: "api-connector-builder"
+    why: "The route is already decided; what remains is building a robust typed client, which is that skill's job."
+
+  - prompt: "Set up 01-TOOLS and 02-DOCS for this whole repo and detect every provider we use."
+    route_to: "harness"
+    why: "A whole-workspace scan and layout, not one named tool."
+
+  - prompt: "¿Merece la pena automatizar la conciliación bancaria o la seguimos haciendo a mano?"
+    route_to: "automation-strategy"
+    why: "Whether to automate a process at all; no tool is being connected yet."
+
+  - prompt: "When a Stripe payment lands, create the invoice in Holded and post it to Slack."
+    route_to: "automation-flows"
+    why: "Chaining already-connected services into a workflow, not establishing one connection."
+
+  - prompt: "We need to receive Stripe webhooks and verify their signatures."
+    route_to: "webhooks"
+    why: "Inbound callbacks into our own service, not connecting the agent to an outside tool."
+
+capability:
+  - scenario: "A non-technical user says: 'Usamos A3 en un servidor de la oficina, lo lleva una gestoría. Quiero que el agente me diga qué clientes deben dinero.' Show what the agent does from the first answer to the end."
+    must_include:
+      - "Asks only what the docs cannot answer (edition, where it runs, who administers it) and confirms the goal is reading, not writing"
+      - "Researches the vendor's current documentation and cites sources with dates, or says plainly that nothing reliable was found"
+      - "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"

package/skills/harness/SKILL.md

@@ -2,7 +2,7 @@
 name: harness
 description: "Use when governing a workspace's control plane, code or not — the `01-TOOLS/` tooling layer, the `02-DOCS/` chaos→knowledge wiki, the root Knowledge map. Audits it, migrates legacy `XX-*` folders, scaffolds provider tooling, sweeps the inbox, writes root CLAUDE.md/AGENTS.md. NOT the bootstrap front door (that is `init`, which hands off here)."
 tags: [harness, company, ops, docs, wiki, connect, tools, knowledge]
-recommends: [init]
+recommends: [init, connect-tool]
 profiles: [minimal, core, full]
 origin: risco
 ---
@@ -81,7 +81,7 @@ for harness-level choices, but defer concrete deploy mechanics to `deployment`,
 
 The skill proposes, the user confirms, the skill executes. Every destructive operation (deleting a legacy folder, merging into an existing `CLAUDE.md`) requires explicit consent quoted back from the user, not inferred.
 
-**Out of scope:** adding a single tool — the user does `cp -r 01-TOOLS/_TEMPLATE 01-TOOLS/<X>` manually, no need for the full protocol; and refactoring runtime code — this skill is operational tooling only, never runtime.
+**Out of scope:** adding a single tool the user names — that is `../connect-tool/SKILL.md`, which researches the tool and builds `01-TOOLS/<X>/` from the template; and refactoring runtime code — this skill is operational tooling only, never runtime.
 
 ## Protocol — five phases
 
@@ -152,7 +152,7 @@ Execute in this exact order. Each step writes to disk; abort and report on first
    - Same logic for `AGENTS.md`, rendered from `references/agents-md-template.md`.
 2. **Create `01-TOOLS/` skeleton.**
    - Create `01-TOOLS/` directory.
-   - Copy `assets/_TEMPLATE/` to `01-TOOLS/_TEMPLATE/`. The asset ships its ignore rules as `gitignore` (no leading dot, because npm never packages a `.gitignore`) and it must land as `.gitignore`; the installer already does this on every apply, so normally you will find the directory built. This template is **generic boilerplate with placeholders (`<NOMBRE_TOOL>`, `<TOOL>_API_KEY`)**. The user copies it manually when adding a tool NOT in the catalog. The skill itself does NOT use `_TEMPLATE/` to generate the detected tools — those come from `providers.yaml`.
+   - Copy `assets/_TEMPLATE/` to `01-TOOLS/_TEMPLATE/`. The asset ships its ignore rules as `gitignore` (no leading dot, because npm never packages a `.gitignore`) and it must land as `.gitignore`; the installer already does this on every apply, so normally you will find the directory built. This template is **generic boilerplate with placeholders (`<NOMBRE_TOOL>`, `<TOOL>_API_KEY`)**. `../connect-tool/SKILL.md` copies it when the user asks for a tool NOT in the catalog. The skill itself does NOT use `_TEMPLATE/` to generate the detected tools — those come from `providers.yaml`.
 3. **Per detected tool** (in catalog order):
    - Create `01-TOOLS/<ID>/`.
    - Write every file from the provider entry's `files:` map verbatim (replacing template variables: `{{TOOL_ID}}`, `{{DASHBOARD_URL}}`, etc.).
@@ -279,7 +279,7 @@ Opt out of the size nudge with `.rsc/.no-claudemd-check`.
 The consent, merge and `.env` rules live with the phases that enforce them above. These four are
 scope rules that no single phase owns, and breaking one destroys something the user cannot get back:
 
-1. **No speculative tools.** A tool is created if and only if the detector found evidence in the user's code. No "we should probably have a Sentry tool too".
+1. **No speculative tools.** A tool is created only when there is evidence: the detector found it in the user's code, or the user asked for it by name (then `../connect-tool/SKILL.md` builds it). No "we should probably have a Sentry tool too".
 2. **Idempotent.** Running the skill twice produces no extra side effects. Re-scanning a project already canonical detects "nothing to do".
 3. **Out-of-scope dirs are invisible.** `node_modules/`, `.venv/`, `.next/`, `__pycache__/`, `.git/`, `dist/`, `build/`, `.dart_tool/` are never read for detection and never touched.
 4. **Subproject internals are out of scope.** `.env.example`, `requirements.txt`, `package.json`, source files inside subprojects are READ for detection only. They are NEVER moved, renamed, modified, or deleted. The skill operates exclusively on workspace-root artifacts (`CLAUDE.md`, `AGENTS.md`, `01-TOOLS/`, `02-DOCS/`, and `XX-*` legacy folders at the root level).