By name: nvflare-orient description: "Route ambiguous NVFLARE requests by inspecting the local project, checking readiness, and recommending the next specific FLARE workflow skill without editing files." min_flare_version: "2.8.0" blast_radius: read_only skill_version: "0.1.0"
NVFLARE Orient
Use When
Use when the user asks where to start with NVFLARE, how a local project maps to FLARE workflows, or which FLARE skill should handle an ambiguous request.
Do Not Use When
Do not use when the user already names a specific workflow such as PyTorch conversion, job submission, production deployment, Kubernetes setup, or log diagnosis. Route to the narrower skill instead.
Workflow
- Clarify the target path or use the current workspace when the user already gives enough context.
- Run
nvflare agent inspect <path> --format jsonfor static project evidence. - Run
nvflare agent doctor --format jsonwhen the user asks about local readiness or when inspection suggests missing FLARE setup. - Classify the request into one next action: conversion, local validation, POC workflow, production workflow, diagnosis, deployment, or no FLARE skill.
- Recommend one lead skill and only mention supporting skills when the next step clearly needs them.
Requirements
- Must keep the work read-only.
- Must report the evidence used for routing.
- Must prefer a specific workflow skill over broad FLARE advice.
- Must say when no FLARE skill should trigger.
- Must not edit files, start POC systems, submit jobs, or read private keys.
Load references/orientation-routing.md when routing is ambiguous or when the
inspect output names multiple possible workflow families.