secret-capture
SolidCapture a secret from the user via a hidden-input dialog (or pull it from an existing store with --from) and route it to exactly one destination (1Password, macOS Keychain, GitHub secret, Cloudflare Workers secret, Coolify env var, n8n credential, a local .env file, a remote SSH file, or an age-encrypted box keystore) without the value ever appearing in any tool result, log, or chat transcript. Auto-triggers whenever the agent needs a new credential, API key, token, password, or secret to configure a service, onboard an integration, set up an MCP, or rotate an existing credential. Use this every time you're about to say "paste your key here" — instead, invoke this skill.
Install
Quality Score: 78/100
Skill Content
Details
- Author
- D1DX
- Repository
- D1DX/secret-capture-skill
- Created
- 3 months ago
- Last Updated
- 1 weeks ago
- Language
- Shell
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
store-secret
Store secrets shared in chat into the cs session secret store. PROACTIVE - invoke immediately when the user shares API keys, passwords, tokens, or other credentials in their message; do not wait to be asked.
1password
Integrate 1Password secrets management into Claude Code workflows. Use when the user wants to: store API keys or credentials in 1Password, read secrets from 1Password into scripts or config, set up .env files using 1Password secret references, rotate or update credentials, manage developer secrets across projects, use 1Password service accounts for CI/CD, or integrate 1Password with tools like Claude Desktop, n8n, Docker, Supabase, GitHub Actions, or Replit. Triggers on phrases like "store in 1Password", "read from 1Password", "op://", "secret reference", "manage API keys with 1Password", "1Password CLI", or any request involving the `op` command.
secret-hygiene
Keep credentials out of source code and out of git. Use this skill WHENEVER writing, editing, or generating code that touches secrets of any kind — API keys, passwords, tokens, JWTs, private keys, connection strings, database URLs, webhook URLs, or deploy/SSH credentials — even when the user hasn't asked about security. Trigger it when adding config, writing deploy or automation scripts, wiring up a new service or SDK, creating a CLAUDE.md or README, or before proposing a git commit. Also use it when the user says a secret leaked, asks to scan a repo for exposed credentials, or wants a pre-commit hook. If a value looks like it could authenticate to something, this skill applies.