Unraid XML Generator
v1.0.1Generate Unraid DockerMan user template XML files from structured input. Use when: the user asks to "生成 Unraid XML 模板", "创建 Docker 模板", "为 XXX 写 Unraid 模板",...
⭐ 0· 25·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
Name/description, SKILL.md, and the included Python script all align: they build Unraid DockerMan XML templates and (optionally) deploy them to /boot/config/plugins/dockerMan/templates-user/my-<name>.xml. The script's CLI flags and outputs match the documented functionality.
Instruction Scope
Instructions and script operate only on inputs provided via CLI and produce XML output. The runtime behavior includes writing files to a user-specified output path and, if --deploy is used and the user confirms, to /boot/config/plugins/dockerMan/templates-user/. The skill documents and prompts for confirmation before deployment. The SKILL.md and script also emphasize bypassing container ENTRYPOINT via ExtraParams/PostArgs — this is expected for an Unraid template generator but is a powerful capability (it allows overriding an image's startup behavior) and should be used intentionally.
Install Mechanism
No install steps or external downloads are present. The skill is instruction+script only and does not attempt to fetch or install third-party code.
Credentials
The skill requests no environment variables or credentials. It does include example/default configuration values (e.g., proxy defaults pointing to 192.168.8.30:7893 and default TZ Asia/Shanghai) and will include user-provided env entries in generated templates. Those defaults are odd but not harmful in themselves — users should review and remove any proxy/secret values they do not intend to expose in template configs. Masking for sensitive values must be set explicitly in the template Config entries.
Persistence & Privilege
always is false and the skill is user-invocable. The only persistence is optional writing of the generated XML to disk (including the Unraid templates-user path) and only if the user runs the script with --deploy and confirms. The skill does not modify other skills or system-wide configs beyond writing its own output.
Assessment
This skill appears coherent and implements exactly what it claims: programmatic generation of Unraid DockerMan XML templates. Before using it: (1) inspect the generated XML to ensure no unintended environment variables or secrets are included (the script will include any --env KEY=VALUE entries verbatim); (2) be aware that the template can override an image's ENTRYPOINT and run arbitrary startup commands via PostArgs — use that deliberately; (3) the --deploy option will write to /boot/config/plugins/dockerMan/templates-user/my-<name>.xml if you confirm, so only deploy on a trusted Unraid host and with correct filename; (4) remove or change any hard-coded example proxy (192.168.8.30:7893) if it is not appropriate for your network. Otherwise the skill is internally consistent and not requesting excessive privileges or credentials.Like a lobster shell, security has layers — review code before you run it.
dockervk979x104j4n9gjt6vw3c91etys84b1cslatestvk979x104j4n9gjt6vw3c91etys84b1cstemplatevk979x104j4n9gjt6vw3c91etys84b1csunraidvk979x104j4n9gjt6vw3c91etys84b1csxmlvk979x104j4n9gjt6vw3c91etys84b1cs
License
MIT-0
Free to use, modify, and redistribute. No attribution required.