ov/skills/stop/SKILL.md
Stop a running service container. MUST be invoked before any work involving: ov stop command, stopping containers, or halting services.
npx skillsauth add overthinkos/overthink-plugins stopInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Stops a running service container. In quadlet mode, stops the systemd user service. In direct mode, stops the container via the container engine.
Relationship to ov deploy del — ov stop <name> is the ergonomic wrapper for ov deploy del <name> on a container deploy. The two are interchangeable for container deploys; ov deploy del host is required for the host-target teardown path (which runs ReverseOps, removes env.d files, and strips the shell managed block). See /ov:deploy and /ov:host-deploy.
| Action | Command | Description |
|--------|---------|-------------|
| Stop service | ov stop <image> | Stop the running container |
| With instance | ov stop <image> -i 2 | Stop a specific instance |
# Stop a running service
ov stop jupyter
# Stop a specific instance
ov stop ollama -i 2
| Flag | Description |
|------|-------------|
| -i, --instance INSTANCE | Target a specific container instance |
systemctl --user stop ov-<image>.service<engine> stop <container>ov remove for thatov start <image> --enable=false then ov stop <image>/ov:pull -- Prerequisite: fetch the image into local storage; handles remote refs (@github.com/...) and the ErrImageNotLocal recovery path
/ov:start -- Start services
/ov:remove -- Remove containers, quadlets, and deploy config
/ov:status -- Check service status
tools
Use when authoring or modifying a charly PLUGIN — a candy with a `plugin:` block that contributes Providers (verbs/kinds/deploy-targets/steps/builders/commands), its own CUE schema, builtin (compiled-in) or external (out-of-tree git repo). Covers the unified Provider model, the per-plugin CUE-schema contract (single source → Go params for dev + schema-over-Describe RPC for runtime), the SDK, and the loader.
tools
The CUE data-validation / configuration CLI (cue), pinned to v0.16.1. Use when working with the cue candy, installing the cue binary into a box or onto a target:local dev host, or running the offline schema-vendoring pipeline that feeds charly's egress validation.
tools
CUE EGRESS validation — validating (and, where it adds value, generating) the config files charly WRITES to a system BEFORE the bytes hit disk. MUST be invoked before working on charly/egress.go, the vendored schemas under candy/plugin-egress/egress-schemas/vendor/, the ValidateEgress / registerVendoredEgressKind path, the offline `task cue:vendor` pipeline, or adding an egress schema for any written artifact (cloud-init, k8s manifests, traefik routes, runtime config, install ledger, systemd/quadlet units, ssh_config, libvirt XML).
tools
Kubernetes cluster-probe declarative check verb — the `kube:` check verb (nodes, pods, ingress, storage class, addon health, apply/delete, and arbitrary resource GETs) served out-of-process by the candy/plugin-kube plugin (vendored client-go; no external kubectl required).