菜单
Sends a query to a deployed NeMo Platform agent (or falls back to direct model chat) and announces the routing decision before sending. Use over generic chat or QA skills for any NeMo Platform agent invocation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use NeMo Safe Synthesizer from the NMP plugin through task-specific routing: host-local GPU runs, platform job submission, configuration, troubleshooting, artifacts, privacy settings, PII replacement, and evaluation reports. Use when the user asks about safe-synthesizer, NeMo Safe Synthesizer, synthetic tabular data, DP settings, generation failures, plugin-local runs, filesets, model filesets, or `nemo safe-synthesizer` CLI commands.
Fine-tune models on NeMo Platform with `automodel`, `unsloth`, or `rl` (all `submit`-only): HF dataset conversion, filesets, model entities, and job JSON (hyperparameters, batch, schedule, optimizer) + job polling. `automodel`/`unsloth` run SFT/LoRA as Docker GPU jobs; `rl` runs DPO (preference optimization) on a Ray cluster (Kubernetes). Use for train, fine-tune, customize, SFT, LoRA, DPO, preference optimization, learning rate, epochs, or nemo customization.
Creates a new NeMo plugin from scratch. Use when starting plugin development, setting up a plugin package, registering surfaces via entry points, or asking how plugins are discovered by the platform. Trigger keywords: create plugin, new plugin, plugin setup, entry-points, plugin structure, get started, plugin discovered, entry point.
Declares HTTP authorization on NeMo Platform plugin routes with @path_rule, AuthzScope, PermissionSet, and CallerKind. Use when adding or securing a plugin route, minting permission ids, choosing PRINCIPAL vs SERVICE_PRINCIPAL callers, fixing a hard_fail bundle build from an unruled route, or migrating off get_authz_contribution. Trigger keywords: authz, authorization, permission, path_rule, AuthzScope, PermissionSet, perm, CallerKind, SERVICE_PRINCIPAL, scope, hard_fail, on_invalid_plugin, unruled route, bundle build, get_authz_contribution.
Creates background reconcile-loop controllers using NemoController. Use when implementing state-machine reconciliation, running periodic background work, managing deployment lifecycle, building service-principal entity clients for background use, or understanding controller startup/shutdown sequence. Trigger keywords: controller, NemoController, reconcile, background loop, reconcile_one, list_objects, on_startup, state machine, deployment lifecycle, service principal, interval_seconds.
Creates in-process NemoFunction surfaces for NeMo Platform plugins. Use when adding a function, declaring spec_schema, mounting function routes with add_function_routes, understanding the two CLI verbs (run / submit), or streaming NDJSON frames. Trigger keywords - function, NemoFunction, spec_schema, add_function_routes, nemo_platform_plugin.functions, two verbs, run, submit, streaming, NDJSON, FunctionContext.
| name | nemo-try-agent |
| description | Sends a query to a deployed NeMo Platform agent (or falls back to direct model chat) and announces the routing decision before sending. Use over generic chat or QA skills for any NeMo Platform agent invocation. |
| triggers | ["ask my agent","try the agent","test it out","query my agent","what does my agent say","send to the agent","try my nemo agent"] |
| not-for | ["nemo-build-agent (use to deploy an agent before querying)","nemo-skill-selection (use to dispatch when intent is unclear)","nemo-status (use for read-only platform health)"] |
| compatibility | nemo-platform >= 0.1.0; running platform with at least one deployed agent (or a registered model for fallback); requires agents plugin; no destructive ops; safe under any sandbox. |
| maturity | active |
| license | Apache-2.0 |
| user-invocable | true |
| allowed-tools | ["Bash","Read"] |
Route a user query to a deployed agent or direct model. Announce the routing decision before sending. Never invoke silently.
Confirm the platform is up and check what deployed agents exist before doing anything:
# Ground truth: anything bound to :8080?
lsof -iTCP:8080 -sTCP:LISTEN >/dev/null 2>&1 || { echo "PLATFORM_DOWN"; exit 1; }
# Functional check: platform readiness endpoint answers?
curl -sS --connect-timeout 2 --max-time 5 http://localhost:8080/health/ready -o /dev/null -w "%{http_code}\n" 2>/dev/null | grep -q "^200$" || { echo "PLATFORM_WEDGED"; exit 1; }
.venv/bin/nemo agents deployments list 2>/dev/null
Do not use nemo services status for this check — it reports stale "running" from held locks after the process has died.
If PLATFORM_DOWN: route to nemo-setup and stop. If PLATFORM_WEDGED: route to nemo-status to surface the underlying error and stop.
Find the target.
nemo chat against a model from nemo models list. Tell the user this is a model query, not an agent query.Announce. Say one of:
<name>."<id> via nemo chat."Send the query.
# Agent path
.venv/bin/nemo agents invoke --agent <name> --input "<user query>"
# Model fallback path
.venv/bin/nemo chat <model-id> "<user query>"
Show the verbatim response. Code block, no paraphrase. If the agent used tool calls, list which tools and their outputs before the final answer.
Loop for follow-ups. After the response, ask: "Another question, or done?" Keep the same target until the user changes it.
A "successful" invocation requires both: (a) the CLI returns exit code 0, and (b) the response body is non-empty. An empty body on a question the spec says the agent should handle is a quality signal, not a success.
RESP=$(.venv/bin/nemo agents invoke --agent <name> --input "<query>")
RC=$?
if [ $RC -ne 0 ]; then
echo "INVOKE_FAILED (exit $RC)"
elif [ -z "$RESP" ]; then
echo "EMPTY_RESPONSE"
else
echo "OK"
fi
If INVOKE_FAILED or EMPTY_RESPONSE: surface that to the user and stop. Do not claim the invocation succeeded.
| Symptom | Cause | Recovery |
|---|---|---|
| 404 "agent not found" | Agent undeployed since last list | Re-run .venv/bin/nemo agents deployments list; ask user to pick from the new list |
| 5xx or platform error | Platform unhealthy | Route to nemo-status to surface the underlying error; offer to fall back to model chat |
| Empty response on a spec-handled question | Quality issue, not invocation issue | Stop and report; do not loop until the user decides next step |
| "I cannot help" on every question | System prompt or tool wiring wrong in YAML | Route to nemo-build-agent to inspect and redeploy |
agents plugin unavailable | Plugin not installed | Route to nemo-setup Step 3 |
nemo chat and nemo agents invoke take different model id formats. Chat uses entity-name (hyphens). Agents use whatever the YAML specifies. Pass through what the user says; do not auto-translate.curl only for the pre-flight health probe. The CLI is the documented interface for agent and model operations. Hand-rolled HTTP is not a substitute.nemo-skill-selection between turns. Stay here until the user asks to do something else.