390 skills (repositories by NVIDIA) · sorted by popularity
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.
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.
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 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.
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.
Draft a NemoClaw release announcement from verified GitHub tags and shipped pull requests. Produce a local Markdown draft with an opening narrative, categorized changes, visible pull request links, and thanks to external contributors.
Review agent skills for risky behavior, excessive permissions, and hidden data sharing. It combines static scanning, which checks known risk patterns without running code, with source review to produce an evidence-based installation verdict.
Process one recommendation selected by ID from a local issue or CI triage report. Apply, reject, or defer it, record the outcome, and obtain separate confirmation before each change made on GitHub.
Review OpenShell issues, pull requests, and failed main-branch checks, then build a local Markdown report with linked evidence and ranked recommendations. Saved progress helps resume an unfinished triage pass without changing GitHub.
Promote the latest qualified OpenShell prerelease to a stable release after maintainer approval. Check that qualification matches the tag and commit, present changes since the previous stable version, and monitor the release workflow through completion.
Implement an authorized fix for a reviewed security issue, check the plan against current code, and add regression tests to catch recurrence. Verify affected components and open a pull request that closes the issue while respecting disclosure rules.
Develop and fix OpenShell’s keyboard-driven terminal interface using guidance on screen structure, background data fetching, themes, and navigation. Follow existing implementation patterns to add features that fit the interface’s established behavior.
Diagnose unreachable or unhealthy OpenShell gateways and sandbox startup failures. Identify the underlying execution platform, then examine logs, authentication, certificates, and configuration with the matching tools to narrow down the cause.
Assess OpenShell issues by checking first-hand use cases, reproduction evidence, existing behavior, and duplicates. Prepare a concise technical assessment, request specific missing information, and leave acceptance and roadmap decisions to human maintainers.
Review a GitHub pull request or branch and receive a concise summary of its purpose, design choices, and notable code. Check linked issue acceptance and highlight evidence-based concerns through their observable impact on users.
Handle network requests blocked by an OpenShell sandbox by checking its current access rules and proposing the smallest necessary change. Wait for approval and confirmation that the policy has reloaded before retrying the request.
Keep repository contribution guidance consistent after workflow changes. Compare agent skills, coding guidance, contributor documentation, and issue and pull request templates, then fix contradictory instructions, outdated references, and mismatched inventories.
Set up and manage a local Kubernetes development environment for OpenShell using k3d, Skaffold, and Helm. Build and deploy changes, inspect traces, configure optional authentication components, and test behavior across multiple gateway replicas.
Generate an OpenShell SBOM, an inventory of software components, with Syft. Fill missing license details from public registries, export CSV files for compliance review, and inspect or validate SBOMs attached to container images.
Maintain and validate OpenShell builds for Windows on x64 and ARM64 using MSVC, Microsoft's C++ toolchain. Check compilation, build executables, run tests on native hosts, and report artifacts and unsupported driver behavior.
Create GitHub pull requests with the gh command-line tool. Check linked issues, contributor permissions, branch conventions, and relevant tests, then prepare a title and description that follow the project's contribution rules.
Launch and supervise gator agents for specific GitHub issues or pull requests in OpenShell. Check isolated execution environments, inspect logs, restart stalled agents, and test model or image overrides without changing default settings.
Review an authorized security issue in its private workflow. Check the affected code, assess whether the report is valid, explain severity and attack prerequisites, and propose a remediation plan with focused tests.
Review recent Git commits to find changes that affect users, then update the relevant documentation pages. Identify missing pages, explain changed behavior or migration steps, and validate the resulting documentation with the project's build tools.