install-and-cli
Covers Anomalib installation choices, the install subcommand, CLI help behavior, config loading, and command selection for fit, validate, test, train, predict, export, and benchmark.
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-08
- Stars
- ★ 11
- Forks
- 3
01 前言 Front Matter
- name
- install-and-cli
- license
- Apache 2.0
- metadata
- { "disco-role": "operating" }
- description
- Covers Anomalib installation choices, the install subcommand, CLI help behavior, config loading, and command selection for fit, validate, test, train, predict, export, and benchmark.
- disable-model-invocation
- true
02 资源文件 3
- 参考文档references/cli-reference.md3.8 KB
- 参考文档references/installation.md3.7 KB
- 参考文档references/troubleshooting.md3.4 KB
03 SKILL.md 正文
Install and CLI
Use this sub-skill when the user wants to install Anomalib, understand the anomalib install subcommand, inspect CLI help, load configs, or choose between fit, validate, test, train, predict, export, and benchmark.
Read first
- For install matrices, backend selection, editable installs, and when to use direct package install versus
anomalib install, read references/installation.md. - For the command map, config-loading rules, help verbosity, and export flag selection, read references/cli-reference.md.
- For missing-backend, config-path, help-verbosity, or export-flag failures, read references/troubleshooting.md.
- For a read-only CLI smoke check, run scripts/check_cli_help.sh.
- For copyable install, training, prediction, export, and benchmark recipes, run scripts/cli_recipes.sh.
Safe operating boundary
This sub-skill stays at the command, installation, and routing layer.
It covers:
- package installation choices for CPU and OpenVINO support;
anomalib installoptions and when they are appropriate;- top-level help output, verbose help formatting, and config-file loading;
- command selection for
fit,validate,test,train,predict,export, andbenchmark.
It does not cover:
- model math, dataset schemas, export internals, or training loops;
- benchmark pipeline mechanics beyond choosing the
benchmarkcommand; - Studio or UI application code.
Quick routing
| User need | Route here? | Read or run |
|---|---|---|
| Smallest CPU plus OpenVINO install | Yes | Read references/installation.md, then print commands with scripts/cli_recipes.sh |
Decide between anomalib install and pip/uv |
Yes | Read references/installation.md |
Explain why anomalib -h only shows install |
Yes | Read references/troubleshooting.md |
| Check top-level help, install help, and verbose help behavior | Yes | Run scripts/check_cli_help.sh |
Choose fit vs train vs validate vs test |
Yes | Read references/cli-reference.md |
Choose predict or recover from old --data_path examples |
Yes | Read references/cli-reference.md and references/troubleshooting.md |
| Diagnose export flags, especially OpenVINO options | Yes | Read references/cli-reference.md and references/troubleshooting.md |
| Understand benchmark routing or benchmark config semantics | Partly | Route the command choice here, then hand off to the sibling pipelines-and-benchmarks sub-skill for workflow details |
Operating notes
- Use direct package install when the user is bootstrapping a fresh environment or needs a specific backend wheel.
- Use
anomalib installonly after Anomalib is already installed and the user wants to add optional bundles such asopenvino,loggers, ornotebooks. - Treat
cpuas a package extra, not as ananomalib install --optionvalue. - Prefer the current
--datasyntax for prediction examples; older--data_pathshell snippets are legacy and should be translated before reuse. - If a config file names the right subcommand but the wrong model or data class path, diagnose it as a command/config mismatch rather than a parser failure.
- If the benchmark command is missing, check whether the pipeline module is importable before assuming the CLI is broken.
Recommended workflow
- Confirm whether the user needs a fresh install, an editable source install, or an add-on bundle inside an existing environment.
- Read the installation reference and pick the smallest command that satisfies the backend.
- Run the CLI smoke helper after installation or dependency changes.
- Use the CLI reference to choose the right subcommand and flags.
- Escalate to troubleshooting when help output, config loading, or export flags do not match the expected command shape.
04 同仓库更多 Skills
obsidian-clipper-template-creator
Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.
obsidian-clipper-template-creator
Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.
python-api
Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP/mAP semantics, and source-style import diagnostics.
file-evaluation
Folder-based PASCAL VOC AP/mAP evaluation from ground-truth and detection text files.
object-detection-metrics
Guides legacy Object-Detection-Metrics PASCAL VOC AP/mAP evaluation from detection text folders and direct Python API classes.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.