replicas-agent — Claude Code skill: what it does, how to install

What replicas-agent does

Inside a Replicas VM the agent needs to know its own toolbox, and this skill is the map. A locally running service can be published behind a public URL, so a person clicks through the UI or calls the API while the agent keeps going. Slack threads, Linear issues, pull requests through the pre-authenticated gh CLI, Google Docs and Sheets, Docker containers, screenshots and recordings each get a section of their own. Every section lives in a file under references/ (PREVIEWS.md, SLACK.md, LINEAR.md, GITHUB.md, GOOGLE.md, DOCKER.md, MEDIA.md, REPLICAS.md), and the agent is meant to read the matching file before touching anything.

Some of it depends on the machine. Docker is installed, yet the daemon does not come up on its own, so docker and docker compose fail until somebody starts it. Google files stay inside Replicas: the gateway owns what it creates, and documents made outside the integration remain out of reach. gh arrives already logged in, so no token setup is needed.

One more part covers the replicas CLI for automations, environment variables and files, repos and replicas.json. When the question is how Replicas itself works, the skill sends the agent to the docs first and saves the CLI for actual changes.