conch: Skill for Cursor

R-Shell SSH Workflow

Use the local r-shell CLI for every remote-server task in this project. Save each server once as a named connection, then always reference it by -c <id|name>. This reuses one clean connect-do-disconnect path with stored credentials, instead of spawning many raw ssh user@ip processes that look like a brute-force/attack to the remote host.

Core Rule

• DO NOT run raw ssh, scp, or sftp to reach a server in this project.
• DO use r-shell subcommands with a saved connection (-c <id|name>).
• On every use of this skill, first run Step 0 (ensure installed) and Step 1 (ensure MCP running), then do the task.

Step 0 — Ensure r-shell is installed (auto-install if missing)

Detect the binary; if absent, build/install it from this repo automatically. Do NOT ask the user — just install it.

# 1. Already installed and on PATH?
if command -v r-shell >/dev/null 2>&1; then
  echo "r-shell: $(command -v r-shell)"
else
  echo "r-shell not found — installing from source"
fi

If missing, install (prefer cargo install, which puts it on PATH via ~/.cargo/bin). Run from the repo root:

# Preferred: installs `r-shell` to ~/.cargo/bin (make sure that's on PATH)
cargo install --path cli

# Fallback if `cargo install` is unavailable/undesired: build in-tree.
# The binary lands at cli/target/release/r-shell
cargo build --release --manifest-path cli/Cargo.toml

• If cargo itself is missing, stop and tell the user to install Rust from https://rustup.rs (do not attempt a silent toolchain install).
• After a fallback build, invoke the binary by its full path cli/target/release/r-shell (or via cargo run --manifest-path cli/Cargo.toml --).

For brevity the rest of this skill writes r-shell <command>; substitute the built path or the Cargo form when r-shell is not yet on PATH.

Step 1 — Ensure the MCP server is running (auto-start)

The skill should make the local MCP server available without manual steps. It binds to http://127.0.0.1:9123/mcp (localhost only).