Menu
SkillsMP has collected 49 skills from NVIDIA/nemoclaw-community. Open a skill to review its source and details.
Showing 40 of 49 collected skills.
Read public GitHub pull requests, produce a short triage brief, and draft feature test cases grounded in the pull request description and diff. Use when a Slack user provides a public GitHub repository or pull request.
Check the memory against its schema and fix what can be fixed, so the store degrades visibly rather than silently.
Create and update the memory pages that the ranking job gates its top tier on, from evidence the selector collected.
Guide NemoClaw Community contributors through classifying, naming, adding, moving, renaming, and reviewing repository examples. Use when work affects examples, recipes, partner contributions, field demos, launchables, developer tools, the example catalog, or…
Compare findings across Slack, GitHub, NVIDIA forums, and Outlook to identify alignment gaps, missing coverage, and follow-ups.
Read the configured live GitHub repository through authenticated, policy-scoped GitHub REST GET requests.
Guide users through Hermes availability checks and the optional host-side auto-heal setup without crossing the sandbox-to-host boundary.
Route product, program, engineering, data and ML, quality, SRE, security, and developer-community work through the eight local role lenses packaged with the developer-community-chief-of-staff recipe in nemoclaw-community. Use for explicit NVTeam or persona…
Search the Outlook mailbox via Microsoft Graph to find and read emails that help answer user questions.
Discover Slack channels by topic, team, or domain and determine the channel ID.
Read and summarize Slack channel history from inside the NemoClaw sandbox.
Query the host-side source-etls REST mirror for GitHub discussions, historical GitHub mirror data, and NVIDIA forums research.
This skill should be used when a learner is working through Module 1 ("Build an Agent") of the Build-an-Agent workshop and wants help understanding the concepts, notebooks, or code — e.g. "/module-1 what are agents?", "/module-1 explain the ReAct pattern",…
This skill should be used when a learner is working through Module 5 ("Deep Agents") of the Build-an-Agent workshop and wants help understanding the concepts, the code, or sandboxing — e.g. "/module-5 what are deep agents?", "/module-5 explain the four…
This skill should be used when a learner is working through Module 6 ("Agent Safety") of the Build-an-Agent workshop and wants help understanding the concepts, the code, or the NemoClaw stack — e.g. "/module-6 why isn't HITL or a container enough?",…
This skill should be used when a learner is working through Module 7 ("Agent Harnesses & Skills") of the Build-an-Agent workshop and wants help understanding the concepts, the harness landscape, the lab code, or portable/GPU skills — e.g. "/module-7 what is a…
Operator/host side of running the NVIDIA "Build an Agent" DevX workshop inside an OpenShell/NemoClaw sandbox. In the NemoClaw community repo this is the PRIMARY workshop-setup entry point: use it for "set up / run the Build-an-Agent workshop" requests when…
Set up the NVIDIA "Build an Agent" DevX workshop as a working JupyterLab environment from INSIDE a locked-down OpenShell/NemoClaw sandbox, and hand the user the token URL + access commands. This is the PRIMARY workshop-setup path in the NemoClaw community…
This skill should be used when a learner wants to navigate or understand the Build-an-Agent workshop as a whole — e.g. "/workshop where do I start?", "what order should I do the modules in?", "what does Module 3 need before I start?", "which module covers RAG…
Automated web accessibility scanning (axe-core) driven by patchright + real Google Chrome — audits sites behind bot walls and behind auth
Decide which newly-arrived email and Slack messages create an obligation for the user, and craft the row that represents each one.
Keep the memory inside its size limits by compacting rather than truncating, so it stays readable as it ages.
Re-judge open obligations against their current state in the world and re-rank them, on a schedule that does not depend on new mail arriving.
Update a bounded preference policy from the user's repeated corrections, without ever overwriting the user's own choices.
Read one of the configured GitLab projects through authenticated, policy-scoped REST GET requests.
Search the current public web through the recipe's optional, policy-scoped Tavily integration and return cited titles, URLs, snippets, and search metadata. Use for current public information that is not available from the configured Slack, Outlook, GitHub, or…
Compare findings across Slack, GitHub, NVIDIA forums, and Outlook to identify alignment gaps, missing coverage, and follow-ups.
Read an allowed live GitHub repository through authenticated, policy-scoped GitHub REST GET requests.
Query the host-side source-etls REST mirror for GitHub discussions, historical GitHub mirror data, and NVIDIA forums research.
Read and summarize Slack channel history from inside the NemoClaw sandbox.
Search the Outlook mailbox via Microsoft Graph to find and read emails that help answer user questions.
Queue deep, multi-step research and analysis tasks to the DeepAgents worker. Supports execution depth presets, request-specific rubrics, SubAgent delegation, and RubricMiddleware cross-validation.
Screen x402 payments with an advisory Blackwall verdict, then submit a payment intent to the host-side release gate. You prepare payments; only the gate can settle them.
Review one exact pull-request head with the read-only Hermes review advisor, an ordered evidence protocol, and a canonical finding ledger.
Answer NVIDIA technical questions by searching authorized sources and citing retrieved evidence rather than relying on memory. Use for NVIDIA SDK or library usage and sample code, technology recommendations (including models and NGC/GitHub assets), adoption…
Provide read-only NemoClaw Community maintainer policy for Issue Type, labels, title conventions, triage, and example publication metadata.
Coach a NemoClaw Hermes sub-agent through Blender, OVRTX, OVPhysX, USD, rendering, simulation, and live Blender-control tasks. Use when Codex should delegate specialized execution to Hermes while managing sandbox boundaries, preventing overlapping runs,…
Legacy compatibility entry point for prompts that explicitly request coordinate-nemoclaw-blender. Use coach-nemoclaw-hermes for new Codex-coached Blender, OVRTX, OVPhysX, USD, rendering, or simulation tasks.
Route Blender, USD, OVRTX, and OVPhysX work when Hermes terminal and file tools run in an OpenShell sandbox but Blender MCP runs inside a host Blender process. Use before any task that inspects the active scene, mentions host or sandbox paths, exports or…
Verify Blender Python properties, enums, operators, animation APIs, and add-on interfaces against the running Blender build before writing or executing uncertain bpy code. Use for any Blender scene edit, render setup, animation, import/export, or add-on task…