virtual-machine-management
Manage Proxmox Virtual Machines
Managing virtual machines across Proxmox nodes requires navigating complex interfaces and remembering multiple API endpoints. This skill provides a unified interface to create, monitor, and control VMs directly through natural language commands.
์คํฌ ZIP ๋ค์ด๋ก๋
Claude์์ ์ ๋ก๋
์ค์ โ ๊ธฐ๋ฅ โ ์คํฌ โ ์คํฌ ์ ๋ก๋๋ก ์ด๋
ํ ๊ธ์ ์ผ๊ณ ์ฌ์ฉ ์์
ํ ์คํธํด ๋ณด๊ธฐ
"virtual-machine-management" ์ฌ์ฉ ์ค์ ๋๋ค. List all VMs on the production node
์์ ๊ฒฐ๊ณผ:
- Found 5 virtual machines:
- โข VM 100 (web-server-01): Running - 4 CPUs, 8GB RAM, 100GB storage
- โข VM 101 (db-server-01): Running - 8 CPUs, 32GB RAM, 500GB storage
- โข VM 102 (test-app): Stopped - 2 CPUs, 4GB RAM, 50GB storage
- โข VM 103 (dev-environment): Running - 2 CPUs, 4GB RAM, 40GB storage
- โข VM 104 (template-ubuntu): Template - 2 CPUs, 2GB RAM, 20GB storage
"virtual-machine-management" ์ฌ์ฉ ์ค์ ๋๋ค. Create a new VM with 4 CPU cores and 8GB RAM
์์ ๊ฒฐ๊ณผ:
- Creating VM with configuration:
- โข CPUs: 4
- โข Memory: 8GB
- โข Node: pve1
- VM 200 successfully created and is ready for use.
- Use 'get_vm_status' to verify configuration.
๋ณด์ ๊ฐ์ฌ
์์ This is a pure documentation skill with no executable code. The SKILL.md file defines MCP tool interfaces for Proxmox VM management using markdown formatting. All static findings are false positives caused by the scanner misinterpreting documentation syntax (markdown code spans, hash values, and URLs) as malicious patterns. No scripts, network calls, filesystem access, or code execution paths exist in this skill.
์ํ ์์ธ
๐ ๋คํธ์ํฌ ์ ๊ทผ (1)
๐ ํ์ผ ์์คํ ์ก์ธ์ค (1)
โ๏ธ ์ธ๋ถ ๋ช ๋ น์ด (37)
ํ์ง ์ ์
๋ง๋ค ์ ์๋ ๊ฒ
Automate VM Lifecycle
Automate start, stop, and scaling operations for development and testing environments.
Manage Production VMs
Monitor and maintain virtual machines across multiple Proxmox nodes from a single interface.
Deploy VM Templates
Create standardized VM templates and clone them for consistent, repeatable deployments.
์ด ํ๋กฌํํธ๋ฅผ ์ฌ์ฉํด ๋ณด์ธ์
List all virtual machines on the production Proxmox node
What is the current status and resource usage of VM 100
Create a new virtual machine with 4 CPU cores and 8GB RAM on node pve1
Clone template VM 100 to create a new VM named web-server-01 with a unique ID
๋ชจ๋ฒ ์ฌ๋ก
- Use template VMs for consistent, repeatable deployments across your infrastructure
- Monitor VM resource utilization regularly to prevent performance bottlenecks
- Test all VM changes in non-production environments before applying them to production
ํผํ๊ธฐ
- Creating VMs with fixed resources without planning for workload requirements
- Skipping graceful shutdown and using immediate stop which can cause data loss
- Leaving unused VMs running which consumes resources and increases attack surface
์์ฃผ ๋ฌป๋ ์ง๋ฌธ
Which Proxmox versions are supported?
What are the resource limits for VM operations?
How do I connect this skill to my Proxmox environment?
Is my VM data stored or transmitted externally?
Why did my VM creation fail?
How does this compare to the Proxmox web UI?
๊ฐ๋ฐ์ ์ธ๋ถ ์ ๋ณด
์์ฑ์
DataKnifeAI๋ผ์ด์ ์ค
MIT
๋ฆฌํฌ์งํ ๋ฆฌ
https://github.com/DataKnifeAI/proxmox-ve-mcp/tree/main/.github/skills/virtual-machine-management์ฐธ์กฐ
main
ํ์ผ ๊ตฌ์กฐ
๐ SKILL.md