environment-guide
Ludus Environment Guide
Use this skill to map user goals to pre-built Ludus environments and provide reliable deployment guidance.
Workflow
- Clarify what the user wants to learn, test, or simulate.
- Recommend one or more pre-built environments that match that objective.
- Check prerequisites before deploy: required templates, required Ansible roles/collections, and minimum resources.
- Guide the deployment steps in order and call out any external playbook steps.
- Provide post-deploy next actions (validation checks, docs, and common follow-up commands).
Key Considerations
- Resource requirements vary widely; include sizing guidance in recommendations.
- Verify required templates are available on the server before starting a deploy.
- Ensure required Ansible roles and collections are installed before deploy.
- Call out when setup depends on external Ansible playbooks run from the user machine.
- Remind users a WireGuard connection is required when running external Ansible against range VMs.
References
- Use
references/environments.mdfor the full environment catalog, requirements, and deployment notes. - Use
https://docs.ludus.cloud/docs/category/environment-guidesfor official environment guide updates. - Use
https://docs.ludus.cloud/docs/quick-start/build-templatesto verify template setup prerequisites.
More from badsectorlabs/ludus-skills
troubleshooting
Diagnose and resolve Ludus deployment, networking, template, WireGuard, Proxmox, and Ansible issues. Use when users report failures, errors, unreachable systems, failed joins, or unexpected behavior during build or deploy.
29range-config
Create, edit, and validate Ludus range configuration YAML including VM definitions, domains, networking, router settings, testing behavior, and role configuration. Use when users need help authoring or reviewing `ludus` range config files.
29ludus-cli
Provide Ludus CLI command guidance, flags, and workflows for range lifecycle, template management, testing mode, snapshots, users/groups, and diagnostics. Use when users ask how to run, interpret, or troubleshoot any `ludus` command.
29