How do I install the Setup Context skill?

Run npx get-skill add tomevault-io/setup-context in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Setup Context safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Setup Context?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Setup Context free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Setup Context?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Setup Context by tomevault-io — Agent Skill

Name: Setup Context
Author: tomevault-io

Setup Context

Set up a new nixos-vm-template context for managing VMs on a hypervisor (libvirt or proxmox). Use this when the user wants to configure a new VM management context, create an alias, or set up environment variables for a backend. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Setup Context Skill

Configure the .env file for managing VMs on a hypervisor.

Instructions

Step 1: Ask for Backend Type

Use AskUserQuestion to ask which backend:

libvirt - Local QEMU/KVM via libvirt
proxmox - Remote Proxmox VE server via SSH

Step 2: Gather Backend-Specific Settings

For libvirt backend:

Most users can accept defaults. Only ask about non-default settings if user indicates special requirements (like running from a container).

Create .env with just:

BACKEND=libvirt

For proxmox backend:

Ask the user (as plain text prompts, not multiple choice):

PVE_HOST (required) - SSH config host name (e.g., pve) or hostname/IP
PVE_STORAGE - Storage for VM disks (default: local)
PVE_BRIDGE - Network bridge (default: vmbr0)

Explain that they should configure their SSH connection in ~/.ssh/config:

Host pve
    HostName 192.168.1.100
    User root
    Port 22

And use ssh-agent for key authentication:

eval $(ssh-agent)
ssh-add ~/.ssh/id_ed25519

Step 3: Create the .env file

Create/overwrite the .env file at the project root.

Example .env for libvirt:

BACKEND=libvirt

Example .env for proxmox:

BACKEND=proxmox
PVE_HOST=pve
PVE_STORAGE=local-lvm
PVE_BRIDGE=vmbr0
PVE_BACKUP_STORAGE=local

Step 4: Test Connection

After creating the .env file, run the connection test:

just test-connection

Important: Warn the user that they may need to authenticate multiple times during the test (SSH key passphrase prompts if not using ssh-agent, or host key verification).

If the test passes, tell the user the setup is complete and they can now use just commands.

Variable Reference

Libvirt Variables

Variable	Default	Description
`BACKEND`	`libvirt`	Set to `libvirt`
`LIBVIRT_URI`	`qemu:///system`	Libvirt connection URI
`HOST_CMD`	(empty)	Prefix for host commands (e.g., `host-spawn` for distrobox)

Proxmox Variables

Variable	Default	Description
`BACKEND`	-	Set to `proxmox`
`PVE_HOST`	(required)	SSH config host name (or hostname/IP)
`PVE_NODE`	`$PVE_HOST`	Proxmox node name (for clusters)
`PVE_STORAGE`	`local`	Proxmox storage for VM disks
`PVE_BRIDGE`	`vmbr0`	Network bridge name
`PVE_DISK_FORMAT`	`qcow2`	Disk format (qcow2, raw, vmdk)
`PVE_BACKUP_STORAGE`	`local`	Proxmox storage for backups

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: setup-contextdescription: Set up a new nixos-vm-template context for managing VMs on a hypervisor (libvirt or proxmox). Use this when the user wants to configure a new VM management context, create an alias, or set up environment variables for a backend. Use when this capability is needed.---# Setup Context SkillConfigure the `.env` file for managing VMs on a hypervisor.## Instructions### Step 1: Ask for Backend TypeUse AskUserQuestion to ask which backend:- **libvirt** - Local QEMU/KVM via libvirt- **proxmox** - Remote Proxmox VE server via SSH### Step 2: Gather Backend-Specific Settings#### For libvirt backend:Most users can accept defaults. Only ask about non-default settings if user indicates special requirements (like running from a container).Create `.env` with just:```bashBACKEND=libvirt```#### For proxmox backend:Ask the user (as plain text prompts, not multiple choice):- **PVE_HOST** (required) - SSH config host name (e.g., `pve`) or hostname/IP- **PVE_STORAGE** - Storage for VM disks (default: local)- **PVE_BRIDGE** - Network bridge (default: vmbr0)Explain that they should configure their SSH connection in `~/.ssh/config`:```Host pve HostName 192.168.1.100 User root Port 22```And use ssh-agent for key authentication:```basheval $(ssh-agent)ssh-add ~/.ssh/id_ed25519```### Step 3: Create the .env fileCreate/overwrite the `.env` file at the project root.Example `.env` for libvirt:```bashBACKEND=libvirt```Example `.env` for proxmox:```bashBACKEND=proxmoxPVE_HOST=pvePVE_STORAGE=local-lvmPVE_BRIDGE=vmbr0PVE_BACKUP_STORAGE=local```### Step 4: Test ConnectionAfter creating the `.env` file, run the connection test:```bashjust test-connection```**Important:** Warn the user that they may need to authenticate multiple times during the test (SSH key passphrase prompts if not using ssh-agent, or host key verification).If the test passes, tell the user the setup is complete and they can now use `just` commands.## Variable Reference### Libvirt Variables| Variable | Default | Description ||----------|---------|-------------|| `BACKEND` | `libvirt` | Set to `libvirt` || `LIBVIRT_URI` | `qemu:///system` | Libvirt connection URI || `HOST_CMD` | (empty) | Prefix for host commands (e.g., `host-spawn` for distrobox) |### Proxmox Variables| Variable | Default | Description ||----------|---------|-------------|| `BACKEND` | - | Set to `proxmox` || `PVE_HOST` | (required) | SSH config host name (or hostname/IP) || `PVE_NODE` | `$PVE_HOST` | Proxmox node name (for clusters) || `PVE_STORAGE` | `local` | Proxmox storage for VM disks || `PVE_BRIDGE` | `vmbr0` | Network bridge name || `PVE_DISK_FORMAT` | `qcow2` | Disk format (qcow2, raw, vmdk) || `PVE_BACKUP_STORAGE` | `local` | Proxmox storage for backups |---> Converted and distributed by [TomeVault](https://tomevault.io/claim/enigmacurry) — claim your Tome and manage your conversions.

Frequently asked questions