rose-docker-build
Build the ROSE compiler in a Docker container using autotools or CMake. Use when setting up ROSE development environment, building ROSE from source, or troubleshooting ROSE build issues. ROSE requires GCC 7-10 which most modern hosts don't have, so Docker is the recommended approach.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/chunhualiao/rose-docker-build-skillWhat This Skill Does
The rose-docker-build skill provides an automated, containerized approach to compiling the complex ROSE source-to-source compiler framework. Because ROSE relies on specific legacy versions of the GCC toolchain (specifically 7-10), attempting to build it on modern host operating systems often results in compilation errors. This skill abstracts the complexity of Dockerfile configuration and container lifecycle management, allowing developers to build, test, and develop with ROSE in a stable, version-locked environment.
Installation
To integrate this skill into your OpenClaw environment, execute the following command in your terminal:
clawhub install openclaw/skills/skills/chunhualiao/rose-docker-build-skill
Ensure you have Docker Desktop or the Docker Engine installed and running on your host machine prior to installation, as this skill performs direct operations against the Docker daemon.
Use Cases
- Cross-Platform Compilation: Building the ROSE compiler on systems running Ubuntu 22.04 or later, which lack the required GCC versions.
- CI/CD Pipeline Setup: Creating reproducible build environments for ROSE research projects to ensure consistent output across different machines.
- Development Environment Isolation: Avoiding 'dependency hell' on your host system by keeping build-time dependencies, such as Boost and specific autotools versions, contained within the container image.
- Modernizing Build Workflows: Transitioning from legacy Autotools-based builds to modern CMake build systems while maintaining compatibility with the core compiler framework.
Example Prompts
- "OpenClaw, please set up a new ROSE development environment using the Autotools configuration in a container."
- "I need to rebuild ROSE using CMake. Can you execute the build process with the standard Release configuration?"
- "The ROSE compilation failed on my system. Can you use the rose-docker-build skill to isolate the build and identify if it is a dependency issue?"
Tips & Limitations
- Resource Allocation: ROSE builds are notoriously memory-intensive. When using the CMake workflow, always ensure your Docker container is allocated at least 8GB of RAM; use
-j4flags to limit parallel threads if you experience OOM (Out of Memory) kills. - Host Volume Mapping: The skill uses volume mapping to keep your source code on the host machine. Ensure you have write permissions to your local project directory.
- Build Speed: The initial build is time-consuming as it compiles the large ROSE codebase. Use incremental builds and maintain your container state to significantly reduce subsequent build times.
- CMake vs Autotools: While CMake is recommended for modern IDE integration, the Autotools workflow remains the most stable path for deep ROSE framework development.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-chunhualiao-rose-docker-build-skill": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-read, file-write, code-execution
Related Skills
claude-usage
Check Claude Max plan usage limits by launching Claude Code and running /usage. Use when the user asks about Claude plan usage, remaining quota, rate limits, or sends /claude_usage.
save-to-obsidian
Saves markdown content to remote Obsidian vault via SSH
task-runner
Persistent task queue system. Users add tasks at any time via natural language; tasks are stored in a single persistent queue file and executed asynchronously via subagents. A heartbeat/cron dispatcher wakes periodically to check pending tasks, spawn workers, and report completions. The system never "finishes" — it always remains ready for the next task.
openclaw-docker-setup
Install and configure a fully operational Dockerized OpenClaw instance on macOS from scratch. Includes browser pairing, Discord channel setup, and optional Gmail/Google Drive integration. Use when user asks to "install openclaw docker", "set up dockerized openclaw", "openclaw in docker", or "isolated openclaw instance".
skill-releaser
Release skills to ClawhHub through the full publication pipeline — auto-scaffolding, OPSEC scan, dual review (agent + user), force-push release, security scan verification. Use when releasing a skill, preparing a skill for release, reviewing a skill for publication, or checking release readiness.