Skip to content

Add Nemotron Custom Policy Generator skill#237

Open
svenchilton wants to merge 1 commit into
mainfrom
schilton-publish-nemotron-custom-policy-generator-skill
Open

Add Nemotron Custom Policy Generator skill#237
svenchilton wants to merge 1 commit into
mainfrom
schilton-publish-nemotron-custom-policy-generator-skill

Conversation

@svenchilton
Copy link
Copy Markdown

Generates deployable content safety policies for NVIDIA Nemotron content safety models from natural-language safety requirements. Supports dual-target: Nemotron-Content-Safety-Reasoning-4B (text, English) and Nemotron-3-Content-Safety (multimodal, 12 languages).

Skill authored by Shyamala Prayaga; repo restructure by Sven Chilton.

@svenchilton
Copy link
Copy Markdown
Author

CI failure is due to 2 pre-existing broken links in train-models/reference/optimize/prune.md and distill.md — not related to this PR. The links (docs.nvidia.com/nemo/megatron-bridge/latest/training/pruning.html and distillation.html) return 404 on main as well.

@rkalaniNV, @chrisalexiuk-nvidia, or whoever else is appropriate, would you be kind enough to approve this PR anyway, or tell me how to fix the broken links?

Copy link
Copy Markdown
Collaborator

@rkalaniNV rkalaniNV left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for contributing this skill.

  • Please remove Computex/future-launch references from SKILL.md and prompt templates
  • Please make the skill name/folder/path consistent everywhere
  • Please remove internal publishing/audit/process notes from user-facing files.
  • Please align taxonomy mode names between SKILL.md and policy_json_schema.json
    Once done, I can trigger the nvskills-ci bot to give you more insights as well as populate BENCHMARK.md

Run it twice, once for each agent harness the catalog supports (Claude Code and Codex), per the publishing guide:

```bash
nv-aces run --skill skills/nemotron-policy-generator \
Copy link
Copy Markdown
Collaborator

@rkalaniNV rkalaniNV May 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The folder name is nemotron-custom-policy-generator. Can you please check if this is intentional here. This can affect discoverability of the skill.

@@ -0,0 +1,126 @@
# Publishing Audit — nemotron-policy-generator
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need this file?

ownership: # team-owned
team: "Nemotron Safety PM"
primary_contact: "Shyamala Prayaga <sprayaga@nvidia.com>"
slack_channel: "#nv-skills-onboarding"
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we remove the internal slack channel for public repo?

@@ -0,0 +1,138 @@
## Description: <br>
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need multiple skill card files?

---
name: "nemotron-policy-generator"
title: "Nemotron Custom Policy Generator"
description: "Generates BYO custom safety policies for NVIDIA Nemotron content-safety guardrails. Targets two Gemma-3-4B fine-tunes: nvidia/Nemotron-Content-Safety-Reasoning-4B (text, English, /think and /no_think, BYO today) and nvidia/Nemotron-3-Content-Safety (multimodal text+image, 12 languages, BYO + reasoning at Computex 2026). Both share the Nemotron Content Safety V2 taxonomy. Accepts loose keywords, keywords + deployment context, an existing policy to extend, or free-form prose. Produces a Markdown policy, JSON taxonomy, drop-in inference prompts for the chosen model+mode, and optional .docx. Maps rough words to V2 canonical categories; adds custom categories or topic-following rules where needed. Use whenever the user mentions building, drafting, generating, or extending a safety policy, content policy, moderation policy, guardrail config, BYO-policy, custom safety taxonomy, eval rubric, labeling rubric, or topic-following rules — even when they just say 'rough words for a Nemotron policy'."
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Computex references in skill file.

"type": "array",
"items": { "enum": ["runtime_guardrails", "training_data_labeling", "customer_byo_policy", "eval_rubric"] }
},
"taxonomy_mode": { "enum": ["clean_aegis", "aegis_plus_custom", "mostly_custom"] },
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Diff from skill.md where clean_v2 is mentioned.

Generates deployable content safety policies for NVIDIA Nemotron
content safety models from natural-language safety requirements.
Supports dual-target: Nemotron-Content-Safety-Reasoning-4B (text,
English) and Nemotron-3-Content-Safety (multimodal, 12 languages).

Skill authored by Shyamala Prayaga; repo restructure by Sven Chilton.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Sven Chilton <schilton@nvidia.com>
@svenchilton svenchilton force-pushed the schilton-publish-nemotron-custom-policy-generator-skill branch from 0e9e33b to afc49a1 Compare June 1, 2026 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants