# Manage Proxmox LXC Containers

Container operations in Proxmox require clear status checks, lifecycle actions, and resource planning. This skill guides Claude, Codex, and Claude Code through structured LXC workflows.

## Install

```bash
npx skillstore add dataknifeai/container-management
```

## Metadata

- Status: approved
- Slug: dataknifeai-container-management
- Skillstore revision: r1
- Version status: missing
- Tree hash: 027c23ec736d9327056ead7066e812e30de7b91d977db472bd18003e2498d805
- Author: DataKnifeAI
- GitHub username: DataKnifeAI
- License: MIT
- Repository: https://github.com/DataKnifeAI/proxmox-ve-mcp/tree/main/.github/skills/container-management
- Ref: 7e9e368dc1a370f2040369ebcd0db06d90cb48e5
- 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-container-management
- Manifest: https://skillstore.pages.dev/api/skills/dataknifeai-container-management/manifest

## Capabilities

- List containers on a specific Proxmox node.
- Review container status, configuration, and resource allocation.
- Coordinate start, stop, shutdown, reboot, and delete workflows.
- Guide basic and advanced LXC container creation.
- Plan container cloning for testing or deployment.
- Support resource monitoring and placement recommendations.

## Use Cases

- Daily Container Operations: Review container status, start stopped services, and confirm resource use across a node.
- Deployment Preparation: Create or clone LXC containers with planned CPU, memory, storage, and hostname settings.
- Capacity Review: Compare container allocations and identify candidates for tuning or redistribution across nodes.

## Prompt Templates

### Check Container Inventory

```
List containers on node <node> and summarize status, CPU, memory, and storage allocation.
```

### Inspect One Container

```
Get the status and full configuration for container <id>, then flag unusual resource or state values.
```

### Plan a Safe Clone

```
Clone container <source_id> for testing. Recommend target settings, validation steps, and rollback checks before changes.
```

### Optimize Container Placement

```
Review containers across nodes and recommend placement or resource changes for balanced CPU, memory, and storage use.
```

## Limitations

- Requires configured Proxmox tools or MCP access.
- Does not include executable scripts or API clients.
- Destructive operations still need operator confirmation.
- Recommendations depend on data returned by Proxmox.

## Best Practices

- Confirm node, container ID, and backup status before destructive actions.
- Use graceful shutdown before immediate stop when possible.
- Document hostname, purpose, owner, and resource plan for each container.

## Anti Patterns

- Deleting containers without checking backups and attached storage.
- Cloning production containers without changing identity and network settings.
- Increasing resource limits without reviewing node capacity.

## Security Audit

- Audited at: 2026-07-05T09:23:38.918\+00:00
- Summary: All static findings were reviewed against SKILL.md. The external command detections are Markdown inline tool names, and the system reconnaissance detection is a benign hostname best practice.

## Stats

- Views: 250
- Downloads: 8
- Favorites: 0
- Popularity score: 0