Range 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.
Install
$ agentstack add skill-badsectorlabs-ludus-skills-range-config ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-badsectorlabs-ludus-skills-range-config) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Ludus Range Configuration
Use this skill to build safe, valid Ludus YAML configurations and explain tradeoffs in topology, networking, and role design.
Key Principles
- Always suggest the YAML schema validation header at the top of configs:
``yaml # yaml-language-server: $schema=https://docs.ludus.cloud/schemas/range-config.json ``
- Use
{{ range_id }}template strings in vm_name and hostname fields. This resolves to the user's range ID (e.g., "JS").
- Windows hostnames are limited to 15 characters due to NETBIOS.
- VLANs must be 2-255 and become the third octet of the VM's IP (e.g., vlan 10 = 10.X.10.Y).
- iplastoctet must be unique within a VLAN.
- Set
linux: truefor Linux VMs,windows:key for Windows VMs,macOS: truefor macOS VMs.
- Domain roles are:
primary-dc,alt-dc, ormember.
- role_vars must be a dictionary - do not use hyphens to prefix variables.
- Roles must exist on the server before deploy — verify installed roles and add any that are missing.
Workflow
- Clarify the target environment and intended use case.
- Define required VMs and roles.
- Verify that required templates are available on the server.
- Build or revise YAML in small, valid increments.
- Propose network rules and testing behavior appropriate for the scenario.
- Verify that required Ansible roles/collections are installed; recommend any that need to be added.
- Validate structure and values against the schema reference.
References
- Use
references/schema.mdfor full schema details, valid values, defaults, and complete examples. - Use
https://docs.ludus.cloud/docs/configurationfor official configuration guidance. - Use
https://docs.ludus.cloud/schemas/range-config.jsonfor schema-backed validation.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: badsectorlabs
- Source: badsectorlabs/ludus-skills
- License: MIT
- Homepage: https://docs.ludus.cloud/docs/using-ludus/mcp
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.