plugin-config

Standardize NeMo Platform plugin configuration with Pydantic models and hierarchical loading.

58|16|Updated May 14, 2026
One-click install
npx skills add https://github.com/NVIDIA-NeMo/nemo-platform --skill plugin-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-config
Source: https://github.com/NVIDIA-NeMo/nemo-platform/tree/main/packages/nemo_platform_plugin/src/nemo_platform_plugin/.agents/skills/plugin-config
Command: npx skills add https://github.com/NVIDIA-NeMo/nemo-platform --skill plugin-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a unified, type-safe framework for managing configuration settings across NeMo Platform plugins, eliminating manual parsing errors and inconsistent environment variable handling.

Core Features & Use Cases

  • Type-Safe Configuration: Uses Pydantic-based models to enforce schema validation for plugin settings.
  • Multi-Source Loading: Automatically aggregates settings from environment variables, YAML files, and hardcoded defaults.
  • Use Case: Developers can define a configuration class for a new plugin, and the system will automatically map environment variables like NMP_MY_PLUGIN_DEBUG to the corresponding class fields.

Quick Start

Use the plugin-config skill to generate a new configuration class for your plugin by defining the required plugin_name and plugin_description fields within a NemoConfig subclass.

Frequently Asked Questions about plugin-config

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

FAQPage Schema
How do I manage NeMo plugin configurations using environment variables and YAML?

To manage NeMo plugin configurations, you can use a Pydantic-based framework that aggregates settings from environment variables, YAML files, and class defaults, ensuring type safety and consistent access.

How does Pydantic schema validation work for NeMo plugin settings?

Pydantic schema validation enforces type safety by mapping environment variables like NMP_MY_PLUGIN_DEBUG to specific class fields, eliminating manual parsing errors and inconsistent environment variable handling across plugins.

What is the best way to define type-safe configuration classes for platform plugins?

The best way to define type-safe configuration classes is to subclass NemoConfig and specify required fields like plugin_name and plugin_description, letting the system automatically map hierarchical settings.

Does this configuration management approach support hierarchical loading from multiple sources?

Yes, hierarchical loading automatically aggregates and overrides settings from hardcoded class defaults, YAML files, and environment variables, providing a unified and type-safe framework for platform plugins.

Why do I need standardized configuration models for NeMo Platform plugins?

You need standardized configuration models to eliminate manual parsing errors and inconsistent environment variable handling, ensuring type safety and uniform access patterns for plugin-specific parameters.

Can I use environment variables to override YAML configurations in my plugin?

Yes, you can use environment variables to override YAML configurations, as the system automatically aggregates settings from multiple sources to enforce schema validation and type safety.