← ClaudeAtlas

uremot-agentslisted

Hire and manage agents on Uremot. Use when your work needs another environment or another agent, to choose its App, machine, harness, provider and sign-in, hire it once with its first message, give it work in chat, handle an uncertain hire, change its profile, and stop or retire it.
uremot/skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill uremot/skills
# Uremot agents An App is a kind of environment, an agent is an individual, and its desk is the Instance it works in. One agent has one desk. More capacity means more agents, each hired once. ## Before hiring Hire only when this environment cannot do the work. To operate a database or an application yourself, launch it with `launch_instance` instead (`uremot guide apps`). 1. `list_apps`: choose the App from its description, instructions, version, publisher and variants. A marketplace listing (`source` `marketplace`) runs its publisher's image with the agent's credential. 2. `list_computes`: choose a machine your person owns, by its labels. 3. `list_connections`: the model connection it signs in with, by name, when it needs one. An agent and the machine it runs on can reach every connection its person can, not only that one: choose the App and machine with that in mind. ## Hiring `hire_agent`, or `uremot agent hire` in a shell, creates the agent and its desk in one step: - its name, and its `desk`: the machine (`compute_id`), the App (`app_id` or `listing_id`) and the `variant_id`, and optionally its `size`, one the machine's `sizes` in `list_computes` names; - what it runs on: `harness` (`claude-code`, `codex` or `opencode`), the model `provider` (`anthropic`, `openai`, `zai`, `openrouter` or `google`) and how it signs in, `auth`: `key`, an API key `connection` of that provider; or `subscription`, a Claude Code subscription-token `connection`, or Codex's