ov-selkies/skills/libnotify/SKILL.md
Desktop notification client library providing notify-send CLI. Use when working with notify-send, libnotify, or shell-based notifications.
npx skillsauth add overthinkos/overthink-plugins libnotifyInstall 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.
| Property | Value |
|----------|-------|
| Dependencies | dbus |
libnotify (RPM) -- provides notify-send CLI and libnotify.so shared library# image.yml
my-image:
layers:
- libnotify
Provides notify-send as a convenience CLI for sending desktop notifications from shell scripts and manual use. The ov eval dbus notify command uses native Go D-Bus instead and does NOT depend on this layer.
notify-send vs ov eval dbus notify| | notify-send | ov eval dbus notify |
|---|--------------|-----------------|
| Requires | libnotify layer | ov layer (or gdbus fallback) |
| Implementation | Shell command, libnotify C library | Native Go godbus/dbus/v5 |
| Use case | Shell scripts inside container | Host-side automation, ov cmd/ov tmux cmd notifications |
/ov-foundation:dbus -- D-Bus session bus (required dependency)/ov-selkies:swaync -- notification daemon to display the notifications/ov-foundation:ov -- alternative: native D-Bus via ov eval dbus notifyNot used in any current image definition. Optional notification CLI -- prefer ov eval dbus notify which uses native Go D-Bus.
Use when the user asks about:
notify-send inside containers/ov-build:layer — layer authoring reference (layer.yml schema, task verbs, service declarations)/ov-build:eval — declarative testing (eval: block, ov eval image, ov eval live)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).