nemo-try-agent

Route user queries to NeMo Platform agents or fallback models with explicit routing announcements.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents silent failures and ambiguous routing when interacting with NeMo Platform agents by enforcing explicit confirmation of the target agent or model before execution.

Core Features & Use Cases

  • Explicit Routing: Announces whether a query is being sent to a specific deployed agent or falling back to a model chat.
  • Platform Health Monitoring: Performs pre-flight checks to ensure the platform is responsive before attempting to invoke agents.
  • Interactive Fallback: Automatically detects if no agents are deployed and offers to route queries to available models instead.

Quick Start

Ask the agent to process your query by saying try the agent followed by your specific question.

Frequently Asked Questions about nemo-try-agent

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

FAQPage Schema
How do I route queries to a specific deployed agent on the NeMo Platform?

Route queries to NeMo Platform agents by invoking the agent with your specific question, which triggers explicit routing announcements and pre-flight platform health checks before execution.

What happens if no agents are deployed when I try to use a NeMo agent?

When no agents are deployed, the system performs an interactive fallback, automatically detecting the missing deployment and offering to route your query to an available model chat instead.

How does NeMo handle ambiguous routing or silent failures during agent invocation?

NeMo prevents ambiguous routing and silent failures during agent invocation by enforcing explicit confirmation of the target agent or fallback model before executing any commands.

Do I need the NeMo CLI to interact with deployed platform agents?

Yes, interacting with deployed platform agents requires the NeMo CLI and an active platform environment to execute agent-specific commands and manage model interactions successfully.

Can I check NeMo Platform health before attempting to invoke agents?

Yes, the system performs pre-flight platform health verification checks to ensure the NeMo Platform is fully responsive before attempting to invoke agents or route queries.

How do I manage multi-agent selection scenarios in my automation workflow?

Manage multi-agent selection scenarios by routing user queries through the NeMo Platform, which handles agent invocation workflows and provides explicit routing announcements for clarity.