core/skills/cmd/SKILL.md
Single command execution in a running container with D-Bus notification. MUST be invoked before any work involving: charly cmd command, running commands in containers, or container exec with notifications.
npx skillsauth add overthinkos/overthink-plugins cmdInstall 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.
Runs a single command inside a running container via <engine> exec and sends a D-Bus desktop notification when the command completes. Useful for one-off commands without opening an interactive shell.
| Action | Command | Description |
|--------|---------|-------------|
| Run command | charly cmd <image> "command" | Execute command in running container |
| With instance | charly cmd <image> "command" -i 2 | Target specific instance |
| With env vars | charly cmd <image> "command" -e KEY=VALUE | Pass environment variables |
# Run a command in a running container
charly cmd fedora "uname -a"
# Run with environment variables
charly cmd jupyter "python script.py" -e CUDA_VISIBLE_DEVICES=0
# Target a specific instance
charly cmd ollama "ollama list" -i 2
| Flag | Description |
|------|-------------|
| -i, --instance INSTANCE | Target a specific container instance (default: 1) |
| -e, --env KEY=VALUE | Pass environment variables to the command |
| --sidecar NAME | Run in the named SIDECAR container (charly-<box>[-<inst>]-<name>) instead of the app container |
charly start <image>)charly shell insteadcharly tmux cmd/charly-build:pull -- Prerequisite: fetch the image into local storage; handles remote refs (@github.com/...) and the ErrImageNotLocal recovery path
/charly-core:shell -- Interactive shell sessions with workspace mounts
/charly-check:dbus -- D-Bus interaction inside containers
/charly-automation:tmux -- Persistent tmux sessions for long-running commands
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).