ov-selkies/skills/niri-desktop/SKILL.md
Base Niri desktop composition with audio, portals, Chrome, terminal, and file manager. Base desktop composition layer — no display server included.
npx skillsauth add overthinkos/overthink-plugins niri-desktopInstall 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 |
|----------|-------|
| Layers (composition) | pipewire, xdg-portal-niri, niri, chrome-niri, wl-overlay, niri-apps |
| Install files | none (pure composition) |
niri-desktop
├─ pipewire (audio/media)
├─ xdg-portal-niri (desktop portals, GTK+GNOME backends)
├─ niri (Smithay compositor, built from source)
├─ chrome-niri (Chrome browser + DevTools)
├─ wl-overlay (fullscreen overlays via gtk4-layer-shell)
└─ niri-apps (xfce4-terminal, thunar)
| Component | sway-desktop | niri-desktop | |-----------|-------------|-------------| | Compositor | Sway (wlroots, packaged) | Niri (Smithay, built from source) | | Portals | xdg-desktop-portal-wlr | xdg-desktop-portal-gnome | | Status bar | waybar + sway-autotile | None (niri has built-in workspace indicators) | | wl-tools | grim, wtype, wlrctl | Not included (wlrctl is wlroots-specific) | | Config format | i3-style | KDL |
# image.yml
my-desktop:
base: nvidia
layers:
- niri-desktop
/ov-selkies:sway-desktop -- Sway variant/ov-selkies:niri -- compositor (included)/ov-selkies:pipewire -- audio (included)/ov-selkies:chrome-niri -- Chrome browser (included)/ov-selkies:wl-overlay-layer -- Fullscreen overlays for recordings (included)Not used in any current image definition. Available as a metalayer composition but no image references it yet.
Use when working with Niri desktop composition or comparing Niri vs Sway desktop stacks.
/ov-build:layer — layer authoring reference (layer.yml schema, task verbs, service declarations)/ov-build:eval — declarative testing (tests: block, ov eval image, 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.