provision
This skill should be used when the user asks to "provision a VPS", "create a Hetzner server", "spin up a cloud server", "launch a Hetzner instance", "set up a cloud server for Claude Code", "deploy Claude Code to a server", "create a VPS for Claude", or mentions Hetzner Cloud provisioning. Automates VPS creation with Claude Code pre-installed.
What this skill does
# Hetzner VPS Skill
Provision Hetzner Cloud VPS instances with Claude Code pre-installed.
## Provisioning Workflow
### Step 1: Pre-Flight Verification
Invoke the `hetzner-preflight-check` agent to verify prerequisites and gather options dynamically.
The agent verifies hcloud CLI, validates token, and returns available:
- Locations (datacenter options)
- SSH keys (registered in Hetzner)
- Existing servers (to avoid naming conflicts)
### Step 2: Gather User Preferences
Use AskUserQuestion to collect:
| Option | Required | Default |
|--------|----------|---------|
| Server name | Yes | - |
| SSH key | Yes | - |
| Location | Yes | - |
| Server type | No | Cheapest 4 vCPU, 8 GB option |
| Terminal setup | No | No |
| ccstatusline setup | No | No |
**Recommendations:**
- **Server type:** Preflight check finds the cheapest 4 vCPU, 8 GB server (best balance for Claude Code)
- **Location:** fsn1 (Germany) for EU, ash (Virginia) for US
### Step 3: Provision
Call provision.sh with explicit flags:
```bash
${CLAUDE_PLUGIN_ROOT}/skills/provision/scripts/provision.sh \
--name <server-name> \
--ssh-key <key-name> \
--location <location> \
--type <selected-type> \
--terminal-setup # Optional: copy zsh/oh-my-zsh/p10k
--statusline-setup # Optional: install bun + ccstatusline
```
### Step 4: Post-Provision
After successful provisioning, provide the user with:
```
SSH access: ssh claude@<ip>
Next steps: claude
```
**Interactive SSH (recommended for daily use):**
```bash
# Connect to the server
ssh claude@<ip>
# Claude is available in PATH for interactive sessions
claude --version
claude
```
**Non-interactive SSH verification:**
```bash
# Use full path for non-interactive SSH commands
ssh claude@<ip> "~/.local/bin/claude --version"
```
**Note:** Non-interactive SSH commands (e.g., `ssh user@host "command"`) don't source shell profiles, so the `claude` command won't be in PATH. Always use the full path `~/.local/bin/claude` for non-interactive verification. Interactive sessions work normally.
## Flags Reference
| Flag | Description |
|------|-------------|
| `--name` | Server name (must be unique) |
| `--ssh-key` | SSH key name from Hetzner Cloud |
| `--location` | Datacenter (fsn1, nbg1, ash, hil, hel1, sin) |
| `--type` | Server type (from preflight recommendation) |
| `--user` | Non-root username (default: claude) |
| `--terminal-setup` | Copy local zsh/oh-my-zsh/p10k config |
| `--statusline-setup` | Install bun and copy statusLine settings |
## Available Scripts
| Script | Purpose |
|--------|---------|
| `${CLAUDE_PLUGIN_ROOT}/skills/provision/scripts/provision.sh` | Create VPS with Claude Code |
| `${CLAUDE_PLUGIN_ROOT}/skills/provision/scripts/status.sh` | Check VPS health |
| `${CLAUDE_PLUGIN_ROOT}/skills/provision/scripts/ssh-command.sh` | Execute remote commands |
| `${CLAUDE_PLUGIN_ROOT}/skills/provision/scripts/inject-secret.sh` | Inject other secrets (databases, APIs) |
## Prerequisites
First-time setup requirements (see `references/prerequisites.md`):
- hcloud CLI installed
- HCLOUD_TOKEN environment variable set
- SSH key registered in Hetzner Cloud
## Terminal Setup Options
When `--terminal-setup` is provided, copies from local machine:
- `~/.zshrc`, `~/.oh-my-zsh/`, `~/.p10k.zsh`
- `~/.config/ccstatusline/`
When `--statusline-setup` is also provided:
- Installs bun runtime
- Creates `~/.claude/settings.json` with statusLine (uses full path to bunx)
## Troubleshooting
See `references/troubleshooting.md` for:
- SSH connection issues
- Claude Code installation failures
- ccstatusline not appearing
- Terminal font issues
## Security
See `references/security-best-practices.md` for:
- Claude account authentication
- Token security
- Incident response
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.