CLI Reference
This page lists every skillevaluator command with its full flag set and exact defaults. If you want task-oriented guidance instead, start from the tier guides: Tier 1: Validation, Tier 2: Deduplication, and Tier 3: Live Evaluation.
Harbor is the open-source agent evaluation framework behind the Tier 3 task, environment, trial, and trajectory commands referenced below.
Command map
Global conventions
Reports. Every Tier 1 and Tier 2 command accepts the same two report options:
In practice: a default validate run (no -r) shows the compact pipeline view and writes json + html report files; passing -r takes over completely — -r cli really means terminal output only, no files. The standalone commands take the cli default literally: they print the full terminal report and write files only for the formats you request with -r. A validate run writes skillevaluator-output-<timestamp>.json / .html (plus .md with -r markdown); standalone commands write a fixed skillevaluator-<kind> basename (for example skillevaluator-quality.json), so a re-run overwrites the previous report. Filename conventions and report anatomy live in Reports & Results.
Exit codes. Commands communicate through a small exit-code contract — this is what your CI gates on (see Gate Your CI):
Version. skillevaluator --version prints the installed version.
Expert tier groups
Most commands are also reachable under a tier-prefixed group — skillevaluator tier1 validate behaves exactly like skillevaluator validate. The groups exist so you can discover a tier’s commands in one place:
The exceptions run in both directions. health-check and models are top-level only, with no tier-prefixed twin. And two commands are advertised only inside the tier3 group: tier3 evaluate, documented with its full flag set below, and tier3 validate:
tier3 validate
Validate the Tier 3 evals/ directory and the optional Harbor bring-your-own-task contract before you spend money on a live run. The dataset and directory rules it enforces are documented in Eval Datasets.
validate
Validate a skill, rule, workflow, or plugin. Tier 1 static, security, and quality checks gate the exit code — and so do Tier 2 deduplication findings when that pass runs (on by default, degrading gracefully without embedding access); Tier 3 live evaluation attaches as an advisory pass when enabled with --tier3, --autopilot, --full, or the supported --agent-eval compatibility alias.
Pointing validate at a directory of skills (one with no root SKILL.md) runs the whole pipeline serially for each skill inside it and finishes with a per-skill summary — catalog validation in one command. By default the terminal shows a compact pipeline view; --verbose switches to the full per-check detail stream.
--help groups the flags into four panels, mirrored by the subsections below.
Run & Reports
Applies to the whole run: target typing, policy profile, reports, tier selection.
Auto-detection recognizes: a SKILL.md for skills, .mdc files for rules, workflow-rules.mdc for workflows, and — for plugins — a bundle-reference agent_plugin.yaml/.yml manifest or a contained .claude-plugin/plugin.json manifest. Plugins are validated against their public contract; quality, lint, and version checks are skill-only and skipped for plugins.
validate also takes the standard -r/--report and -o/--output-dir options described under Global conventions.
Tier 1 · Static & Security
Static checks; LLM-free by default. Tier 1 gates the exit code and always runs.
Tier 2 · Deduplication
Embedding + LLM dedup; on by default, skips gracefully without a provider key.
Tier 3 · Live Agent Evaluation
The following flags are forwarded to the live-eval engine only when Tier 3 is enabled — with --tier3, --autopilot, --full, or the supported --agent-eval compatibility alias. On their own they have no effect. The Dockerfile-, workspace-, resource-, preflight-, and progress-tuning flags (--custom-dockerfile-mode, --skill-workspace-mode, the --override-* flags, --agent-runtime-preflight, and --progress) are not forwardable — use the standalone tier3 evaluate command for those.
Flags marked “unset” fall back to their matching keys in evals/config.yml where one exists, then to the built-in defaults (Eval Datasets documents the config keys and precedence). The exception is --results-dir, which resolves independently of evals/config.yml (see Reports & Results).
quality-check
Score skill quality across correctness, discoverability, reliability, and efficiency. Runs entirely offline — no API key.
Plus the standard report options. Scoring weights and grade bands are documented in Tier 1: Validation.
rubric-eval
Run LLM-as-judge rubric evaluation for a skill against nine weighted criteria. Requires a configured LLM provider.
Plus the standard report options.
security-scan
Scan for security vulnerabilities using the static scanner stack. Keyless by default; the LLM flags require a configured provider.
Plus the standard report options.
pii-scan
Scan for PII and local identifiers (emails, credentials, home paths, and more).
Plus the standard report options.
lint-scripts
Run advisory lint checks on skill scripts. Takes only the standard report options.
context-optimization-check
Detect redundant content within one skill (intra-skill deduplication). Needs an embeddings-capable provider plus a chat LLM for the verification stage — see Tier 2: Deduplication.
Plus the standard report options.
dedup-scan
Alias of context-optimization-check — same behavior, same flags (--threshold default 0.8, --model, --llm-model, plus the standard report options).
similarity-check
Detect duplicate content across a collection with embedding similarity (inter-skill deduplication). Takes a content path — a single item or a folder of them.
Plus the standard report options. Classification tiers and catalog rules are in Tier 2: Deduplication.
tier3 evaluate
Run Tier 3 live agent evaluation: real agents attempt your eval cases with and without the skill, and the difference becomes Skill Lift. Requires the tier3 extra, a provider key for grading, a credential the selected agents can use — with NVIDIA Build in --env-mode docker or local, the one NVIDIA_API_KEY covers both roles — and a running backend (Docker by default). The full walkthrough is Tier 3: Live Evaluation.
The old top-level spelling skillevaluator evaluate still works for existing scripts, but no longer appears in --help; tier3 evaluate is the advertised name.
Without a --model/--agent-model override, each agent uses the selected provider’s default model: gpt-5.4-mini on OpenAI, and Nemotron on the NVIDIA provider — nvidia/nemotron-3-super-120b-a12b for bridged agents, nvidia/nemotron-3-nano-30b-a3b for direct OpenCode.
Flags marked “unset” fall back to their matching keys in evals/config.yml where one exists, then to the built-in defaults. The exception is --results-dir, which resolves independently of evals/config.yml.
create-eval-dataset
Create synthetic eval datasets for agent skill evaluation, written to evals/evals.json. Uses the configured LLM provider unless you pass --no-llm. Dataset anatomy and the four case buckets are documented in Eval Datasets.
--force overwrites an existing evals/evals.json, including any hand-edited cases. Use --dry-run first if you are unsure.
init-custom-grader
Create a bring-your-own-grader (BYOG) starter under evals/. The grader contract it scaffolds is documented in Custom Graders & Tasks.
init-harbor-task
Create a bring-your-own-task (BYOT) Harbor starter template under evals/harbor/. See Custom Graders & Tasks for how case IDs map to eval entries.
view
Open the latest HTML live-evaluation report for a skill. If the results exist but report.html is missing, view regenerates it before opening.
compare
Compare live-evaluation results across agents from previous runs.
harbor-view
Open retained Harbor job artifacts with Harbor’s trajectory browser. Takes a jobs directory as its argument and has no options. Jobs are only retained when the original run passed --harbor-keep-jobs. skillevaluator tier3 harbor-view is an identical tier-prefixed spelling.
doctor
Check live-evaluation runtime readiness: the CLI install, the configured provider, the requested agents and their credentials, and the selected backend. Run it before your first tier3 evaluate — see Agents & Sandboxes for what each check means.
skillevaluator tier3 doctor takes the same flags, including --agent-model and --verify-models.
health-check
Quick readiness check for the CLI and the selected live-eval backend. Use it as an install smoke test or a fast CI preflight. It differs from doctor by two flags: health-check has no --agent-model and no --verify-models.
models
List a filtered view of the selected provider’s authenticated catalog. Uses the same provider and credential resolution as evaluation (see Providers & Credentials), so it doubles as a quick check that your key works. A model appearing in the catalog is not proof it is compatible with the evaluation harness — use doctor --verify-models for that. Top-level only; there is no tier-prefixed twin.
See also
- Environment Variables — every
SKILL_EVAL_*andSKILLEVALUATOR_*variable - Gate Your CI — exit codes and JSON reports as a merge gate
- Providers & Credentials — which commands need which key