Generated banner for Ethos Orchestrate
Generated logo for Ethos Orchestrate

Ethos Orchestrate

NVIDIAOfficialPublished by NVIDIA

  • Skill
  • Meta (authoring, orchestration, planning, memory)
  • Agent tooling
  • Apache-2.0
  • Medium risk

From the author

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.
— the description by NVIDIA

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

ethos-orchestrate serves as the primary entry point for managing an agent's ETHOS.md file, which acts as a durable record of the agent's purpose, principles, and constraints. It routes user requests to specialized sub-flows for exploring intent or writing and editing the file, ensuring a consistent standard for documentation. By maintaining context across interactions, it prevents redundant questioning and guides the user through a structured process of discovery, drafting, and validation.

What it does

  • Routes requests to appropriate sub-flows for exploring or writing ETHOS.md files.
  • Maintains conversation context to avoid repeating questions or steps.
  • Provides a standardized checklist for creating new documentation.
  • Locates existing ETHOS.md files within a repository.
  • Ensures that intent is confirmed by the user rather than inferred by the agent.
  • Reports on validation status and identifies unresolved questions.

When to use it

  • When you need to create an ETHOS.md file for an agent from scratch.
  • When you want to update or modify specific sections of an existing ETHOS.md.
  • When you need to verify if an agent has an ETHOS.md file and check its validity.
  • When you are unsure which specific ethos-related sub-flow to invoke.

Advantages

  • Ensures documentation accurately reflects user-confirmed intent.
  • Reduces user effort by carrying forward previously established information.
  • Provides a clear, step-by-step path for documentation tasks.
  • Maintains consistency in how agent intent is captured and recorded.

Usage examples

“Help me write an ETHOS.md for my agent.”
The skill initiates the exploration process, presenting the path-ahead checklist and beginning to scan the agent's code to draft intent.
“Update my agent's ETHOS.md to include a new constraint.”
The skill routes the request to the editing sub-flow to modify the specific section in place, followed by validation and review.
“Does my agent have an ETHOS.md?”
The skill searches the repository for an existing file, reports its location, and confirms whether it passes validation.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/nvidia/ethos-orchestrate/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip ethos-orchestrate.zip -d .agents/skills

Documentation by NVIDIA

<!-- 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.

Locate an existing file first: the user's path, otherwise ETHOS.md at the repository root or at the root of the selected agent's package.

find . -maxdepth 4 -iname ETHOS.md -not -path '*/.git/*' -not -path '*/node_modules/*' 2>/dev/null | grep . || echo "no ETHOS.md yet"
Starting situation and requestRouteFirst action and deliverable
No ETHOS.md and the user wants oneethos-exploreShow the path ahead below, then scan and interview. Explore hands off to ethos-write.
An ETHOS.md exists and the user names specific changesethos-writeEdit the named sections in place, validate, and review. No new interview.
An ETHOS.md exists and intent may have drifted, or the user wants it revisitedethos-exploreRead the file as prior answers; interview only for what changed or is missing.
The user wants to know what ETHOS.md is, or whether one existsThis skillExplain it, or report what was found and whether it validates. Offer the next route; do not start writing.

When several apply, take the earliest row that matches. A request phrased as "write the ETHOS.md" with no prior interview in this conversation still goes through ethos-explore: writing needs intent the code cannot supply.

Show the path ahead

For a fresh request to create an ETHOS.md, open with this checklist using literal - [ ] checkboxes, marking the first step We're here:

  • [ ] Explore the agent — read its code and docs and draft what they establish.

  • [ ] Confirm intent — answer a few questions the code cannot: purpose, principles, and vision.

  • [ ] Review the draft — see the whole ETHOS.md and correct it.

  • [ ] Save and validate — write the file, check it, and confirm the final contents.

End with "Ready to start?" and wait. On return visits, resume the earliest unfinished step instead of repeating the opening.

The standard

ETHOS.md records intent the user confirmed, not intent you inferred.

  • Code, prompts, configs, and docs establish what the agent does today. They draft Tools, Harness, Evaluation Setup, and similar sections.

  • Only the user establishes purpose, principles, vision, trade-offs, and constraints. An inferred answer is a draft to confirm, never a filled section.

  • An honest _(none)_, recorded in Open Questions, beats a plausible guess.

  • The bundled validator establishes structure: front matter, schema version, and the fourteen required sections. A file that validates can still be wrong; the user's review establishes that it is right.

Vocabulary

TermMeaning
ETHOS.mdThe agent's intent snapshot: front matter plus fourteen required ## sections, schema version 1
SectionOne required ## heading from the template. Extra headings are allowed and preserved
InferredDrafted from source; shown to the user as an option, never final
ConfirmedAnswered or accepted by the user in this conversation, or carried with explicit user-reply provenance in matching prior context

Sub-flows

Load the selected sub-flow skill when its step begins and follow it. This file carries the standard and the routing; the sub-flow carries the steps.

Sub-flowUse it to
ethos-exploreScan the agent's code and docs, then ask one intent question at a time; hand the agreed answers to ethos-write
ethos-writeRender the template, save ETHOS.md, run the validator, show a gut-check, and get the user's confirmation; edit an existing file

Boundaries

  • Write only the ETHOS.md. Never edit the agent's code, prompts, configs, or evals. The file goes at the user's path or the repository root, and nothing is committed automatically.

  • Preserve what exists. Keep custom sections, extra front-matter keys, author, and created_timestamp on edits.

  • Capture intent without authorizing application changes. Do not ask optimization or change-permission questions in the interview, draft review, or completion checkpoint. Creating an ETHOS.md implies no follow-up to optimize or change the agent. If the user later requests such work, its workflow owns the permission decisions.

  • Keep runtime safety requirements. Record behavioral constraints and approval requirements for actions the agent takes during operation, such as issuing refunds. These describe intended behavior, not permission to edit the application. Also preserve already-confirmed organizational safety and review policies and their known owners without reopening permission questions.

  • No run settings. Spend caps, experiment counts, and per-run limits belong to the tool that runs them, not to ETHOS.md.

Communicating with the user

Do not assume the user knows the term. Before the first question, explain in a sentence or two that ETHOS.md records what the agent should do, what it should avoid, and what a good result looks like, and that people and agents working on the agent read it first. Make the explanation concrete for this agent. Reuse that explanation when it has already been given.

Ask one question per message, prefer multiple choice grounded in what the scan found, and always allow "I don't know". When reporting an existing file, lead with whether it validates and what it says the agent is for, then the gaps.

Prerequisites

A local checkout of the agent, or a description of a planned one. Validation needs Python 3.10+.

Limitations

ETHOS.md is a snapshot of intent; it does not prove the agent behaves that way. Measuring that belongs to evaluation tools.

Troubleshooting

  • Several candidate files or agents: ask which agent the ETHOS.md describes.

  • Validator unavailable: check the structure by reading the file against the template, and say the check was not run.

  • User cannot state a concrete Role: stop, explain that the file is not useful without one, and offer to resume later.

Examples

Request: "Help me write an ETHOS.md for this support bot."
Route: ethos-explore, after the path-ahead checklist.
Deliverable: a reviewed, validated ETHOS.md at the repository root.

Request: "Add a no-PII rule to Constraints in our ETHOS.md."
Route: ethos-write, editing Constraints in place.
Deliverable: the updated file, validated, with the change shown for review.

Request: "We still have the ETHOS.md we wrote last month."
Route: this skill, checking the existing file.
Deliverable: the existing ETHOS.md with unchanged name and contents, validated.

Files

LICENSE

Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Written for: Claude Code

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Declares allowed tools, Claude Code frontmatter

The author says: Routing reads the local checkout only. Sub-flows write one ETHOS.md; validation needs Python 3.10+ and ethos-write's standard-library script. Works offline.

Security

What our scanner noticed· Medium risk

  • Large base64-encoded blobs

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
NVIDIA
Publisher
NVIDIA (Official)
Source
NVIDIA/skills · skills/ethos-orchestrate · commit fce3cca
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE-APACHE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by NVIDIA or NVIDIA.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download ethos-orchestrate.zip