What problem does it solve?
New contributors to the NemoClaw repository often struggle to configure a development machine correctly, verify readiness, and know which setup mode (initial, repair, doctor, CLI exposure, runtime onboarding) applies to their situation.
Core Features & Use Cases
- Intent-based routing: Runs
./scripts/dev-setup.sh in the correct mode (default, --doctor, --repair, --expose-cli, --with-runtime) based on whether the user wants readiness checks, initial setup, repair, CLI exposure, or runtime onboarding.
- Trust-first execution: Compares the checkout against a refreshed trusted
origin/main and requires explicit approval before running any changed execution surface.
- Safe remediation: Pauses for approval before host package changes, Git identity or signing-key configuration, and GitHub authentication, and never exposes secrets in output.
- Use Case: A new contributor clones NemoClaw and asks to prepare their machine for a first PR; the Skill runs the setup script, verifies readiness with the doctor, and hands off to the issue-planning workflow.
Quick Start
Ask the agent to set up your machine as a NemoClaw contributor and verify the checkout is ready for a first PR.