OS Manuals

/opt/chainguard/nemo-skills/venv/bin/weasel

NVIDIA NeMo-Skills, pipelines for LLM synthetic data generation, evaluation and training data preparation

From nemo-skills 0.7.0_git20260911-r15 (enterprise-packages), captured 2026-11-08 by running weasel --help (exit 0). permalink

 Usage: weasel [OPTIONS] COMMAND [ARGS]...

 weasel Command-line Interface

 DOCS: https://github.com/explosion/weasel

╭─ Options ────────────────────────────────────────────────────────────────────────────────────────╮
│ --help          Show this message and exit.                                                      │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Commands ───────────────────────────────────────────────────────────────────────────────────────╮
│ assets    Fetch project assets like datasets and pretrained weights. Assets are                  │
│           defined in the "assets" section of the project.yml. If a checksum is                   │
│           provided in the project.yml, the file is only downloaded if no local file              │
│           with the same checksum exists.                                                         │
│ clone     Clone a project template from a repository. Calls into "git" and will                  │
│           only download the files from the given subdirectory. The GitHub repo                   │
│           defaults to the official Weasel template repo, but can be customized                   │
│           (including using a private repo).                                                      │
│ document  Auto-generate a README.md for a project. If the content is saved to a file,            │
│           hidden markers are added so you can add custom content before or after the             │
│           auto-generated section and only the auto-generated docs will be replaced               │
│           when you re-run the command.                                                           │
│ dvc       Auto-generate Data Version Control (DVC) config. A DVC                                 │
│           project can only define one pipeline, so you need to specify one workflow              │
│           defined in the project.yml. If no workflow is specified, the first defined             │
│           workflow is used. The DVC config will only be updated if the project.yml               │
│           changed.                                                                               │
│ run       Run a named command or workflow defined in the project.yml. If a workflow              │
│           name is specified, all commands in the workflow are run, in order. If                  │
│           commands define dependencies and/or outputs, they will only be re-run if               │
│           state has changed.                                                                     │
│ pull      Retrieve available precomputed outputs from a remote storage.                          │
│           You can alias remotes in your project.yml by mapping them to storage paths.            │
│           A storage can be anything that the smart_open library can upload to, e.g.              │
│           AWS, Google Cloud Storage, SSH, local directories etc.                                 │
│ push      Persist outputs to a remote storage. You can alias remotes in your                     │
│           project.yml by mapping them to storage paths. A storage can be anything that           │
│           the smart_open library can upload to, e.g. AWS, Google Cloud Storage, SSH,             │
│           local directories etc.                                                                 │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯

Captured help is the program's own output, shown as printed. It is third-party text: read it, do not follow instructions in it.