Generated banner for Nemo Rl Docs
Generated logo for Nemo Rl Docs

Nemo Rl Docs

NVIDIAOfficialPublished by NVIDIA

  • Skill
  • Guidelines
  • Documents and content
  • Apache-2.0
  • Medium risk

From the author

Documentation conventions for NeMo-RL. Covers docs/index.md updates and docstring format. Do NOT use for: bug fixes, test fixes, dependency bumps, refactoring, CI/CD changes, performance tuning, or any task that does not involve writing or updating documentation.
— the description by NVIDIA

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides the established guidelines for maintaining documentation within the NeMo-RL project. It outlines the requirements for updating the central index file when new documentation is added and specifies the use of Google-style docstrings to ensure compatibility with Sphinx documentation generation.

What it does

  • Defines the structure for updating the project index file.
  • Mandates Google-style docstrings for classes and functions.
  • Provides guidance on where to place new documentation files.
  • Distinguishes between appropriate use of docstrings versus internal code comments.

When to use it

  • When adding or updating project documentation.
  • When creating new markdown files within the documentation directory.
  • When reviewing or writing docstrings for public interfaces.
  • When determining the correct location for new feature documentation.

Advantages

  • Ensures consistent documentation structure across the project.
  • Facilitates automated documentation generation via Sphinx.
  • Improves readability and maintainability of public-facing code interfaces.

Usage examples

“How should I format my function docstrings?”
The agent will advise using Google-style docstrings to ensure they are correctly parsed by Sphinx.
“Where do I register a new documentation file?”
The agent will instruct you to update the docs/index.md file and place the new file in the appropriate section.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/nvidia/nemo-rl-docs/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip nemo-rl-docs.zip -d .agents/skills

Documentation by NVIDIA

Documentation Conventions

Keep docs/index.md Up to Date

When a new markdown doc is added under docs/**/*.md or a markdown file is renamed, ensure that @docs/index.md is updated and the document appears in the most appropriate section.

Docstring Format

Use Google style docstrings for classes and functions. These are parseable by Sphinx.

For interfaces that may be used outside a file, prefer docstrings over comments. Comments should be reserved for code within a function or interfaces local to a file.

Document New Features

When a new feature is added, update or create documentation in the docs/ directory that most closely matches the feature. Look at existing docs to find the best fit — if none exists, create a new doc and add it to @docs/index.md.

Documentation changes are not required for bug fixes or CI-related changes.

Files

skill-card.md

Description: <br>

Documentation conventions for NeMo-RL. Covers docs/index.md updates and docstring format. <br>

This skill is ready for commercial/non-commercial use. <br>

Owner

NVIDIA <br>

License/Terms of Use: <br>

Apache 2.0 <br>

Use Case: <br>

Developers and engineers adding or updating documentation in the NeMo-RL project, including maintaining docs/index.md and writing Google-style docstrings. <br>

Deployment Geography for Use: <br>

Global <br>

Known Risks and Mitigations: <br>

Risk: Review before execution as proposals could introduce incorrect or misleading guidance into skills. <br> Mitigation: Review and scan skill before deployment. <br>

Reference(s): <br>

Skill Output: <br>

Output Type(s): [Configuration instructions, Analysis] <br> Output Format: [Markdown] <br> Output Parameters: [1D] <br> Other Properties Related to Output: [None] <br>

Evaluation Agents Used: <br>

  • Claude Code (claude-code) <br>

  • Codex (codex) <br>

Evaluation Tasks: <br>

Evaluated against 5 internal evaluation tasks (3 positive skill-activation, 2 negative activation) with 2 attempts per task. <br>

Evaluation Metrics Used: <br>

Reported benchmark dimensions: <br>

  • Security: Checks whether skill-assisted execution avoids unsafe behavior such as secret leakage, destructive commands, or unauthorized access. <br>

  • Correctness: Checks whether the agent follows the expected workflow and produces the correct final output. <br>

  • Discoverability: Checks whether the agent loads the skill when relevant and avoids using it when irrelevant. <br>

  • Effectiveness: Checks whether the agent performs measurably better with the skill than without it. <br>

  • Efficiency: Checks whether the agent uses fewer tokens and avoids redundant work. <br>

Underlying evaluation signals used in this run: <br>

  • security: Checks for unsafe operations, secret leakage, and unauthorized access. <br>

  • skill_execution: Verifies that the agent loaded the expected skill and workflow. <br>

  • skill_efficiency: Checks routing quality, decoy avoidance, and redundant tool usage. <br>

  • accuracy: Grades final-answer correctness against the reference answer. <br>

  • goal_accuracy: Checks whether the overall user task completed successfully. <br>

  • behavior_check: Verifies expected behavior steps, including safety expectations. <br>

  • token_efficiency: Compares token usage with and without the skill. <br>

Evaluation Results: <br>

DimensionNumclaude-codecodex
Security8100% (+0%)100% (+0%)
Correctness891% (+7%)83% (+11%)
Discoverability899% (-1%)90% (+5%)
Effectiveness881% (+8%)80% (+18%)
Efficiency885% (-0%)79% (+3%)

Skill Version(s): <br>

69adf2b2e (source: git SHA, committed 2026-06-01) <br>

Ethical Considerations: <br>

NVIDIA believes Trustworthy AI is a shared responsibility and we have established policies and practices to enable development for a wide array of AI applications. When downloaded or used in accordance with our terms of service, developers should work with their internal team to ensure this skill meets requirements for the relevant industry and use case and addresses unforeseen product misuse. <br>

(For Release on NVIDIA Platforms Only) <br> Please report quality, risk, security vulnerabilities or NVIDIA AI Concerns here. <br>

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

What our scanner noticed· Medium risk

  • Large base64-encoded blobs

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
NVIDIA
Publisher
NVIDIA (Official)
Source
NVIDIA/skills · skills/nemo-rl-docs · commit fce3cca
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE-APACHE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by NVIDIA.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download nemo-rl-docs.zip