Replicas Agent

# Docker

Docker is pre-installed in Replicas workspaces, but the daemon does **not** auto-start. You must start it manually before running any `docker` or `docker compose` commands.

## Starting the Docker Daemon

```bash
sudo service docker start
```

After starting, verify the daemon is running:

```bash
docker info
```

## Important Notes

- **Start once per session.** The daemon stays running until the workspace shuts down. You do not need to restart it between commands.
- **Check before starting.** If you are unsure whether the daemon is already running, check first to avoid an unnecessary restart:
  ```bash
  docker info > /dev/null 2>&1 || sudo service docker start
  ```
- **Sudo is required** for starting the daemon, but regular `docker` commands run without sudo (the user is in the `docker` group).


name: Validate Skill

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

jobs:
  validate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - uses: actions/setup-node@v4
        with:
          node-version: "20"

      - name: Install skill
        run: npx skills add . --all --global -y


---
name: replicas-agent
description: Guide for background coding agents running inside Replicas cloud workspaces
---

# Replicas Agent

You are a background coding agent running inside a Replicas cloud workspace (a remote VM). This skill covers capabilities and best practices specific to this environment.

## Capabilities

This skill provides detailed guides for the following capabilities. **Read the relevant reference file before performing any of these actions.**

### Previews
Expose locally running services (web apps, APIs, databases) as public preview URLs so humans can interact with them directly.

**Reference:** `references/PREVIEWS.md`

Use this when:
- You need to start a service that a human should view or interact with
- The task involves UI work that benefits from human review
- You are verifying frontend/backend integrations visually

### Slack
Send messages, read threads, search conversations, and upload files via the Slack Web API.

**Reference:** `references/SLACK.md`

Use this when:
- You need to send a message to a Slack channel or thread
- You need to read or fetch a Slack conversation
- You encounter a Slack message link and need to retrieve its content
- The task asks you to notify, update, or communicate via Slack

### Linear
Fetch issues, update state, add comments, and search via the Linear GraphQL API.

**Reference:** `references/LINEAR.md`

Use this when:
- You encounter a Linear issue link and need to understand the task
- You need to update an issue's state (e.g. mark as done)
- You need to comment on or search for Linear issues

### GitHub
Use the pre-authenticated `gh` CLI for pull requests, issues, actions, and API calls.

**Reference:** `references/GITHUB.md`

Use this when:
- You need to create, review, or manage pull requests
- You need to interact with GitHub issues or actions
- You need to use the GitHub API for advanced operations
- You need to include images in PR descriptions

### Google Workspace (Docs, Sheets, Forms, Drive)
Create and edit Google Docs, Sheets, and Forms via the Replicas gateway. Files are owned by Replicas — the integration cannot access pre-existing Google content created outside of it.

**Reference:** `references/GOOGLE.md`

Use this when:
- You need to create or edit a Google Doc, Sheet, or Form
- You need to share, rename, move, or delete a Replicas-created Google file
- You need to read responses from a Replicas-created Google Form

### Docker
Start and use the Docker daemon in Replicas workspaces. Docker is pre-installed but the daemon does not auto-start.

**Reference:** `references/DOCKER.md`

Use this when:
- You need to run `docker` or `docker compose` commands
- You need to build or run Docker containers
- Your task involves containerized services or Docker-based workflows

### Media
Share screenshots, screen recordin