CtrlK
BlogDocsLog inGet started
Tessl Logo

nemoclaw-contributor-onboard

Prepare a NemoClaw source checkout for compliant contribution through the repository's one-command setup and readiness doctor. Use when a new contributor asks to set up a development machine, prepare a checkout for a first PR, repair local contributor tooling, verify contributor readiness, launch the pinned coding agent, or decide whether optional runtime onboarding is needed. Trigger keywords - contributor setup, developer onboarding, first PR, dev setup, dev doctor, repair checkout, prepare development machine.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an instruction-only workflow skill that is lean, actionable, and rigorously sequenced with approval gates and validation loops appropriate to its destructive/risky operations. With no bundle files, progressive disclosure is satisfied by clean sectioning and a single one-level reference.

DimensionReasoningScore

Conciseness

Lean, assumes Claude's competence throughout — no padding, no over-explanation of basic concepts — and each section earns its place (e.g., 'Use the repository setup script as the executable source of truth. Do not duplicate its ... logic').

5 / 5

Actionability

Fully executable guidance with copy-paste-ready commands per intent — './scripts/dev-setup.sh --doctor', '--repair', '--expose-cli', '--with-runtime', 'npm run agent', 'gh auth login -h github.com' — covering the common routing cases.

5 / 5

Workflow Clarity

A clearly sequenced multi-step flow (Trust → Route → Handle Changes → Runtime → Launch Agent → Hand Off → Report) with explicit validation checkpoints and approval gates for risky operations ('obtain explicit approval before running it', rerun doctor after remediation, 'readiness passes' before launching the agent).

5 / 5

Progressive Disclosure

No bundle files are present; the skill is a single well-organized file with clear section headers and a one-level-deep external reference ('../_shared/git-github-hard-end.md'), so navigation is easy with no nested references.

5 / 5

Total

20

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong across all dimensions: it states concrete capabilities, includes an explicit 'Use when' trigger clause with natural synonyms, and is tightly scoped to a distinct NemoClaw niche. Third-person voice is maintained throughout, so no specificity penalty applies.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'set up a development machine, prepare a checkout for a first PR, repair local contributor tooling, verify contributor readiness, launch the pinned coding agent' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (prepare a checkout via one-command setup and readiness doctor) and 'when' (a clear 'Use when...' clause enumerating concrete trigger scenarios).

5 / 5

Trigger Term Quality

Provides a dedicated, comprehensive keyword list with natural synonyms a user would say — 'contributor setup, developer onboarding, first PR, dev setup, dev doctor, repair checkout, prepare development machine'.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (NemoClaw contributor onboarding) with distinctive triggers; the repo-specific framing minimizes overlap with other skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
NVIDIA/NemoClaw
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.