Back to Skills

nemo-rl-docs

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.

2,779stars322forksUpdated 8/4/2026

Security Assessment

Safe(98/100)
Security Score98/100

About nemo-rl-docs

The nemo-rl-docs skill is a concise conventions guide for writing and updating documentation in the NeMo-RL project. It solves the common drift between code and docs by codifying a few clear rules that keep documentation discoverable and consistently formatted, and it deliberately scopes itself out of non-documentation tasks such as bug fixes, test fixes, dependency bumps, refactoring, CI/CD changes, and performance tuning.

The guidance is short and specific: when a new markdown doc is added under docs or a markdown file is renamed, docs/index.md must be updated so the document appears in the most appropriate section; classes and functions use Google-style docstrings that Sphinx can parse, with docstrings preferred over comments for interfaces used outside a file; and when a new feature is added, documentation in the docs directory should be updated or created to match it. It explicitly notes that documentation changes are not required for bug fixes or CI-related changes.

Target users are developers and engineers contributing to NeMo-RL who are adding or updating documentation, adding new markdown files, or reviewing docstrings during code review. This is a thin, guide-only convention reference rather than a tool that executes anything; it points to the Google Python Style Guide and NeMo-RL documentation as external references and carries no scripts or automation.

FAQ

When should this skill be used?

When adding or updating documentation, adding a new markdown file, or reviewing docstrings. It should not be used for bug fixes, test fixes, dependency bumps, refactoring, CI/CD changes, or performance tuning.

What docstring style does NeMo-RL use?

Google-style docstrings for classes and functions, because they are parseable by Sphinx. Docstrings are preferred over comments for interfaces that may be used outside a file.

What do I need to do when adding a new doc?

When a new markdown doc is added under docs or a markdown file is renamed, update docs/index.md so the document appears in the most appropriate section.

Are docs required for every change?

No. Documentation changes are not required for bug fixes or CI-related changes. New features, however, should update or create matching documentation under the docs directory.

Does this skill run any code?

No. It is a guide-only conventions reference with no scripts or executable steps; it simply describes documentation practices and links to external style references.

All Files

5 files
skill.oms.sig4.5 KB
View
BENCHMARK.md4.1 KB
View
SKILL.md1.4 KB
View
evals/evals.json2.4 KB
View
skill-card.md3.6 KB
View

Install nemo-rl-docs

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

nvidia/skills