Skill

ssh-remote-connection

Establishes SSH connections to remote servers for executing commands, checking logs, restarting services, and managing Docker containers via bash scripts.

Docker

Bash

Linux

devops

infrastructure

npx claudepluginhub artwist-polyakov/polyakov-claude-skills --plugin ssh-remote-connection

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Universal skill for connecting to remote servers via SSH.

Supporting Assets

scripts/connect.sh

SKILL.md

Similar Skills

cache-components

139.2k

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

canvas-design

124.2k

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

20 files

anthropics-skills-13

Stats

Parent Repo Stars80

Parent Repo Forks23

Last CommitJan 11, 2026

Actions

View Source View Plugin View on GitHub View README

Tags

SSH Remote Connection

Universal skill for connecting to remote servers via SSH.

Usage

# Interactive shell scripts/connect.sh # Run command directly scripts/connect.sh "docker compose logs backend --tail 50"

Setup

For Claude Code (local)

Copy config template:

cp config/.env.example config/.env

Fill in config/.env with actual values

Make script executable:

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_KEY_PATH — path to private key

SSH_KEY_PASSWORD — key passphrase (optional)

SERVER_PROJECT_PATH — project directory on server

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

# 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"