[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75EBCE533XPMVVCHSWTJSAG":3,"skill-same:01M75EBCE533XPMVVCHSWTJSAG":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M75EBCE533XPMVVCHSWTJSAG","rose-docker-build",null,"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.","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fchunhualiao\u002Frose-docker-build-skill\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: rose-docker-build\ndescription: 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.\n---\n\n# ROSE Docker Build\n\nBuild the ROSE source-to-source compiler in an isolated Docker container.\n\n## Why Docker?\n\nROSE requires GCC 7-10. Modern systems have GCC 11+, causing build failures. Docker provides:\n- Correct GCC version (9.x recommended)\n- All dependencies pre-installed\n- Reproducible builds\n- Edit on host, build in container\n\n## Quick Start (Autotools)\n\n```bash\n# 1. Clone ROSE\ngit clone git@github.com:rose-compiler\u002Frose.git\ncd rose && git checkout weekly\n\n# 2. Create Docker environment\nmkdir ..\u002Frose-docker && cd ..\u002Frose-docker\n\n# 3. Build and run container (see Dockerfile below)\ndocker build -t rose-dev .\ndocker run -d --name rose-dev -v $(pwd)\u002F..\u002Frose:\u002Frose\u002Fsrc rose-dev\n\n# 4. Build ROSE inside container\ndocker exec rose-dev bash -c 'cd \u002Frose\u002Fsrc && .\u002Fbuild'\ndocker exec rose-dev bash -c 'mkdir -p \u002Frose\u002Fbuild && cd \u002Frose\u002Fbuild && \\\n  \u002Frose\u002Fsrc\u002Fconfigure --prefix=\u002Frose\u002Finstall \\\n    --enable-languages=c,c++ \\\n    --with-boost=\u002Fusr \\\n    --with-boost-libdir=\u002Fusr\u002Flib\u002Fx86_64-linux-gnu \\\n    --disable-binary-analysis \\\n    --disable-java'\ndocker exec rose-dev bash -c 'cd \u002Frose\u002Fbuild && make core -j$(nproc)'\ndocker exec rose-dev bash -c 'cd \u002Frose\u002Fbuild && make install-core'\n```\n\n## Quick Start (CMake)\n\nCMake builds require CMake 4.x (3.16 fails at ROSETTA generation).\n\n```bash\n# 1. Clone ROSE\ngit clone git@github.com:rose-compiler\u002Frose.git\ncd rose && git checkout weekly\n\n# 2. Create Docker environment and build container\nmkdir ..\u002Frose-docker && cd ..\u002Frose-docker\ndocker build -t rose-dev -f Dockerfile.cmake .\ndocker run -d --name rose-cmake -v $(pwd)\u002F..\u002Frose:\u002Frose\u002Fsrc:ro rose-dev\n\n# 3. Configure with CMake\ndocker exec -w \u002Frose\u002Fbuild rose-cmake cmake \u002Frose\u002Fsrc \\\n  -DCMAKE_INSTALL_PREFIX=\u002Frose\u002Finstall \\\n  -DENABLE_C=ON \\\n  -DENABLE_TESTS=OFF \\\n  -DCMAKE_BUILD_TYPE=Release\n\n# 4. Build (use -j4 to avoid OOM on 16GB systems)\ndocker exec -w \u002Frose\u002Fbuild rose-cmake make -j4\n\n# 5. Test\ndocker exec rose-cmake \u002Frose\u002Fbuild\u002Fbin\u002Frose-compiler --version\n```\n\n### CMake Options\n\n| Option | Description |\n|--------|-------------|\n| `ENABLE_C=ON` | Enable C\u002FC++ analysis (uses EDG frontend) |\n| `ENABLE_BINARY_ANALYSIS=ON` | Enable binary analysis (no EDG needed) |\n| `ENABLE_TESTS=OFF` | Skip test compilation (faster build) |\n| `CMAKE_BUILD_TYPE=Release` | Optimized build |\n\n### CMake vs Autotools\n\n| Feature | Autotools | CMake |\n|---------|-----------|-------|\n| Stability | ✅ Mature | ⚠️ Newer |\n| C\u002FC++ analysis | ✅ Works | ✅ Works (with fixes) |\n| Build target | `make core` | `make` (full build) |\n| Incremental builds | Slower | Faster |\n| IDE integration | Limited | Excellent |\n\n## Dockerfiles\n\n### Dockerfile (Autotools)\n\n```dockerfile\nFROM ubuntu:20.04\nENV DEBIAN_FRONTEND=noninteractive\nENV TZ=America\u002FLos_Angeles\n\nRUN apt-get update && apt-get install -y \\\n    build-essential g++ gcc gfortran \\\n    automake autoconf libtool flex bison \\\n    libboost-all-dev libxml2-dev \\\n    git wget curl vim \\\n    && rm -rf \u002Fvar\u002Flib\u002Fapt\u002Flists\u002F*\n\nRUN useradd -m -s \u002Fbin\u002Fbash developer\nRUN mkdir -p \u002Frose\u002Fsrc \u002Frose\u002Fbuild \u002Frose\u002Finstall && chown -R developer:developer \u002Frose\nUSER developer\nWORKDIR \u002Frose\nCMD [\"tail\", \"-f\", \"\u002Fdev\u002Fnull\"]\n```\n\n### Dockerfile.cmake (CMake)\n\n```dockerfile\nFROM ubuntu:20.04\nENV DEBIAN_FRONTEND=noninteractive\nENV TZ=America\u002FLos_Angeles\n\n# Install build dependencies\nRUN apt-get update && apt-get install -y \\\n    build-essential g++ gcc gfortran \\\n    flex bison \\\n    libboost-all-dev libxml2-dev libreadline-dev \\\n    zlib1g-dev libsqlite3-dev libpq-dev libyaml-dev \\\n    libgmp-dev libmpc-dev libmpfr-dev \\\n    git wget curl vim \\\n    gnupg software-properties-common \\\n    && rm -rf \u002Fvar\u002Flib\u002Fapt\u002Flists\u002F*\n\n# Install CMake 4.x from Kitware (Ubuntu 20.04 has 3.16 which is too old)\nRUN wget -O - https:\u002F\u002Fapt.kitware.com\u002Fkeys\u002Fkitware-archive-latest.asc 2>\u002Fdev\u002Fnull | apt-key add - \\\n    && echo 'deb https:\u002F\u002Fapt.kitware.com\u002Fubuntu\u002F focal main' > \u002Fetc\u002Fapt\u002Fsources.list.d\u002Fkitware.list \\\n    && apt-get update && apt-get install -y cmake \\\n    && rm -rf \u002Fvar\u002Flib\u002Fapt\u002Flists\u002F*\n\nRUN useradd -m -s \u002Fbin\u002Fbash developer\nRUN mkdir -p \u002Frose\u002Fsrc \u002Frose\u002Fbuild \u002Frose\u002Finstall && chown -R developer:developer \u002Frose\nUSER developer\nWORKDIR \u002Frose\nCMD [\"tail\", \"-f\", \"\u002Fdev\u002Fnull\"]\n```\n\n## EDG Binary Handling\n\nEDG (C++ frontend) binaries are required for C\u002FC++ analysis. The build checks:\n\n### Autotools\n1. Build directory for existing tarball\n2. Source tree at `src\u002Ffrontend\u002FCxxFrontend\u002FroseBinaryEDG-*.tar.gz`\n3. Network download from `edg-binaries.rosecompiler.org`\n\n### CMake\n1. Source tree at `src\u002Ffrontend\u002FCxxFrontend\u002FroseBinaryEDG-*.tar.gz` (auto-detected)\n2. Extracts matching tarball based on GCC version at build time\n3. Links `libroseEDG.a` to `librose.so` automatically\n\nIf server is down, ensure source tree has EDG binaries (included in `weekly` branch).\n\n## Common Commands\n\n### Autotools\n```bash\n# Rebuild after source changes\ndocker exec rose-dev bash -c 'cd \u002Frose\u002Fbuild && make core -j8'\n\n# Install\ndocker exec rose-dev bash -c 'cd \u002Frose\u002Fbuild && make install-core'\n```\n\n### CMake\n```bash\n# Rebuild after source changes  \ndocker exec -w \u002Frose\u002Fbuild rose-cmake make -j4\n\n# Install\ndocker exec -w \u002Frose\u002Fbuild rose-cmake make install\n```\n\n### Both\n```bash\n# Test ROSE compiler\ndocker exec rose-dev \u002Frose\u002Finstall\u002Fbin\u002Frose-compiler --version\ndocker exec rose-cmake \u002Frose\u002Fbuild\u002Fbin\u002Frose-compiler --version\n\n# Source-to-source test\ndocker exec rose-dev bash -c 'echo \"int main(){return 0;}\" > \u002Ftmp\u002Ftest.c && \\\n  \u002Frose\u002Finstall\u002Fbin\u002Frose-compiler -c \u002Ftmp\u002Ftest.c && cat rose_test.c'\n\n# Enter container shell\ndocker exec -it rose-dev bash\ndocker exec -it rose-cmake bash\n```\n\n## Build Time\n\n| Build System | First Build | Incremental |\n|--------------|-------------|-------------|\n| Autotools (`make core -j8`) | ~60-90 min | seconds-minutes |\n| CMake (`make -j4`) | ~35 min | seconds-minutes |\n\n- `librose.so`: ~200 MB (CMake) to ~1.3 GB (autotools with debug)\n- Memory: Use `-j4` on 16GB systems to avoid OOM\n\n## Troubleshooting\n\n| Issue | Solution |\n|-------|----------|\n| EDG download fails | Use `weekly` branch (has EDG binaries in source tree) |\n| CMake: ROSETTA fails | Upgrade to CMake 4.x |\n| CMake: EDG link errors | Ensure using latest CMake fixes (PR #250) |\n| CMake: quadmath errors | Add `-lquadmath` or use latest fixes |\n| Permission denied | Check volume mount permissions |\n| Out of memory | Reduce `-j` parallelism |\n| Boost not found | Verify boost paths in configure\u002Fcmake |\n\n## Testing with Sample Code\n\n```bash\n# Create factorial test\ncat \u003C\u003C 'EOF' | docker exec -i rose-cmake tee \u002Ftmp\u002Ffactorial.cpp\n#include \u003Ciostream>\nint factorial(int n) { return n \u003C= 1 ? 1 : n * factorial(n-1); }\nint main() {\n    for(int i = 0; i \u003C= 10; i++)\n        std::cout \u003C\u003C \"factorial(\" \u003C\u003C i \u003C\u003C \") = \" \u003C\u003C factorial(i) \u003C\u003C std::endl;\n    return 0;\n}\nEOF\n\n# Run through ROSE (source-to-source transformation)\ndocker exec -w \u002Ftmp rose-cmake \u002Frose\u002Fbuild\u002Fbin\u002Frose-compiler factorial.cpp\n\n# Compile and run the transformed code\ndocker exec -w \u002Ftmp rose-cmake g++ rose_factorial.cpp -o factorial_test\ndocker exec -w \u002Ftmp rose-cmake .\u002Ffactorial_test\n```\n\nExpected output:\n```\nfactorial(0) = 1\nfactorial(1) = 1\n...\nfactorial(10) = 3628800\n```\n","# ROSE Docker Build\n\nBuild the ROSE source-to-source compiler in an isolated Docker container.\n\n## Why Docker?\n\nROSE requires GCC 7-10. Modern systems have GCC 11+, causing build failures. Docker provides:\n- Correct GCC version (9.x recommended)\n- All dependencies pre-installed\n- Reproducible builds\n- Edit on host, build in container\n\n## Quick Start (Autotools)\n\n```bash\n# 1. Clone ROSE\ngit clone git@github.com:rose-compiler\u002Frose.git\ncd rose && git checkout weekly\n\n# 2. Create Docker environment\nmkdir ..\u002Frose-docker && cd ..\u002Frose-docker\n\n# 3. Build and run container (see Dockerfile below)\ndocker build -t rose-dev .\ndocker run -d --name rose-dev -v $(pwd)\u002F..\u002Frose:\u002Frose\u002Fsrc rose-dev\n\n# 4. Build ROSE inside container\ndocker exec rose-dev bash -c 'cd \u002Frose\u002Fsrc && .\u002Fbuild'\ndocker exec rose-dev bash -c 'mkdir -p \u002Frose\u002Fbuild && cd \u002Frose\u002Fbuild && \\\n  \u002Frose\u002Fsrc\u002Fconfigure --prefix=\u002Frose\u002Finstall \\\n    --enable-languages=c,c++ \\\n    --with-boost=\u002Fusr \\\n    --with-boost-libdir=\u002Fusr\u002Flib\u002Fx86_64-linux-gnu \\\n    --disable-binary-analysis \\\n    --disable-java'\ndocker exec rose-dev bash -c 'cd \u002Frose\u002Fbuild && make core -j$(nproc)'\ndocker exec rose-dev bash -c 'cd \u002Frose\u002Fbuild && make install-core'\n```\n\n## Quick Start (CMake)\n\nCMake builds require CMake 4.x (3.16 fails at ROSETTA generation).\n\n```bash\n# 1. Clone ROSE\ngit clone git@github.com:rose-compiler\u002Frose.git\ncd rose && git checkout weekly\n\n# 2. Create Docker environment and build container\nmkdir ..\u002Frose-docker && cd ..\u002Frose-docker\ndocker build -t rose-dev -f Dockerfile.cmake .\ndocker run -d --name rose-cmake -v $(pwd)\u002F..\u002Frose:\u002Frose\u002Fsrc:ro rose-dev\n\n# 3. Configure with CMake\ndocker exec -w \u002Frose\u002Fbuild rose-cmake cmake \u002Frose\u002Fsrc \\\n  -DCMAKE_INSTALL_PREFIX=\u002Frose\u002Finstall \\\n  -DENABLE_C=ON \\\n  -DENABLE_TESTS=OFF \\\n  -DCMAKE_BUILD_TYPE=Release\n\n# 4. Build (use -j4 to avoid OOM on 16GB systems)\ndocker exec -w \u002Frose\u002Fbuild rose-cmake make -j4\n\n# 5. Test\ndocker exec rose-cmake \u002Frose\u002Fbuild\u002Fbin\u002Frose-compiler --version\n```\n\n### CMake Options\n\n| Option | Description |\n|--------|-------------|\n| `ENABLE_C=ON` | Enable C\u002FC++ analysis (uses EDG frontend) |\n| `ENABLE_BINARY_ANALYSIS=ON` | Enable binary analysis (no EDG needed) |\n| `ENABLE_TESTS=OFF` | Skip test compilation (faster build) |\n| `CMAKE_BUILD_TYPE=Release` | Optimized build |\n\n### CMake vs Autotools\n\n| Feature | Autotools | CMake |\n|---------|-----------|-------|\n| Stability | ✅ Mature | ⚠️ Newer |\n| C\u002FC++ analysis | ✅ Works | ✅ Works (with fixes) |\n| Build target | `make core` | `make` (full build) |\n| Incremental builds | Slower | Faster |\n| IDE integration | Limited | Excellent |\n\n## Dockerfiles\n\n### Dockerfile (Autotools)\n\n```dockerfile\nFROM ubuntu:20.04\nENV DEBIAN_FRONTEND=noninteractive\nENV TZ=America\u002FLos_Angeles\n\nRUN apt-get update && apt-get install -y \\\n    build-essential g++ gcc gfortran \\\n    automake autoconf libtool flex bison \\\n    libboost-all-dev libxml2-dev \\\n    git wget curl vim \\\n    && rm -rf \u002Fvar\u002Flib\u002Fapt\u002Flists\u002F*\n\nRUN useradd -m -s \u002Fbin\u002Fbash developer\nRUN mkdir -p \u002Frose\u002Fsrc \u002Frose\u002Fbuild \u002Frose\u002Finstall && chown -R developer:developer \u002Frose\nUSER developer\nWORKDIR \u002Frose\nCMD [\"tail\", \"-f\", \"\u002Fdev\u002Fnull\"]\n```\n\n### Dockerfile.cmake (CMake)\n\n```dockerfile\nFROM ubuntu:20.04\nENV DEBIAN_FRONTEND=noninteractive\nENV TZ=America\u002FLos_Angeles\n\n# Install build dependencies\nRUN apt-get update && apt-get install -y \\\n    build-essential g++ gcc gfortran \\\n    flex bison \\\n    libboost-all-dev libxml2-dev libreadline-dev \\\n    zlib1g-dev libsqlite3-dev libpq-dev libyaml-dev \\\n    libgmp-dev libmpc-dev libmpfr-dev \\\n    git wget curl vim \\\n    gnupg software-properties-common \\\n    && rm -rf \u002Fvar\u002Flib\u002Fapt\u002Flists\u002F*\n\n# Install CMake 4.x from Kitware (Ubuntu 20.04 has 3.16 which is too old)\nRUN wget -O - https:\u002F\u002Fapt.kitware.com\u002Fkeys\u002Fkitware-archive-latest.asc 2>\u002Fdev\u002Fnull | apt-key add - \\\n    && echo 'deb https:\u002F\u002Fapt.kitware.com\u002Fubuntu\u002F focal main' > \u002Fetc\u002Fapt\u002Fsources.list.d\u002Fkitware.list \\\n    && apt-get update && apt-get install -y cmake \\\n    && rm -rf \u002Fvar\u002Flib\u002Fapt\u002Flists\u002F*\n\nRUN useradd -m -s \u002Fbin\u002Fbash developer\nRUN mkdir -p \u002Frose\u002Fsrc \u002Frose\u002Fbuild \u002Frose\u002Finstall && chown -R developer:developer \u002Frose\nUSER developer\nWORKDIR \u002Frose\nCMD [\"tail\", \"-f\", \"\u002Fdev\u002Fnull\"]\n```\n\n## EDG Binary Handling\n\nEDG (C++ frontend) binaries are required for C\u002FC++ analysis. The build checks:\n\n### Autotools\n1. Build directory for existing tarball\n2. Source tree at `src\u002Ffrontend\u002FCxxFrontend\u002FroseBinaryEDG-*.tar.gz`\n3. Network download from `edg-binaries.rosecompiler.org`\n\n### CMake\n1. Source tree at `src\u002Ffrontend\u002FCxxFrontend\u002FroseBinaryEDG-*.tar.gz` (auto-detected)\n2. Extracts matching tarball based on GCC version at build time\n3. Links `libroseEDG.a` to `librose.so` automatically\n\nIf server is down, ensure source tree has EDG binaries (included in `weekly` branch).\n\n## Common Commands\n\n### Autotools\n```bash\n# Rebuild after source changes\ndocker exec rose-dev bash -c 'cd \u002Frose\u002Fbuild && make core -j8'\n\n# Install\ndocker exec rose-dev bash -c 'cd \u002Frose\u002Fbuild && make install-core'\n```\n\n### CMake\n```bash\n# Rebuild after source changes  \ndocker exec -w \u002Frose\u002Fbuild rose-cmake make -j4\n\n# Install\ndocker exec -w \u002Frose\u002Fbuild rose-cmake make install\n```\n\n### Both\n```bash\n# Test ROSE compiler\ndocker exec rose-dev \u002Frose\u002Finstall\u002Fbin\u002Frose-compiler --version\ndocker exec rose-cmake \u002Frose\u002Fbuild\u002Fbin\u002Frose-compiler --version\n\n# Source-to-source test\ndocker exec rose-dev bash -c 'echo \"int main(){return 0;}\" > \u002Ftmp\u002Ftest.c && \\\n  \u002Frose\u002Finstall\u002Fbin\u002Frose-compiler -c \u002Ftmp\u002Ftest.c && cat rose_test.c'\n\n# Enter container shell\ndocker exec -it rose-dev bash\ndocker exec -it rose-cmake bash\n```\n\n## Build Time\n\n| Build System | First Build | Incremental |\n|--------------|-------------|-------------|\n| Autotools (`make core -j8`) | ~60-90 min | seconds-minutes |\n| CMake (`make -j4`) | ~35 min | seconds-minutes |\n\n- `librose.so`: ~200 MB (CMake) to ~1.3 GB (autotools with debug)\n- Memory: Use `-j4` on 16GB systems to avoid OOM\n\n## Troubleshooting\n\n| Issue | Solution |\n|-------|----------|\n| EDG download fails | Use `weekly` branch (has EDG binaries in source tree) |\n| CMake: ROSETTA fails | Upgrade to CMake 4.x |\n| CMake: EDG link errors | Ensure using latest CMake fixes (PR #250) |\n| CMake: quadmath errors | Add `-lquadmath` or use latest fixes |\n| Permission denied | Check volume mount permissions |\n| Out of memory | Reduce `-j` parallelism |\n| Boost not found | Verify boost paths in configure\u002Fcmake |\n\n## Testing with Sample Code\n\n```bash\n# Create factorial test\ncat \u003C\u003C 'EOF' | docker exec -i rose-cmake tee \u002Ftmp\u002Ffactorial.cpp\n#include \u003Ciostream>\nint factorial(int n) { return n \u003C= 1 ? 1 : n * factorial(n-1); }\nint main() {\n    for(int i = 0; i \u003C= 10; i++)\n        std::cout \u003C\u003C \"factorial(\" \u003C\u003C i \u003C\u003C \") = \" \u003C\u003C factorial(i) \u003C\u003C std::endl;\n    return 0;\n}\nEOF\n\n# Run through ROSE (source-to-source transformation)\ndocker exec -w \u002Ftmp rose-cmake \u002Frose\u002Fbuild\u002Fbin\u002Frose-compiler factorial.cpp\n\n# Compile and run the transformed code\ndocker exec -w \u002Ftmp rose-cmake g++ rose_factorial.cpp -o factorial_test\ndocker exec -w \u002Ftmp rose-cmake .\u002Ffactorial_test\n```\n\nExpected output:\n```\nfactorial(0) = 1\nfactorial(1) = 1\n...\nfactorial(10) = 3628800\n```\n",{"name":5,"description":7},"main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fchunhualiao\u002Frose-docker-build-skill",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill rose-docker-build",{"tool":39,"command":40},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill rose-docker-build",{"tool":42,"command":43},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill rose-docker-build","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fchunhualiao\u002Frose-docker-build-skill\u002FSKILL.md",true,[],[48,56,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M778GGXG2VQ0YF31W2MKGMQZ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":55},"01M778G7BH8SBJ9FJ6C3G7CB1K","ceaser","Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":55},"01M778FYCJQZWFKKX5FYMK3S47","ceaser-send","Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":55},"01M778FQQNSEYA3HJKZBPQ4M9Z","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":55},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":55},"01M778F88D8PQ9MQ0KNW2TJ8ZH","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]