nemotron-add-model

What problem does it solve?

It prevents contributors from adding a new Nemotron model family into the plugin ecosystem with incorrect or inconsistent knowledge artifacts (paper chunks, recipe summaries, context packs, and model card layout).

Core Features & Use Cases

• Model-family knowledge-base onboarding: Creates the complete skills/nemotron-{model}/ shell (SKILL, INDEX, model card, paper chunks, context pack, and marketplace entry) in the same structure as existing model skills.
• Report-faithful chunking and sourcing: Produces question-oriented paper chunks based on available HTML tech reports (falling back to PDF only when necessary).
• Repo-convention validation and guardrails: Uses a four-phase workflow (Orient → Generate → Validate → Summarize) that enforces required frontmatter fields, cross-file indexing, and consistent currency semantics.
• Compatibility with downstream skills: Ensures the new model family can be routed by skills like /nemotron-customize via correct context mapping and repository-native intent coverage.

Quick Start

Ask the contributor questions about the new model family slug, preferred tech-report HTML URL, architecture type, available sizes, and which existing steps should later gain [[models]] entries, then generate and validate the full skills/nemotron-{model}/ knowledge-base structure accordingly.