SKILLEMALL.ai
GitHub ↗ RU Sign in

CC nemoclaw-contributor-onboard

Set up, repair, or check a NemoClaw contributor checkout. Also handles requested development CLI exposure, runtime onboarding, and pinned-agent launch.

NVIDIA/NemoClaw Agent Skills author: NVIDIA Apache-2.0 3 files body ≈ 1 398 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Set up, repair, or check a NemoClaw contributor checkout.

As a process C 61/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationGitHubAI and agentsData and analyticsCommercetype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
C
61/100
Has gaps
Inputs and preconditions w 11
0
When it triggers w 12
20
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 61/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 7 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 60Tools and files. Uses tools (bash, python, node) that frontmatter does not declare
  • 100Steps. 19 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1398 tokens
  • 100Progress reporting. Reports progress
  • medium 7 test cases, all positive: not one "should refuse" or "should ask first"
  • low No test case covers injection arriving through data

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 151: enough signal without eating the budget
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 19 items
  • +4Has examples (2 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.