overthinkos/stop
core/skills/stop/SKILL.md
Stop a running service container. MUST be invoked before any work involving: charly stop command, stopping containers, or halting services.
data-ai
Updated Jun 20, 2026
$ install --global
skillsauthnpx skillsauth add overthinkos/overthink-plugins stopInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 20, 2026, 6:06 AM5.3s1 file scanned
SKILL.md
- name:
- stop
- description:
- |
- MUST be invoked before any work involving:
- charly stop command, stopping containers, or halting services.
charly stop -- Stop Service Container
Overview
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 charly bundle del — charly stop <name> is the ergonomic wrapper for charly bundle del <name> on a container deploy. The two are interchangeable for container deploys; charly bundle del host is required for the host-target teardown path (which runs ReverseOps, removes env.d files, and strips the shell managed block). See /charly-core:deploy and /charly-local:local-deploy.
Quick Reference
| Action | Command | Description |
|--------|---------|-------------|
| Stop service | charly stop <image> | Stop the running container |
| With instance | charly stop <image> -i 2 | Stop a specific instance |
| Stop + tear down FUSE | charly stop <image> --unmount | Stop the container AND unmount encrypted volumes (drops charly-enc-<image>-<volume>.scope units) |
Usage
# Stop a running service
charly stop jupyter
# Stop a specific instance
charly stop ollama -i 2
# Stop and tear down encrypted FUSE mounts in one step
charly stop immich --unmount
Flags
| Flag | Description |
|------|-------------|
| -i, --instance INSTANCE | Target a specific container instance |
| --unmount | After the container stop succeeds, also tear down charly-enc-<image>-<volume>.scope units via encUnmount. Best-effort: per-volume unmount failures emit a warning but don't propagate (the container has already stopped; the user can retry with charly config unmount <image>). Default false — plain charly stop leaves gocryptfs scopes running so they survive container restart (the original load-bearing design from /charly-automation:enc). |
Behavior
- Quadlet mode: Runs
systemctl --user stop charly-<image>.service - Direct mode: Runs
<engine> stop <container> - Does not remove the container or its configuration -- use
charly removefor that - Does not disable the service -- the container may restart on next login if enabled
- To stop and disable:
charly start <image> --enable=falsethencharly stop <image> - By design, plain
charly stopdoes NOT tear down encrypted FUSE mounts — thecharly-enc-*.scopeunits are deliberately decoupled from the container service cgroup so they surviveKillMode=mixedon stop and let the next start fast-path through thecharly config mountshort-circuit. Use--unmountfor the full teardown semantics.
Cross-References
-
/charly-build:pull-- Prerequisite: fetch the image into local storage; handles remote refs (@github.com/...) and theErrImageNotLocalrecovery path -
/charly-core:start-- Start services -
/charly-core:remove-- Remove containers, quadlets, and deploy config -
/charly-core:charly-status-- Check service status
Related Skills
overthinkos/plugin
tools
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Jun 22, 2026
overthinkos/cue
tools
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Jun 16, 2026
overthinkos/egress
tools
VerifiedTrustedCommunity
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).
SKILL.mdUpdated Jun 16, 2026
overthinkos/check-k8s
tools
VerifiedTrustedCommunity
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).
SKILL.mdUpdated Jun 14, 2026