eval/skills/dbus/SKILL.md
D-Bus interaction inside containers via native Go godbus/dbus/v5. MUST be invoked before any work involving: ov eval dbus commands, desktop notifications, D-Bus method calls, service introspection, or session bus interaction.
npx skillsauth add overthinkos/overthink-plugins dbusInstall 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.
Send desktop notifications, call D-Bus methods, list services, and introspect objects inside running containers. Uses native Go (godbus/dbus/v5) -- no dependency on dbus-send CLI. All commands operate on the container's session bus.
Every ov eval dbus <method> (list/call/introspect/notify) is authorable as a dbus: verb inside a eval: block. Method-specific fields (dest:, path:, method:, args:, text:) are siblings of the verb line. See /ov-eval:eval for the full YAML shape. Example: - dbus: list\n stdout:\n contains: "org.freedesktop.Notifications".
| Action | Command | Description |
|--------|---------|-------------|
| Send notification | ov eval dbus notify <image> "title" "body" | Desktop notification via Notifications interface |
| Call method | ov eval dbus call <image> <dest> <path> <method> [args...] | Generic D-Bus method call |
| List services | ov eval dbus list <image> | List all registered session bus services |
| Introspect | ov eval dbus introspect <image> <dest> <path> | Introspect a service's interfaces and methods |
# Simple notification
ov eval dbus notify sway-browser-vnc "Build Complete" "Image built successfully"
# Notification appears via swaync or other notification daemon
# Call any D-Bus method on the session bus
ov eval dbus call sway-browser-vnc org.freedesktop.Notifications /org/freedesktop/Notifications org.freedesktop.Notifications.GetCapabilities
# See all registered services on the container's session bus
ov eval dbus list sway-browser-vnc
# View interfaces, methods, signals, and properties
ov eval dbus introspect sway-browser-vnc org.freedesktop.Notifications /org/freedesktop/Notifications
dbus layer)swaync)ov start <image>)/ov-eval:eval -- parent router; ov eval dbus … is how every invocation is dispatched./ov-eval:cdp -- Chrome DevTools Protocol (sibling verb under ov eval)./ov-eval:wl -- Wayland desktop automation (sibling verb under ov eval)./ov-eval:vnc -- VNC desktop automation (sibling verb under ov eval)./ov-core:cmd -- single command execution in running containers/ov-core:shell -- interactive shell access/ov-infrastructure:dbus-layer -- D-Bus session bus layer configuration/ov-selkies:swaync -- notification daemon layerdevelopment
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.