# Create Proxmox VM Templates

Manual VM template work can create slow deployments and inconsistent Proxmox images. This skill guides reusable templates for Cloud-Init, Kubernetes, and application workloads.

## Install

```bash
npx skillstore add dataknifeai/vm-template-creation
```

## Metadata

- Status: approved
- Slug: dataknifeai-vm-template-creation
- Skillstore revision: r1
- Version status: missing
- Tree hash: 08822215deffd6405826b21485b8268585e11378e04ff4bfb20ca9544fd83435
- Author: DataKnifeAI
- GitHub username: DataKnifeAI
- License: MIT
- Repository: https://github.com/DataKnifeAI/proxmox-ve-mcp/tree/main/.github/skills/vm-template-creation
- Ref: 34f316ba14ef36c7a620fc09f2676d2429997a77
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/dataknifeai-vm-template-creation
- Manifest: https://skillstore.pages.dev/api/skills/dataknifeai-vm-template-creation/manifest

## Capabilities

- Plan base VM settings for Proxmox templates, including CPU, memory, disk, ISO, and bridge values.
- Convert tested VMs into templates by setting the template flag.
- Clone templates into named VM instances for application or Kubernetes nodes.
- Describe Cloud-Init use for hostname, network, and post-clone configuration.
- Recommend template versioning, hardening, testing, and cleanup practices.

## Use Cases

- Build Kubernetes Node Templates: Create RKE2-ready Ubuntu templates for repeatable control plane and worker node deployments.
- Standardize Server Provisioning: Prepare web, database, or CI templates that clone into consistent production or lab servers.
- Maintain Template Versions: Track patched, tested, and documented VM templates for infrastructure automation workflows.

## Prompt Templates

### Create Basic Template

```
Create an Ubuntu 22.04 Cloud-Init template on pve2 with VM ID 100, 2 cores, 4 GB memory, and 50 GB disk.
```

### Convert Tested VM

```
Mark VM 100 on pve2 as a template after I confirm packages, patches, SSH, and Cloud-Init are ready.
```

### Clone Cluster Nodes

```
Clone template VM 100 on pve2 into three full clones for control plane nodes named rancher-1, rancher-2, and rancher-3.
```

### Refresh Template Lifecycle

```
Guide a safe update of template VM 100 by creating a test clone, applying patches, validating services, and recording a new version.
```

## Limitations

- Templates must be cloned before booting.
- It does not import disk images or run Proxmox CLI commands directly.
- Cloud-Init network settings still need validation on each target network.
- Large templates can take longer to clone and move between storage pools.

## Best Practices

- Patch and harden the VM before marking it as a template.
- Use Cloud-Init for hostname, network, SSH, and first boot configuration.
- Document template names, versions, packages, and test results.

## Anti Patterns

- Converting a VM that still contains credentials or temporary secrets.
- Booting a template directly instead of cloning it first.
- Using one large template for unrelated workloads with different security needs.

## Security Audit

- Audited at: 2026-07-06T09:20:14.869\+00:00
- Summary: The static findings are false positives caused by Markdown backticks, fenced examples, and normal Proxmox template terms. SKILL.md and output.json contain documentation and marketplace content, not executable code or prompt injection. Operators should still review VM actions before applying them to production infrastructure.

## Stats

- Views: 277
- Downloads: 7
- Favorites: 0
- Popularity score: 0