nemotron-add-pattern

Create reusable machine learning decision patterns for the Nemotron step catalog.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps contributors encode recurring machine learning decisions as reusable patterns so future planning stays consistent, discoverable, and easy to apply.

Core Features & Use Cases

  • Pattern Creation: Adds a new pattern file under the Nemotron step catalog with the required frontmatter and body structure.
  • Catalog Maintenance: Regenerates the patterns catalog so the new guidance is indexed correctly.
  • Validation Workflow: Runs the relevant tests to verify the pattern file, scope, and catalog output are correct.
  • Use Case: A contributor notices the same small-data LoRA decision coming up repeatedly and turns it into a pattern that other skills can reference during planning.

Quick Start

Ask the assistant to create a new Nemotron pattern for your recurring decision and specify the pattern topic, triggers, affected steps, and confidence level.

Frequently Asked Questions about nemotron-add-pattern

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

FAQPage Schema
How do I add a reusable machine learning pattern to a step catalog?

To add a reusable machine learning pattern, you create a pattern file with required frontmatter and body structure under the Nemotron step catalog, then regenerate the catalog for proper indexing. This keeps recurring training or evaluation decisions discoverable.

What is a reusable ML decision pattern and when should I create one?

A reusable ML decision pattern encodes recurring training, evaluation, or optimization decisions into a structured format for future reference. You should create one when you notice the same decision, like a small-data LoRA choice, coming up repeatedly during planning.

How do I validate a new ML pattern file and catalog entry?

You validate a new ML pattern by running the relevant tests to verify the pattern file, scope, and catalog output are correct. This validation workflow ensures the pattern metadata remains consistent with repository conventions and discoverable.

Does adding a pattern to the step catalog require specific frontmatter?

Yes, adding a pattern requires valid frontmatter to keep pattern metadata correct and discoverable. You must specify the pattern topic, triggers, affected steps, and confidence level so the catalog regeneration indexes the new guidance properly.

Can I use this pattern workflow for cross-cutting evaluation decisions?

Yes, the pattern workflow applies to contributor workflows that add cross-cutting guidance for recurring training, evaluation, or optimization decisions. It maintains consistency with repository conventions while making the guidance easy to apply.

What are the limitations of encoding ML decisions as catalog patterns?

Encoding ML decisions as catalog patterns requires strict adherence to repository conventions, including valid frontmatter and test validation. Patterns are limited to cross-cutting guidance and require catalog regeneration to remain discoverable and correct.