nemotron-policy-generator

Generate structured Nemotron content-safety policies with canonical V2 mappings and custom taxonomy extensions.

Updated Jul 30, 2026
One-click install
npx skills add https://github.com/Lhhiep-maxcode/Nemotron --skill nemotron-policy-generator-lhhiep-maxcode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemotron-policy-generator
Source: https://github.com/Lhhiep-maxcode/Nemotron/tree/main/skills/nemotron-policy-generator
Command: npx skills add https://github.com/Lhhiep-maxcode/Nemotron --skill nemotron-policy-generator-lhhiep-maxcode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill turns rough content-safety requirements into a structured Nemotron policy package, so teams can move from informal rules to deployable guardrails without hand-authoring every artifact.

Core Features & Use Cases

  • Policy generation: Produces a Markdown source-of-truth policy, JSON taxonomy, and Nemotron-ready system prompt.
  • Model-aware targeting: Supports both Nemotron-Content-Safety-Reasoning-4B and Nemotron-3-Content-Safety, including emit-mode choices and multimodal notes when needed.
  • Safety customization: Maps rough requirements to canonical V2 categories, extends them with custom categories, and documents allow-lists, calibration notes, and refusal guidance.
  • Use Case: A safety engineer can ask for a BYO policy for enterprise chat, add product-specific restrictions, and export a consistent artifact set for runtime enforcement and review.

Quick Start

Ask for a Nemotron content-safety policy from your rough requirements, and include any target model, deployment context, or custom rules you already know.

Frequently Asked Questions about nemotron-policy-generator

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

FAQPage Schema
How do I generate Nemotron safety policies from rough requirements?

Nemotron safety policies can be generated by submitting informal content-safety rules to the tool. It produces a structured package containing Markdown source-of-truth, JSON taxonomy, and inference-ready system prompts with canonical V2 mappings.

What is a content safety taxonomy and how does it work with Nemotron guardrails?

A content safety taxonomy categorizes restricted content. For Nemotron guardrails, the generator maps rough requirements to canonical V2 categories, extends them with custom rules, and outputs JSON taxonomy for runtime enforcement and training-data labeling.

Can I create custom safety categories for Nemotron-Content-Safety-Reasoning-4B?

Yes, you can create custom safety categories for Nemotron-Content-Safety-Reasoning-4B. The generator extends canonical V2 categories with your custom rules and documents allow-lists, calibration notes, and refusal guidance for the target model.

Does Nemotron policy generation support multimodal moderation and topic-following constraints?

Yes, Nemotron policy generation supports multimodal moderation and topic-following constraints. It produces deployment-specific guidance, model-specific emit modes, and multimodal notes for both Nemotron-3-Content-Safety and Reasoning-4B models.

How do I export an inference-ready system prompt for runtime guardrails?

To export an inference-ready system prompt for runtime guardrails, input your safety requirements and target model. The generator produces system prompt artifacts with model-specific emit modes and severity metadata for immediate deployment.

What's the best way to structure allow-lists and refusal guidance for Nemotron models?

The best way to structure allow-lists and refusal guidance is by mapping requirements to canonical V2 categories. The generator documents these alongside custom taxonomy extensions and calibration notes for consistent runtime enforcement across Nemotron safety models.