agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/NeMo-Relay/.agents/skills/review-doc-style/SKILL.md

review-doc-style

Skill238 starsChanged 2 months agoApache-2.0View on GitHub

Review NeMo Relay documentation, examples, or public text for NVIDIA technical writing style, terminology, and repository accuracy. Do not use for ordinary implementation review.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read references/nvidia-style-guide.md for the fast-path checklist and severity model.

    line 18
  2. Distinctive:

    Verify MDX files use JSX delimiters for top-of-file SPDX comments.

    line 27
  3. Distinctive:

    If no issues are found, say so and identify any commands or examples that were not executed.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Review Documentation Style

Prioritize factual accuracy over copy polish. Confirm commands, package names, APIs, paths, supported bindings, and public behavior against the current repository before reporting style findings.

Review Flow

  1. Identify the changed documentation, examples, or public strings and any corresponding entry points such as README.md, docs/index.yml, or package READMEs.
  2. Read references/nvidia-style-guide.md for the fast-path checklist and severity model.
  3. Open only the focused reference that resolves an actual ambiguity:
    • references/nvidia-style-technical-docs.md for structure, procedures, examples, links, tables, UI text, or accessibility.
    • references/nvidia-style-language-mechanics.md for voice, grammar, punctuation, dates, numbers, units, or plain English.
    • references/nvidia-style-brand-terminology.md for NVIDIA and product names, trademarks, acronyms, legal copy, or SEO.
  4. Verify MDX files use JSX delimiters for top-of-file SPDX comments.
  5. Report findings in severity order with a file and line, reader impact, and a concrete rewrite or direction. Omit preference-only findings unless the user requested a deep copyedit.

If no issues are found, say so and identify any commands or examples that were not executed.

References

  • CONTRIBUTING.md
  • references/nvidia-style-guide.md
  • Open only the focused NVIDIA style reference selected in step 3.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free