connect-tool SKILL.md skillA
connect-tool from ericrisco/rsc-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ericrisco/rsc-harness/connect-tool@git:20261010.5791966Pins git:20261010.5791966 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ericrisco/rsc-harness
- Path
skills/connect-tool/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261010.5791966, committed Oct 10, 2026
- First version recorded
- Oct 9, 2026
- Size
- 9,838 bytes
- Repository stars
- 236
- License
- MIT
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`).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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). ## 1. Research: the docs decide, never memory …
Read the whole file at its exact version.
How to install
mdr add ericrisco/rsc-harness/connect-tool@sha256:7f995e0c75c749d5The line at the top of this page pins the label git:20261010.5791966, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ug46m3x3rso2s4es)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 9, 2026 and Oct 10, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261010.5791966 latest | 2026-10-10 | 5791966 | 9,838 B | A | view · diff |
| git:20261009.1f8d9bb | 2026-10-09 | 1f8d9bb | 10,500 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9838 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
ericrisco/rsc-harness · 236 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ug46m3x3rso2s4es GET https://markdownregistry.com/api/v1/resolve?ref=ericrisco/rsc-harness/connect-tool GET https://markdownregistry.com/api/v1/blob/7f995e0c75c749d5c4b4170bcbdbbe8247e55c85aad5a7bb9849c1df6fe5c1a5
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from ericrisco/rsc-harness
Every file in ericrisco/rsc-harness