Substitute em dashes with colons in definition lists and commas/semicolons inline. Touches only the org-setup skill files modified on this branch. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
5.8 KiB
name, description
| name | description |
|---|---|
| replicas-agent | 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
dockerordocker composecommands - You need to build or run Docker containers
- Your task involves containerized services or Docker-based workflows
Media
Share screenshots, screen recordings, generated diagrams, and audio clips inline in the Replicas chat (and as references in external messages).
Reference: references/MEDIA.md
Use this when:
- You produce a screenshot, recording, generated image, or audio clip the user should see
- You record video output (browser automation, screen capture), including the recommended aspect ratio and FPS
- You need to embed media in a Slack/Linear/GitHub message AND keep a referenceable copy in the Replicas dashboard
Replicas CLI (overview)
The umbrella for the pre-installed, pre-authenticated replicas CLI. Prerequisites, whoami, repos, replicas.json / init, when-not-to-use, common errors, and an index pointing at topical refs below.
Reference: references/REPLICAS.md
Use this when:
- You need to verify auth or list repos
- The user asks to scaffold a
replicas.json/replicas.yamlin a repo - You want to know which topical reference covers a given action
For general questions about how Replicas works (concepts, pricing, what a feature does), check https://docs.tryreplicas.com first. For taking action, use the replicas CLI and the topical refs; never WebFetch in place of running a CLI command.
Environments
Self-contained guide to environments: env vars, env files, warm pool, warm hook, skills, MCPs, configuration. Concepts + CLI + agent-behavior playbooks + env-specific block protocols (:::secure-input, :::add-skills-mcps) + dashboard URLs + edge cases.
Reference: references/ENVIRONMENT.md
Use this when:
- The user asks to create/edit/delete an environment
- The user asks to add/edit/delete an env variable or env file
- The user asks about warm pools, warm hooks, skills, or MCPs
- The user asks about an environment's configuration / system prompt
- The user asks "what envs / variables / files do I have?"
Org configuration (non-env)
Shared agent rules (block emit, secrets, tone, state-adaptation), cross-cutting block protocols (:::confirm-action, :::connect-integration, :::automation-templates), and playbooks for the org-level capabilities that aren't env-bound: integrations and automations.
Reference: references/ORG-CONFIG.md
Use this when:
- The user asks to connect Slack, Linear, or Sentry
- The user asks to create, edit, run, or delete an automation
- You need the catalog of valid
:::confirm-actionkinds, or any cross-cutting block protocol - You need the shared hard rules (no secrets in chat, no clarifying-questions-before-the-block, etc.)
Onboarding wizard
Wizard mechanics for the onboarding workspace: step order, the Walk me through this step prompt, pacing. The agent's behavior in onboarding is identical to any other workspace; capability playbooks live in ENVIRONMENT.md and ORG-CONFIG.md, the wizard is just a stepper on top.
Reference: references/ONBOARDING.md
Use this when:
- The current workspace has
workspace.is_onboarding === true - The user clicks "Walk me through this step" on the wizard accordion
- You need the onboarding step order or step ids