skills.rest
sayalinvidia
sayalinvidiaCOMMUNITY
Explore all skills by this author →
GitHub

nemo-rl-docs

Enforce Google-style docstrings and documentation conventions for NeMo-RL projects.

Updated Apr 16, 2026
Search Tags:#documentation#docstrings#docs#coding-standards#knowledge-sharing#google-style#nemo-rl
One-click install
npx skills add https://github.com/sayalinvidia/sayali-skills-test --skill nemo-rl-docs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nemo-rl-docs
Source: https://github.com/sayalinvidia/sayali-skills-test/tree/main/skills/nemo-rl-docs
Command: npx skills add https://github.com/sayalinvidia/sayali-skills-test --skill nemo-rl-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

NeMo-RL projects often suffer from inconsistent documentation and missing guidance for docstrings and docs updates, leading to lower code quality and harder onboarding.

Core Features & Use Cases

  • Documentation conventions: enforce Google-style docstrings and consistent docs/index.md updates across the codebase for NeMo-RL.
  • Guided maintenance: provide clear procedures for adding/updating docs, docs pages, and docstrings within the NeMo-RL ecosystem.
  • Use Case: when adding a new feature, follow the conventions to update docs/, add new markdown files, and ensure docs/index.md reflects the change.

Quick Start

Consult the Nemo-RL documentation conventions to apply consistent documentation practices when adding or updating documentation.

Frequently Asked Questions about nemo-rl-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce Google-style docstrings in NeMo-RL projects?▼

Enforce Google-style docstrings in NeMo-RL projects by applying standardized documentation conventions that guide contributors when adding or updating code, ensuring consistent formatting and improving code quality.

What is the standard process for updating NeMo-RL documentation when adding a new feature?▼

The standard process for updating NeMo-RL documentation requires adding new markdown files to the docs/ directory and ensuring docs/index.md reflects the change to maintain consistent knowledge sharing.

Why does my NeMo-RL contribution require updates to docs/index.md?▼

NeMo-RL contributions require docs/index.md updates to enforce documentation conventions and ensure the project's central index accurately reflects all newly added or modified markdown files.

Can I use other docstring formats instead of Google-style for NeMo-RL coding standards?▼

No, Google-style docstrings are explicitly required for NeMo-RL projects. Adhering to this specific format enforces consistent documentation conventions and standardizes knowledge sharing across the codebase.

What are the limitations of relying on ad-hoc documentation in NeMo-RL projects?▼

Relying on ad-hoc documentation in NeMo-RL projects leads to inconsistent docs and missing guidance for docstrings, which lowers code quality and makes onboarding significantly harder for new contributors.

Related Skills

Explore More Content & Communication Skills→
toinfinityaitoinfinityai

docstring

Generate Google-style docstrings for Python modules, classes, and constructors.

Official
Advanced
auldsyababuaauldsyababua
6

markdown-validation

Validate Markdown files for syntax, links, and formatting standards.

Community
Advanced
yo-stevenyo-steven

docs

Update docs index entries and standardize Google-style docstrings for NeMo-RL.

Community
Basic
AbeJitsuAbeJitsu

format-standardize

Apply user-defined formatting standards across code, documentation, and content outputs using ESLint and Prettier.

Community
Basic