mock

Manage RPM package builds securely and reproducibly using Mock to create clean chroot environments with configurable presets and plugins.

This skill appears to be what it says: a guide for using Mock to build RPMs. Before following the instructions, consider: do not add NOPASSWD sudo entries unless you understand the risk—prefer adding the user to the mock group and using sudo with explicit, audited commands; avoid disabling GPG checks (gpgcheck=0) unless you control the repository and accept the risk; be careful with the 'sign' plugin because signing requires private keys—ensure keys remain on secure hardware or in a protected agent and are not exposed to build chroots; review any repository URLs and local paths you add; run mock actions in an isolated build host or VM to limit blast radius. If you need a higher-assurance review, provide the full (non-truncated) custom.cfg and any repository URLs or signing workflows the skill will use so those parts can be inspected in detail.

Type: OpenClaw Skill Name: mock-build Version: 1.0.0 The skill bundle provides comprehensive documentation and instructions for managing RPM build environments using the legitimate 'mock' tool. It includes standard setup procedures, such as group management and sudoers configuration for the mock binary, which are typical for build automation. All provided commands, configuration examples (e.g., custom.cfg), and repository URLs (Fedora/EPEL) are consistent with the stated purpose of RPM package building and show no signs of malicious intent, data exfiltration, or prompt injection.