keepass-hygiene

Enforce security rules for KeePass credential management and secret retrieval.

6|1|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/L3DigitalNet/Claude-Code-Plugins --skill keepass-hygiene
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: keepass-hygiene
Source: https://github.com/L3DigitalNet/Claude-Code-Plugins/tree/main/plugins/keepass-cred-mgr/skills/keepass-hygiene
Command: npx skills add https://github.com/L3DigitalNet/Claude-Code-Plugins --skill keepass-hygiene

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces critical security rules for interacting with KeePass, preventing accidental exposure or misuse of sensitive credentials.

Core Features & Use Cases

  • Credential Security: Ensures that inactive or restricted credentials are not used.
  • Secure Handling: Guides the secure retrieval and use of secrets, especially for SSH/GPG keys.
  • Rotation Safety: Provides a safe workflow for rotating credentials, preventing outages.
  • Use Case: Before performing any operation that involves accessing or modifying credentials in KeePass, this skill's rules are automatically applied to ensure best practices are followed.

Quick Start

Ensure all credential operations adhere to the defined KeePass hygiene rules.

Frequently Asked Questions about keepass-hygiene

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

FAQPage Schema
How do I secure KeePass credentials during automated retrieval?

Securing KeePass credentials requires enforcing rules that block inactive or restricted entries from being accessed and restricting data output to prevent accidental exposure of sensitive key material during automated retrieval.

What is the safest workflow for rotating credentials in KeePass?

The safest workflow for rotating credentials in KeePass involves applying strict hygiene rules that verify entry status and enforce secure generation parameters, preventing outages and ensuring restricted credentials are skipped.

How do I handle SSH and GPG keys stored in KeePass securely?

Handling SSH and GPG keys securely requires following specific KeePass hygiene rules for sensitive key material, ensuring secure retrieval practices are applied to all interactions involving these secrets via MCP tools.

Can I use MCP tools to interact with KeePass without exposing secrets?

You can use MCP tools to interact with KeePass without exposing secrets by applying strict data output rules that govern how secrets are retrieved and displayed during credential operations.

What are the limitations when enforcing KeePass credential hygiene?

Limitations when enforcing KeePass credential hygiene include the strict requirement to adhere to specific rules regarding entry access and credential generation parameters, meaning restricted or inactive entries cannot be bypassed.