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.

Two paths, always in this order:

1. Documentation first. Most tools have an API, an MCP server or a manual that says how to get data out. Research finds it and the route follows (sections 1–2).
2. No documentation: option 2. Only when the program has no API, no MCP and no usable docs. The skill does not stop there: it works out what kind of program it is and who holds the key, and keeps going (section 3).

Before anything: what does the user want to do?