nemotron-add-model

Create a Nemotron model-family knowledge base with paper chunks, recipes, and marketplace registration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps contributors add a new model-family knowledge base to the Nemotron plugin ecosystem without breaking the structure used for discovery, retrieval, and downstream routing.

Core Features & Use Cases

  • Model Onboarding: Creates a new model skill directory with paper chunks, a model card, context files, and marketplace registration.
  • Recipe Documentation: Summarizes public reproduction recipes when they exist, or clearly marks the recipe area as minimal when they do not.
  • Validation-First Workflow: Ensures frontmatter, index references, context handoff files, and marketplace metadata stay internally consistent.
  • Use Case: A contributor wants to add support for a newly released Nemotron family so downstream skills like /nemotron-customize can route to it correctly.

Quick Start

Use the nemotron-add-model skill to create a new Nemotron model-family knowledge base from the report, recipes, and marketplace metadata you provide.

Frequently Asked Questions about nemotron-add-model

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

FAQPage Schema
How do I onboard a new Nemotron model family into the skill ecosystem?

Onboarding a new Nemotron model family requires creating a structured knowledge base with consistent paper chunks, recipe summaries, context maps, and marketplace registration without modifying step manifests.

What does a model knowledge base need for downstream skill routing?

Downstream skill routing requires a model knowledge base with internally consistent frontmatter, index references, context handoff files, and marketplace metadata to function correctly.

How do I document public reproduction recipes for a new model checkpoint?

Documenting public reproduction recipes involves summarizing them within the model knowledge base when available, or clearly marking the recipe area as minimal when they do not exist.

Can I modify step manifests when adding a new model skill directory?

You cannot modify step manifests when adding a new model skill directory; the validation-first workflow ensures frontmatter, index references, and marketplace metadata stay internally consistent without manifest changes.

What files are required for Nemotron model onboarding and marketplace registration?

Nemotron model onboarding requires paper chunks, a model card, context handoff files, and marketplace registration metadata to build the new model skill directory.