overthinkos/dbus
ov/skills/dbus/SKILL.md
D-Bus interaction inside containers via native Go godbus/dbus/v5. MUST be invoked before any work involving: ov test dbus commands, desktop notifications, D-Bus method calls, service introspection, or session bus interaction.
development
Updated Apr 27, 2026
$ install --global
skillsauthnpx skillsauth add overthinkos/overthink-plugins dbusInstall 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: Apr 27, 2026, 9:43 AM189.3s1 file scanned
SKILL.md
- name:
- dbus
- description:
- |
- MUST be invoked before any work involving:
- ov test dbus commands, desktop notifications, D-Bus method calls, service introspection, or session bus interaction.
ov test dbus -- D-Bus Interaction Inside Containers
Overview
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.
Also as a declarative verb
Every ov test dbus <method> (list/call/introspect/notify) is authorable as a dbus: verb inside a tests: block. Method-specific fields (dest:, path:, method:, args:, text:) are siblings of the verb line. See /ov:test for the full YAML shape. Example: - dbus: list\n stdout:\n contains: "org.freedesktop.Notifications".
Quick Reference
| Action | Command | Description |
|--------|---------|-------------|
| Send notification | ov test dbus notify <image> "title" "body" | Desktop notification via Notifications interface |
| Call method | ov test dbus call <image> <dest> <path> <method> [args...] | Generic D-Bus method call |
| List services | ov test dbus list <image> | List all registered session bus services |
| Introspect | ov test dbus introspect <image> <dest> <path> | Introspect a service's interfaces and methods |
Usage
Desktop Notifications
# Simple notification
ov test dbus notify sway-browser-vnc "Build Complete" "Image built successfully"
# Notification appears via swaync or other notification daemon
Generic Method Calls
# Call any D-Bus method on the session bus
ov test dbus call sway-browser-vnc org.freedesktop.Notifications /org/freedesktop/Notifications org.freedesktop.Notifications.GetCapabilities
List Services
# See all registered services on the container's session bus
ov test dbus list sway-browser-vnc
Introspect a Service
# View interfaces, methods, signals, and properties
ov test dbus introspect sway-browser-vnc org.freedesktop.Notifications /org/freedesktop/Notifications
Prerequisites
- Container must have a D-Bus session bus running (provided by the
dbuslayer) - For notifications: a notification daemon must be running (e.g.,
swaync) - Container must be running (
ov start <image>)
Cross-References
/ov:test-- parent router;ov test dbus …is how every invocation is dispatched./ov:cdp-- Chrome DevTools Protocol (sibling verb underov test)./ov:wl-- Wayland desktop automation (sibling verb underov test)./ov:vnc-- VNC desktop automation (sibling verb underov test)./ov:cmd-- single command execution in running containers/ov:shell-- interactive shell access/ov-layers:dbus-- D-Bus session bus layer configuration/ov-layers:swaync-- notification daemon layer
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