domains / families / science / nemotron-policy-generator
nemotron-policy-generator
separate
Generates BYO custom safety policies for NVIDIA Nemotron content-safety guardrails — Nemotron-Content-Safety-Reasoning-4B (text) and multimodal Nemotron-3-Content-Safety. Produces a Markdown policy, JSON taxonomy, and drop-in inference prompts. Maps rough words or an existing policy to V2 categories, adding custom categories or topic-following rules.
When to use
- The user mentions any of: NCS, NCS-VL, NCS-Reasoning, Nemotron Content Safety, NeMo Guardrails, Aegis taxonomy.
- The user asks to "build", "draft", "generate", "expand", or "extend" a safety policy, content policy, moderation policy, guardrail config, BYO-policy, custom safety taxonomy, eval rubric, or labeling rubric.
- The user describes their needs in rough words ("no weapons, allow medical, block hate speech") and expects a structured artifact back.
- The user names a deployment context (consumer chat, enterprise RAG, kids/edu, healthcare, financial, code assistant, sovereign deployment) and asks for the safety rules that fit.
- The user wants to *evaluate* an existing policy's quality, not generate one — that's a review task.
- The user wants to *test* whether NCS follows a policy — that's an eval/benchmark task; defer to a benchmark/eval skill.
- The user is asking for legal advice on what their policy *should* cover — defer; this skill generates artifacts from user-supplied intent, it doesn't decide what's legally required in a jurisdiction.
When not to use
- evaluating existing policy quality
- testing whether NCS follows a policy
- legal advice on policy coverage
Skill page
Source
| Repository | Path |
|---|
| NVIDIA/skills | skills/nemotron-policy-generator/SKILL.md |