380 skills (repositories by NVIDIA) · sorted by popularity
Review NemoClaw issues and pull requests, propose issue types, project priorities, statuses, and labels, then apply only approved changes. Supports individual items and batch triage, with explanations and a report of each update.
Continuously monitor automatic end-to-end tests on NemoClaw main, group failures by root cause, and coordinate fixes and peer reviews through GitHub. Track ownership and merge readiness while checking whether later runs confirm each repair.
Compare multiple NemoClaw pull requests addressing the same issue. It checks merge eligibility, correctness, quality, and attribution, then produces an evidence-based recommendation for merging or choosing a candidate for further repair.
Review a NemoClaw pull request for security risks by examining changed code, configuration, and dependencies. Assess nine categories and report findings with severity, file locations, and recommended fixes, alongside an overall assessment of whether it is safe to merge.
Reorganize NemoClaw documentation into focused pages with clearer navigation and a single home for each topic. Plan or implement structural changes while preserving useful information and existing published URLs, then validate routes, links, and builds.
Publish or update a NemoClaw pull request and track automated checks and reviews through completion. It preserves the requested scope, coordinates repairs for valid findings, and reports the latest commit’s results and remaining blockers.
Prepare a local NemoClaw development environment, repair setup problems, or check readiness. It also handles explicitly requested command-line access, runtime onboarding, and launching the coding agent pinned by the project.
Investigate failing or flaky NemoClaw end-to-end tests, which check complete workflows. Trace each assertion through its inputs and implementation, including cleanup and dependent jobs, and produce an evidence ledger to guide authorized repairs and reruns.
Prepare a daily NemoClaw maintenance plan by ranking pending pull requests and issues, checking work carried over from earlier versions, and selecting release targets. Produce a queue with owners, next actions, and merge readiness.
Find open NemoClaw security pull requests marked Urgent or High in the project tracker. Connect them to issues, identify competing or superseding proposals, and recommend which request a maintainer should review first.
Analyze the full retained history of one NemoClaw pull request to identify contributor, review, and automation delays. Generate a summary and an interactive timeline file, then compare observed timing with a default ten-minute target or a requested alternative.
Find official NemoClaw documentation for installation, configuration, operation, and troubleshooting. Get source-linked guidance tailored to the selected operating system, agent variant, and inference provider, with optional documentation MCP setup when requested.
Classify a failed NemoClaw GitHub Actions job using logs with sensitive information hidden and output size limited. Optionally inspect saved artifacts to identify failure patterns and gather evidence for further investigation.
Turn a named NemoClaw issue into an implementation plan with clear ownership, scope, completion criteria, and validation evidence. For larger changes, define independently useful steps, their dependencies, and delivery order.
Prepare and create a signed NemoClaw release tag for a requested version, then monitor release workflows, documentation, and published images. It records maintainer decisions and drafts an announcement after verifying the remote tag.
Update NemoClaw documentation after merged changes or audit it for outdated guidance. Verify current behavior against source and tests, edit the pages responsible for that guidance, and check affected links and generated variants.
Clean up GitHub issue and pull request titles by removing bracketed NemoClaw tags. It previews proposed changes, applies them after approval, and checks for remaining matches while preserving other tags and plain-text mentions.
Audit and upgrade NemoClaw dependencies, including Hermes and base images. Trace upstream changes to affected code, implement required migrations, and verify tests, distributed artifacts, and the versions actually selected for use.
Validate the staging NemoClaw Brev Launchable by checking its web deployment flow, environment access, deployed image, and preinstalled user journey. Report inference results and missing dependencies separately as advisory evidence outside automated end-to-end testing.
Analyze saved NemoClaw CI timings to rank consistently slow command-line tests and compare base-image publication with reuse. Read-only analyzers report execution times, runner queues, and sample coverage as bounded JSON output.
Find the right NemoClaw skill for a task using a catalog organized for users, maintainers, and contributors. Understand which skill handles documentation, setup, implementation, reviews, or releases, and choose an appropriate starting point.
Close a NemoClaw maintenance day by consolidating documentation and changelog updates, reviewing merged and unfinished work, and preparing a release handoff. When requested, pass the version to the dedicated skill that verifies and creates the release tag.
Answer NemoClaw maintainer questions using policy references covering issue and pull request assessment, labels, project fields, releases, and competing contributions. It explains the relevant rules in plain language through a read-only workflow.
Implement or review a managed runtime provider for NemoClaw. Check its required interfaces, activation requirements, saved provider identity, and lifecycle behavior, then report validation evidence and any remaining qualification requirements.