ov-layers/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 test dbus notify command uses native Go D-Bus instead and does NOT depend on this layer.
notify-send vs ov test dbus notify| | notify-send | ov test 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-layers:dbus -- D-Bus session bus (required dependency)/ov-layers:swaync -- notification daemon to display the notifications/ov-layers:ov -- alternative: native D-Bus via ov test dbus notifyNot used in any current image definition. Optional notification CLI -- prefer ov test dbus notify which uses native Go D-Bus.
Use when the user asks about:
notify-send inside containers/ov:layer — layer authoring reference (layer.yml schema, task verbs, service declarations)/ov:test — declarative testing (tests: block, ov image test, ov test)development
Claude Code multi-agent support in Overthink — sub-agents, dynamic workflows, and agent teams, and how each drives the existing `ov eval` disposable beds to test and verify. MUST be invoked before authoring or invoking an ov sub-agent / dynamic workflow / agent team, wiring agent-lifecycle hooks, or asking "which primitive should drive the R10 beds?".
tools
Mounts a virtiofs share tagged `workspace` at /workspace inside a VM guest via a systemd .mount unit. Use when a kind:vm entity shares a host directory into the guest and you need it auto-mounted (and re-mounted at every boot).
development
MUST be invoked before any work involving: the `kind: android` schema kind, a `target: android` deploy, the `apk:` layer package format (installing Android apps declaratively), AndroidDeployTarget, an in-pod emulator OR a remote/physical adb-endpoint device, or nested `pod → android` deployment. The first-class Android device + app surface that sits above `ov eval adb`/`appium`.
tools
Use when committing, branching, pushing, merging, tagging, creating PRs, or approving/merging PRs with gh — the feat/-branch, R10-gated, never-force-push landing workflow across the main repo + the plugins submodule + image/<distro> submodules. Covers sync-to-upstream, branch/worktree pruning, the fork+PR path for contributors without write access, and cross-repo @github landing order.