Automated summary
Completely removes a virtual machine including all disks and configuration, with irreversible data loss.
Strengths
- Thorough removal of all VM artifacts
- Irreversible to prevent accidental recreation
- Clear confirmation steps prevent mistakes
- Uses a simple `just` command
Limitations
- Requires the user to know the VM name
- Destructive and irreversible
- Only works with this specific `just`-based setup
Use when you need to permanently delete a VM and all its associated data to free up resources or clean up old machines.
Do not use if you might need the VM or its data in the future, or if you only want to temporarily stop the VM.
Security analysis
CautionThe skill performs a legitimate administrative task (VM purge) but involves irreversible data loss. The use of Bash to execute the destructive command poses risk, but user confirmation is required, and there is no exfiltration or obfuscation.
- •The skill instructs running a Bash command that permanently deletes an entire VM and its configuration, including all associated data, with no possibility of recovery.
- •The use of `yes |` auto-confirms a destructive command, bypassing the underlying tool's confirmation prompt, though the skill enforces explicit user confirmation beforehand.
Examples
I want to permanently delete the VM named 'dev-server'. Remove it completely including all disks and config.List my VMs and help me purge the ones I no longer need. I want to remove them permanently.name: purge-vm description: Completely remove a VM including its machine config. Use when user wants to permanently delete everything about a VM. allowed-tools: Read, Bash, AskUserQuestion
Purge VM Skill
Completely remove a VM including its disks AND machine configuration. This cannot be undone.
Instructions
Step 1: Get VM Name
Run just list-machines to show existing machine configs. Ask which VM to purge.
Step 2: Confirm Purge
IMPORTANT: Warn the user clearly:
- The VM will be stopped and removed
- All VM disks will be deleted
- All data in /var and /home will be PERMANENTLY LOST
- The machine config (machines/{name}/) will ALSO be deleted
- This CANNOT be undone - unlike
destroy, there's no way to recreate the VM
Ask for explicit confirmation.
Step 3: Purge
Run:
yes | just purge {NAME}
The yes | is required to bypass the interactive confirmation prompt.
Step 4: Report Results
Confirm the VM and its config were completely removed.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/purge-vm-mm78no0j/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/purge-vm-mm78no0j' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/purge-vm-mm78no0j/download' --output '.skill-downloads/purge-vm-mm78no0j/SKILL.md.part' && mv '.skill-downloads/purge-vm-mm78no0j/SKILL.md.part' '.skill-downloads/purge-vm-mm78no0j/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Bash, AskUserQuestion
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/purge-vm-mm78no0j/SKILL.md' && test -s '.skill-downloads/purge-vm-mm78no0j/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/purge-vm' && cp -R '.skill-downloads/purge-vm-mm78no0j' '.claude/skills/purge-vm'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/purge-vm-mm78no0j'openskills read 'purge-vm-mm78no0j'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/purge-vm-mm78no0j/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.