example-debug

Verify plugin skill directory installations and companion resource accessibility in NeMo.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the need to verify that plugin-based skill directories and their associated companion files are correctly installed and accessible within the NeMo platform environment.

Core Features & Use Cases

  • Installation Verification: Confirms that the platform successfully copies skill directories and their sub-resources.
  • Resource Accessibility: Ensures that companion files like notes or documentation are correctly linked and readable by the agent.
  • Use Case: Developers can use this to test the deployment pipeline of custom plugins to ensure all assets are correctly placed before deploying production-grade skills.

Quick Start

Use the example-debug skill to verify that all companion files are correctly installed and accessible in the current environment.

Frequently Asked Questions about example-debug

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

FAQPage Schema
How do I verify plugin skill installation in NeMo?

Verify plugin skill installation in NeMo by validating directory structures and confirming companion resources are correctly deployed and accessible. It checks asset synchronization to ensure all files are readable by the agent.

What is plugin skill directory validation?

Plugin skill directory validation is a diagnostic process that confirms platform skill directories and companion files like notes or documentation are correctly installed and linked within the NeMo environment.

Why are companion files not accessible after plugin deployment?

Companion files may not be accessible after plugin deployment if directory structures are incorrectly deployed or asset synchronization fails. Validating plugin installation integrity confirms resource availability and readable file links.

Can I test custom plugin deployment pipelines before production?

You can test custom plugin deployment pipelines before production by running a lightweight diagnostic tool to verify that all skill directories and sub-resources are correctly placed and accessible in the environment.

Does the NeMo platform automatically copy skill directories and sub-resources?

The NeMo platform copies skill directories and sub-resources during deployment. Verification confirms the platform successfully transferred these directories and that associated companion files are readable by the agent.

What is the best way to debug missing resources in a plugin skill?

The best way to debug missing resources in a plugin skill is to validate installation integrity and check directory structures to ensure companion files are correctly linked and readable by the agent.