Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/nemo-rl-docs
Documentation conventions for NeMo-RL. Covers docs/index.md updates and docstring format.
Passed 18 of 21 test cases with the skill, and 11 of 21 without it.
and 4 more in the full report
7 fixed12 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
Which documentation generator parses the Python docstrings written for classes and functions in this codebase?
| Checked | Without skill | With skill |
|---|---|---|
| Mentions Sphinx as the parser engine for python docstrings. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
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.
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.
test cases passed, vs 11 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.