infrastructure/skills/keepassxc/SKILL.md
KeePassXC password manager desktop app. Single-responsibility candy (rpm+pac, one test). Use when adding KeePassXC to a box as a standalone candy.
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.
# charly.yml
my-desktop-image:
candy:
- selkies-desktop # or another desktop base
- keepassxc # this layer
One 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.
/charly-build:secretsThis candy is the GUI for editing .kdbx databases. /charly-build:secrets is the charly 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 charly's keyring backend reads them. No charly-side .kdbx configuration is involved./charly-infrastructure:keepassxc-keyring for the candy that wires KeePassXC as the host's Secret Service provider./charly-build:secrets — charly CLI credential store (Secret Service + GPG; reads a KeePassXC database only via its FdoSecrets / Secret Service exposure)/charly-image:layer — candy authoring reference/charly-check:check — declarative testing referenceUse when the user asks about:
charly secretstools
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.
tools
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.
tools
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).
tools
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).