keys-manager_skill

Overview

This skill manages API keys and secrets from the terminal using the keys CLI. It provides secure local storage, interactive browsing, profile-based isolation, and utilities to import/export .env files for project workflows. It’s designed for quick retrieval, safe sharing, and organized multi-project key management.

How this skill works

The tool stores keys in an encrypted store and exposes commands to add, get, edit, delete, and list keys. A TUI offers fuzzy search, masking, clipboard copy, and batch export to .env files. Profiles isolate keys per project or environment and commands respect the active profile. On macOS, biometrics (Touch ID) are used to gate access; other systems operate without a prompt.

When to use it

• Store API keys and secrets locally and retrieve them from the shell.
• Generate or update .env files for projects from a curated key set.
• Share masked key views during screen-sharing or demonstrations.
• Migrate or bulk-load secrets from existing .env files.
• Separate credentials per project or environment using profiles.

Best practices

• Use keys add <NAME> <VALUE> when you know exact names to avoid duplicates.
• Switch profiles (keys profile use) per project to avoid accidental secret leakage.
• Use keys peek for masked views during pair programming or presentations.
• Run keys import <file> to parse existing .env files; review new vs updated counts before accepting changes.
• Export with keys env or eval $(keys expose) only in trusted shells; avoid exporting into long-lived CI logs.

Example use cases

• Add and retrieve a service token: keys add OPENAI_KEY sk-XXXXX then keys get OPENAI_KEY.
• Create a project .env: keys profile use projectA; keys env > .env
• Bulk import secrets from a legacy .env: keys import .env and review the summary.
• Share credentials safely: keys see or keys peek to copy a single KEY=VAL to clipboard.
• Quickly switch environments: keys profile list to view profiles and keys profile use staging to activate staging credentials.