← ClaudeAtlas

uremot-connectionslisted

Use connections and variables on Uremot without exposing them. Use when a command needs a repository, model or service credential or a named value, to learn what is in reach and how a program uses it, and when a harness needs a person to sign in.
uremot/skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill uremot/skills
# Uremot connections and variables A connection is an account or key with a provider Uremot knows how to use, which a person linked: a GitHub App installation, a model sign-in or a provider's API key. A variable is a named value with no fixed use, such as `MONITOR_TOKEN`, plain or secret. Values are never shown to you in a listing, and you never show them to anyone. ## What is in reach - `list_connections` names the connections and variables in reach and how a program inside an Instance uses each, never a value. Its name stays, though it lists both. - Inside an Instance, `uremot var list` lists what it can read, with each one's usage instructions. An agent, and the machine it runs on, can reach every connection and variable its person can, not only the one it runs on. ## Using one Read a value only into the one command that needs it, as `uremot var list` says: ```sh uremot var get <name> ``` `gh` and `glab` need nothing installed: on a Uremot desktop each is fetched and verified at first use. Give one a repository connection the same way: `GH_TOKEN=$(uremot var get <name>) gh ...`, `GITLAB_TOKEN=$(uremot var get <name>) glab ...`. `git` needs no command at all: its credential helper asks the platform for each repository. Never print the environment (`env`, `printenv`, a screenshot of either): it holds credentials too. Never put a value in output, chat, command arguments, files, images or commits, and never ask anyone to paste one into chat. A program that cannot as