From gpg-ops
List GPG keys on the local keyring — public keys, secret keys, or both. Use when the user wants to see what keys they have, find a key ID or fingerprint, or check whether a contact's public key is already imported before encrypting to them.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gpg-ops:gpg-list-keysThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The user asks "what GPG keys do I have", needs a key ID or fingerprint to feed into another command, or wants to check whether a recipient's public key is on the keyring.
The user asks "what GPG keys do I have", needs a key ID or fingerprint to feed into another command, or wants to check whether a recipient's public key is on the keyring.
Secret keys (keys whose private half is on this machine — i.e. your keys):
gpg --list-secret-keys --keyid-format=long
Public keys (everything on the keyring, including imported public keys for recipients):
gpg --list-keys --keyid-format=long
With fingerprints (needed for trust signing or precise reference):
gpg --list-keys --with-fingerprint --keyid-format=long
Filter by email or name:
gpg --list-keys "<email-or-name>"
pub ed25519/ABCDEF1234567890 2026-04-30 [SC]
1234567890ABCDEF1234567890ABCDEF12345678
uid [ultimate] Real Name <[email protected]>
sub cv25519/FEDCBA0987654321 2026-04-30 [E]
pub / sec — primary public / secret key. Flags: S=sign, C=certify, E=encrypt, A=authenticate.ed25519/ABC… form is the long key ID (last 16 hex chars of the fingerprint).sub — subkey. Encryption typically lives on a subkey for ed25519 primaries.ultimate (your own key), full, marginal, unknown.gpg-export-public-key skill.gpg-encrypt skill (need their key on the ring first; import via gpg --import recipient.asc).npx claudepluginhub danielrosehill/claude-code-plugins --plugin gpg-opsProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.