replicas-agent
Guide for background coding agents running inside Replicas cloud workspaces
What this skill does
# 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 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 (in-workspace CLI) Take action *with* Replicas itself — manage automations, environments (variables, files), repos, and `replicas.json` config — using the pre-installed, pre-authenticated `replicas` CLI. **Reference:** `references/REPLICAS.md` Use this when: - The user asks you to create, edit, run, or delete an automation - The user asks you to manage environments, environment variables, or environment files - The user asks "what envs / repos / automations do I have?" - The user asks you to scaffold a `replicas.json` / `replicas.yaml` in a repo For *questions about how Replicas works* (concepts, pricing, what a feature does), check https://docs.replicas.dev first and only fall back to this skill when the user is asking you to take an action.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.