Agent skill · nvidia
ethos-orchestrate
Entry point for an AI agent's ETHOS.md: a durable snapshot of what the agent is for, what it must not do, and what success looks like. Routes a request to explore and capture intent (ethos-explore), or write or edit the file (ethos-write). Owns the standard every ethos sub-flow follows. Use when the user asks "help me write an ETHOS.md", "does my agent have an ETHOS.md?", "update my agent's ETHOS.md", or when you need to pick between the ethos sub-flows.
What it needs
About 6k tokens when loaded.
What this skill does
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> <!-- SPDX-License-Identifier: Apache-2.0 --> Ethos orchestrate Purpose Help a developer create and maintain their agent's ETHOS.md. Route each request to the narrow sub-flow that owns it, and carry what is already known into that sub-flow so the user is never asked twice. Continue from prior context When a user or another workflow supplies an earlier Ethos conversation, reuse the selected repository, agent, file location, and requested operation. Skip the repeated opening and completed questions. Check that prior findings and answers still apply to this agent; distinguish source evidence from explicit user replies, retaining where each answer came from. Without usable prior context, use the standalone entry below. Resume the earliest unfinished work. Missing or conflicting intent goes to ethos-explore; completed intent goes to draft review or ethos-write as needed. Before writing, recover the exact accepted draft and the user's confirmation. If either is unavailable or the draft changed, review the draft again while retaining completed answers. Review a suitable existing file without rewriting it. Reuse an earlier saved-content review only when the contents are unchanged, the confirmation applies to this agent, and current findings reveal no conflict. On a pause or completion, report the file location, actual validation outcome, unresolved questions, and what the user confirmed or still needs to review. Carry relevant answers and draft context back to the invoking conversation or workflow, which owns any persistence. These skills write only ETHOS.md; they require no external state format. Missing validation or a required sub-flow must be reported as unfinished work, not completion. Choose the entry route For a continuation, use the context above. The following routing and opening apply to standalone requests. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/ethos-orchestrate