Build ROSE tools using a container

This skill appears to be a set of instructions for using a Docker image to build ROSE-based tools, but there are inconsistencies you should resolve before running anything: - Confirm you have Docker installed; the skill does not declare this but the commands require it. Install and test 'docker' locally first. - The image name 'rose-dev:latest' is unspecified (no registry or digest). Only run/pull container images from a trusted registry or use an explicit image digest, or build the image locally from a trusted Dockerfile. - The example mounts a host path '/home/liao/rose-install' — replace this with your actual path. Avoid mounting sensitive host directories into containers and prefer read-only mounts where possible. - The SKILL.md refers to $ROSE in troubleshooting but the Makefile uses ROSE_INSTALL=/rose/install. Decide which variable you will actually use and set it explicitly when running the container to avoid confusion. - Be cautious about running containers as root or with elevated privileges; consider running with reduced capabilities, a user mapping, or appropriate security flags (e.g., --security-opt, --cap-drop) if the image is untrusted. - The instruction to set ulimit -s unlimited can impact the host; only do this if you understand the implications. If you cannot verify the origin of the 'rose-dev:latest' image or prefer tighter control, obtain/build the container image from a trusted source (or inspect its Dockerfile) and update the skill instructions to declare Docker as a required binary and to use explicit, non-host-specific paths and environment variables.