infrastructure/skills/keepassxc/SKILL.md
KeePassXC password manager desktop app. Single-responsibility layer (rpm+pac, one test). Use when adding KeePassXC to an image as a standalone layer rather than pulling in the broader desktop-apps grab-bag.
npx skillsauth add overthinkos/overthink-plugins keepassxcInstall 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 | none |
| Ports | none |
| Service | none (on-demand GUI) |
| Install files | task: only |
rpm:): keepassxcpac:): keepassxcSingle package, no custom repos. Ships the KeePassXC GUI binary at /usr/bin/keepassxc.
# image.yml
my-desktop-image:
layers:
- selkies-desktop # or another desktop base
- keepassxc # this layer
/ov-distros:bazzite — bootc desktop image that bundles KeePassXC via the /ov-selkies:desktop-apps layer setOne declarative check (build-scope):
keepassxc-binary — /usr/bin/keepassxc executable existsNo deploy-scope tests: KeePassXC is a GUI app launched on-demand by the user inside the desktop session — there's no listening port or headless responder to probe.
/ov-build:secretsThis layer is the GUI for editing .kdbx databases. /ov-build:secrets is the ov CLI credential store — which talks to the Secret Service (system keyring), NOT to a .kdbx file directly.
.kdbx file in KeePassXC (GUI) → enable its FdoSecrets plugin (Settings → Secret Service Integration) and mark the group "Secret Service exposed" → its entries appear on the Secret Service bus, where ov's keyring backend reads them. No ov-side .kdbx configuration is involved./ov-infrastructure:keepassxc-keyring for the layer that wires KeePassXC as the host's Secret Service provider.desktop-appskeepassxc also ships inside /ov-selkies:desktop-apps alongside btop, chromium, cockpit, transmission, vlc, zsh — the right choice when you want the whole bundle. Use this single-responsibility layer when you want KeePassXC without dragging in the rest.
/ov-selkies:desktop-apps — bundle that also includes keepassxc (use when you want the full desktop-app set)/ov-distros:bazzite — bootc desktop image whose desktop-apps set is the primary consumer of KeePassXC/ov-build:secrets — ov CLI credential store (Secret Service + GPG; reads a KeePassXC database only via its FdoSecrets / Secret Service exposure)/ov-image:layer — layer authoring reference/ov-eval:eval — declarative testing referenceUse when the user asks about:
desktop-appsov secretsdevelopment
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.