vulhub-env-manager

Start, stop, and summarize Vulhub environments via Docker Compose.

9|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/KaGty1/vulhub-env-build --skill vulhub-env-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vulhub-env-manager
Source: https://github.com/KaGty1/vulhub-env-build/tree/main
Command: npx skills add https://github.com/KaGty1/vulhub-env-build --skill vulhub-env-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tomllib, and includes scripts (resource) and references (resource) components.

What problem does it solve?

It solves the problem of quickly starting, stopping, and diagnosing local Vulhub vulnerability reproduction environments with accurate access details and actionable troubleshooting when Docker Compose fails.

Core Features & Use Cases

  • Environment discovery by CVE/app query: Locates the correct Vulhub environment directory using environments.toml rather than relying on guesswork.
  • Reliable start/stop with compose orchestration: Runs docker compose up -d to start and docker compose down -v to stop and clean volumes.
  • Chinese failure diagnosis and fixes: When startup fails, it classifies common errors (network/proxy/mirror/TLS/architecture/Kali ulimit) and provides concrete remediation steps.
  • Automated information summarization: Extracts from README.zh-cn.md the access URL(s), default credentials, and initialization/verification cues for the user’s chosen lab.

Quick Start

Ask for it in Chinese, for example: “帮我搭建 CVE-2021-29442 的漏洞环境”,并让 the agent start the matching lab and reply with the environment path, access URL(s), and default credentials/initialization instructions.

Frequently Asked Questions about vulhub-env-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start a Vulhub vulnerability lab using a specific CVE or app query?

To start a Vulhub vulnerability lab, you query by CVE or app name to locate the correct directory using environments.toml, then execute docker compose up -d to orchestrate the environment startup automatically.

Why does docker compose fail when starting Vulhub environments and how can I fix it?

Docker compose startup failures for Vulhub are classified into network, proxy, mirror, TLS, architecture, or Kali ulimit errors, with the Skill providing concrete Chinese diagnostic remediation steps for each.

How do I find access URLs and default credentials for a running Vulhub environment?

Access URLs and default credentials for running Vulhub environments are extracted automatically from README.zh-cn.md or README files, providing initialization cues and verification steps alongside the lab deployment.

What is the best way to stop and clean up local Vulhub vulnerability environments?

The best way to stop Vulhub environments is executing docker compose down -v, which halts the containers and cleans up associated volumes to ensure a pristine state for future vulnerability lab reproductions.

Do I need environments.toml to manage Vulhub Docker compose orchestration?

Yes, environments.toml is mandatory for resolving and discovering the correct Vulhub environment directory, ensuring accurate Docker compose orchestration rather than relying on guesswork for CVE lab startup.