ls-keepass-secrets

Fetch and rotate KeePass secrets using repo-local mappings without writing values to tracked files.

3|2|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/CruxExperts/localsetup --skill ls-keepass-secrets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ls-keepass-secrets
Source: https://github.com/CruxExperts/localsetup/tree/main/_localsetup/skills/ls-keepass-secrets
Command: npx skills add https://github.com/CruxExperts/localsetup --skill ls-keepass-secrets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a safe way to access KeePass-stored secrets using repo-local mappings, ensuring that secret values never live in repo files and are only exposed in ephemeral runtime contexts.

Core Features & Use Cases

  • Secret resolution via keepass-config.yaml and host maps to KeePass entries for multiple services.
  • Password rotation and generation on demand without writing secrets to tracked files.
  • Batch operations via ensure with dry-run and force semantics, including input validation and error reporting.

Quick Start

Fetch a KeePass-stored secret by its logical ID and optionally rotate or generate a password without writing secrets to the repo.

Frequently Asked Questions about ls-keepass-secrets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fetch KeePass secrets using repo-local mapping files?

Batch secret operations use the ensure command with dry-run and force semantics, validating inputs and reporting errors while interacting with keepassxc-cli to read or write entries without leaking secret values into tracked files.

Can I automate password rotation for KeePass entries without writing secrets to the repo?

Password rotation generates new passwords on demand and writes them directly to KeePass entries via keepassxc-cli, strictly avoiding the storage of secret values in tracked repository files during the rotation process.

Does this approach to secret management require the keepassxc-cli tool?

Yes, the secret resolution and rotation process enforces safety checks for KeePass CLI availability and validates inputs before loading per-host maps to interact with keepassxc-cli for reading and writing entries.

What happens if a host-specific secret map is missing during batch operations?

Batch operations enforce safety checks for missing maps and report input validation errors, preventing the process from continuing if a required host-specific mapping file is not found.

What is the best way to manage multiple host-specific KeePass secret mappings?

Managing multiple hosts involves loading secrets and keepass-config.yaml alongside per-host maps, allowing batch operations to resolve and rotate KeePass-stored secrets safely across different host environments.