Menu
Use when submitting, validating, or debugging NPA SkyPilot workflow YAMLs and workflow runner paths.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when ingesting, validating, curating, or querying production sensor data as a versioned dataset-of-record, or wiring the dataset-ingest-curate workflow.
Use when generating adversarial scenarios via RL, ranking mined failures of a policy-under-test, or wiring the adversarial-scenario-hardening workflow.
Use when navigating the Cosmos3 integration in NPA or locating upstream Cosmos3 framework files, defaults, scripts, configs, recipes, and docs.
Use when Cosmos3 setup, fetch, inference, CUDA, uv, Docker, Hugging Face, GitHub, NGC, or checkpoint staging fails in NPA or in an upstream Cosmos framework checkout.
Use when setting up Cosmos3 access through NPA, checking source or Hugging Face reachability, staging the public Cosmos3 framework and checkpoint cache, or deciding which NPA workflow to use before inference.
Use for Claude Code reviews that need robotics, simulation, GPU-routing, sim-to-real, or BDD100K pipeline domain context.
| name | submit-workflow |
| description | Use when submitting, validating, or debugging NPA SkyPilot workflow YAMLs and workflow runner paths. |
Use this skill for workflow launch, YAML validation, runner scripts, and SkyPilot submission behavior.
skills/tools/skypilot-workflows/SKILL.md for SkyPilot version and
cleanup constraints.npa.workflow/v0.0.1 specs under
npa/workflows/workbench/npa-workflows/. Parse / validate-spec locally
before launch.NPA_SKYPILOT_BIN or npa skypilot status --bin-path; do not assume
sky from PATH.npa workbench workflow submit (accepts npa.workflow specs
and legacy SkyPilot YAML) or the shared workflow submission helper.npa workbench workflow --help and tool-specific workflow commands.npa.workflow/v0.0.1 specs under
npa/workflows/workbench/npa-workflows/ for authoring. npa workbench workflow submit accepts those specs (plans → renders → SkyPilot) and still
accepts raw SkyPilot YAML under npa/src/npa/workflows/skypilot/ for
operator/runtime and SkyPilot-only exceptions (parallel, burst, runbook).envs does not support self-referencing interpolation. The
npa.workflow renderer resolves images and config before submit so rendered
YAML has no ${VAR} placeholders.sky jobs launch does not provide a reliable dry-run path in the pinned
version; use npa workbench workflow submit --plan-only for npa.workflow
specs, or mock submission before live launch.npa/.venv/bin/python -m pytest npa/tests/guardrails/test_skills_index.py -q
The smoke test invokes workflow help and parses representative workflow YAML.