What problem does it solve? New contributors to the NemoClaw repository often struggle with configuring a development machine correctly—installing dependencies, setting up Git hooks, configuring commit signing, and verifying readiness before a first PR. This Skill routes all of that through the repository's own setup script and doctor, avoiding duplicated or drifting setup logic. ## Core Features & Use Cases - Intent-based routing: Distinguishes readiness checks (--doctor), initial setup, explicit repair (--repair), CLI exposure (--expose-cli), and runtime onboarding (--with-runtime) so only the requested action runs. - Trust-first execution: Reviews the checkout diff against trusted origin/main before running any checkout-local code, and requires explicit approval for host-level changes like package installs, GitHub auth, or signing keys. - First-PR guidance: Explains the Conventional Commits workflow, DCO sign-off, commit signing, and PR template requirements before implementation begins. - Use Case: A new contributor clones NemoClaw and asks their coding agent to set up the machine. The agent reads AGENTS.md and CONTRIBUTING.md, runs ./scripts/dev-setup.sh, fixes any doctor-reported issues with approval, and confirms readiness for a first PR. ## Quick Start Use the nemoclaw-contributor-onboard skill to set up this machine as a NemoClaw contributor and verify it is ready for a first PR.