Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/prinx-deploy-vps
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: devops
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/deploy-vps
What's inside
- Skill name
deploy-vps- Description
- Use when deploying to a VPS via GitHub Actions and Docker.
- License
- MIT
- Instructions
- 137 lines in SKILL.md · view on GitHub
Before installing
- Instructions call the network
- Instructions read files in your home folder (~/.ssh, ~/.aws…)
Files (1)
- SKILL.md
SKILL.md (first lines)
# Deploy VPS
Deploy to a VPS using GitHub Actions and Docker. This is the simplest repeatable setup for VPS deployment: push to GitHub, GitHub Actions builds and deploys.
## Prerequisites
Before starting, confirm:
1. The project has a GitHub repository.
2. The user has a VPS with SSH access.
3. Docker is installed on the VPS (or will be installed).
## Step 1 — Check Docker on VPS
Ask: **Do you have Docker installed on your server?**
Run on the VPS: `docker --version`
If not installed, guide them:
- Ubuntu/Debian: `curl -fsSL https://get.docker.com | sh`
- Then: `sudo usermod -aG docker $USER` (they may need to log out and back in)
## Step 2 — Create Dockerfile
If the project does not have a `Dockerfile`, create one. Keep it simple:
```dockerfile
# Use the smallest appropriate base image
FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci
COPY . .
RUN npm run build
FROM node:20-alpine
WORKDIR /app
COPY --from=builder /app/dist ./dist
COPY --from=builder /app/node_modules ./node_modules
COPY --from=builder /app/package.json ./
EXPOSE 3000
CMD ["node", "dist/index.js"]
```
Adjust for the project's stack (Python, Go, etc.). Ask the user what their project uses if unclear.
## Step 3 — Create GitHub Actions workflow
Create `.github/workflows/deploy.yml`:
```yaml
name: Deploy to VPS
on:
push:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Deploy via SSH
uses: appleboy/ssh-action@v1
with:
host: ${{ secrets.VPS_HOST }}
username: ${{ secrets.VPS_USER }}
key: ${{ secrets.VPS_SSH_KEY }}
script: |
cd /opt/${{ github.event.repository.name }}
git pull
docker compose down
docker compose build
docker compose up -d
```
If the project uses `docker-compose.yml` at the root, this works as-is. If not, suggest a simple one:
```yaml
services:
app:
build: .
ports:
- "3000:3000"
restart: unless-stopped
```
## Step 4 — Set up GitHub secrets
Tell the user to add three secrets in their GitHub repo (Settings > Secrets and variables > Actions):
1. `VPS_HOST` — their server IP or domain
2. `VPS_USER` — the SSH username (e.g. `root` or `deploy`)
3. `VPS_SSH_KEY` — the private SSH key for connecting
For the SSH key, tell them:
- If they already have one: copy the private key content.
- If not: run `ssh-keygen -t ed25519 -f deploy_key` on their local machine, then add the public key to the VPS `~/.ssh/authorized_keys`.
The agent never handles these values. The user adds them in GitHub.
## Step 5 — First deploy
Push to `main`. GitHub Actions will run the workflow. Tell the user to:
1. Check the Actions tab in GitHub for the workflow run.
2. If it passes, visit `http://<their-vps-ip>:3000` (or their configured port).
3. If it fails, check the SSH step output for the specific error.
## Save as project skill
After successful deployment, save to `.agents/skills/deploy-project/SKILL.md`:
```markdown
---
name: deploy-project
description: Deploy this project to the VPS via GitHub Actions.
---From prinx/agents, MIT.
More from prinx/agents
- 0.521score
ui-ux
prinx
Fallback for user-facing interface work when frontend-design is unavailable; keep UI clear, accessible, responsive, and intentional without unnecessary…
SkillBFreshness: BClaude Code +9 - 0.518score
quality-review
prinx
Use when reviewing a ticket diff for correctness, regressions, architecture, security, and maintainability.
SkillBFreshness: BClaude Code +9 - 0.518score
orchestrate
prinx
Use when classifying engineering work, selecting a fast or full workflow path, and coordinating agent handoffs.
SkillBFreshness: BClaude Code +9 - 0.513score
branch-safely
prinx
Use before implementation when checking repository state, selecting a branch, or protecting uncommitted work.
SkillBFreshness: BClaude Code +9 - 0.473score
unit-testing
prinx
Use when creating or running focused automated tests for isolated logic and edge cases.
SkillCFreshness: CClaude Code +9 - 0.473score
deploy-vercel
prinx
Use when an approved, human-requested deployment specifically targets Vercel.
SkillCFreshness: CClaude Code +9 - 0.473score
e2e-testing
prinx
Use when a user journey or cross-service behavior needs end-to-end validation.
SkillCFreshness: CClaude Code +9 - 0.473score
feature-testing
prinx
Use when validating a completed feature against its acceptance criteria through integrated behavior.
SkillCFreshness: CClaude Code +9 - 0.469score
requirements-gathering
prinx
Use when a request needs product discovery, scope, acceptance criteria, constraints, or high-value clarification questions.
SkillCFreshness: CClaude Code +9 - 0.469score
solution-design
prinx
Use when translating approved requirements into a solution design, architecture fit, risks, and test strategy.
SkillCFreshness: CClaude Code +9 - 0.469score
monitoring
prinx
Use for standalone, on-demand checks of production health, errors, performance, or uptime.
SkillCFreshness: CClaude Code +9 - 0.469score
task-breakdown
prinx
Use when converting a plan into ordered, independently verifiable engineering backlog tickets.
SkillCFreshness: CClaude Code +9
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Jul 26, 2026 (3 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/prinx/agents
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from prinx
- 0.521score
ui-ux
prinx
Fallback for user-facing interface work when frontend-design is unavailable; keep UI clear, accessible, responsive, and intentional without unnecessary…
SkillBFreshness: BClaude Code +9 - 0.518score
orchestrate
prinx
Use when classifying engineering work, selecting a fast or full workflow path, and coordinating agent handoffs.
SkillBFreshness: BClaude Code +9 - 0.518score
quality-review
prinx
Use when reviewing a ticket diff for correctness, regressions, architecture, security, and maintainability.
SkillBFreshness: BClaude Code +9 - 0.513score
branch-safely
prinx
Use before implementation when checking repository state, selecting a branch, or protecting uncommitted work.
SkillBFreshness: BClaude Code +9 - 0.473score
unit-testing
prinx
Use when creating or running focused automated tests for isolated logic and edge cases.
SkillCFreshness: CClaude Code +9 - 0.473score
deploy-vercel
prinx
Use when an approved, human-requested deployment specifically targets Vercel.
SkillCFreshness: CClaude Code +9
Cite this page
deploy-vps skill. Agent Mart. https://agentmart.dev/skills/prinx-deploy-vps (last updated 2026-10-24)