ssh-remote-connection
SSH connection to remote servers. Use when you need to execute commands on a remote server, check logs, restart services, or manage Docker containers.
What this skill does
# SSH Remote Connection Universal skill for connecting to remote servers via SSH. ## Usage ```bash # Interactive shell scripts/connect.sh # Run command directly scripts/connect.sh "docker compose logs backend --tail 50" ``` ## Setup ### For Claude Code (local) 1. Copy config template: ```bash cp config/.env.example config/.env ``` 2. Fill in `config/.env` with actual values Key-based authentication: ```bash SSH_HOST=your-server.example.com SSH_USER=ubuntu SSH_AUTH_METHOD=key SSH_KEY_PATH=/absolute/path/to/private/key SSH_KEY_PASSWORD= SERVER_PROJECT_PATH=/path/to/project ``` Password-based authentication: ```bash SSH_HOST=your-server.example.com SSH_USER=ubuntu SSH_AUTH_METHOD=password SSH_PASSWORD='your account password' SERVER_PROJECT_PATH=/path/to/project ``` 3. Make script executable: ```bash chmod +x scripts/connect.sh ``` ### For Cloud Runtime Set environment variables in your cloud configuration: - `SSH_HOST` — server hostname or IP - `SSH_USER` — SSH username - `SSH_PORT` — SSH port (optional) - `SSH_AUTH_METHOD` — `auto`, `key`, or `password` (optional, defaults to `auto`) - `SSH_KEY_PATH` — path to private key for key authentication - `SSH_KEY_PASSWORD` — key passphrase (optional) - `SSH_PASSWORD` — SSH account password for password authentication - `SERVER_PROJECT_PATH` — project directory on server For password authentication, the local runtime must have either `sshpass` or `expect`. If the host key is not trusted yet, connect once manually or add the host to `known_hosts` before running non-interactive commands. ## Important Notes - **Git operations**: Do NOT run `git pull` on the server. User will handle git sync manually. - **Code location**: Code is in a private repo, changes must be pushed first then pulled by user. - **Docker**: Use `docker compose` (not `docker-compose`) on the server. ## Example Commands ```bash # View logs scripts/connect.sh "docker compose logs backend --tail 100" # Restart service scripts/connect.sh "docker compose restart backend" # Rebuild and restart scripts/connect.sh "docker compose build backend && docker compose up -d backend" # Check status scripts/connect.sh "docker compose ps" ```
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.