secret-capture

Solid

Capture 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.

AI & Automation 1 stars 1 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 78/100

Stars 20%
10
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Secret capture Invoke this skill whenever you need the user to supply a credential. Never ask the user to paste a secret into chat or the terminal — use this skill instead. ## When to use - Onboarding a new MCP, integration, or service that needs an API key - Rotating an existing credential - Creating a new n8n credential, Cloudflare Worker secret, GitHub secret, Coolify env var - Storing a personal API key the user will consume from their shell / agents (→ 1Password) - Any time mid-task you realize "I need a credential here" ## Decision rule — which destination One secret, one home. Pick based on who consumes the value: - **User consumes it** (terminal, agents, MCPs, HTTP calls from the user's machine) → `1password` - **System consumes it natively** (n8n runs the workflow that uses this token, GitHub Actions runs the workflow, Cloudflare Worker runtime reads it, Coolify app reads the env var) → the matching target adapter Never store the same secret in two places. ## Invocation The skill is a bash script. Invoke via the Bash tool: ```bash bash ~/.claude/skills/secret-capture/scripts/capture.sh --target <target> [target-flags] [--rotate] [--expect <shape>] [--from <op://ref|source-spec>] ``` You pass only the destination metadata. You never pass, read, or handle the value. By default the script opens a hidden-input dialog, captures the value, pipes it directly to the destination, and returns a reference on stdout. With `--from`, it pulls the value from an existin...

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

AI & Automation Solid

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.

31 Updated today
hex
Data & Documents Listed

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.

5 Updated 4 days ago
kcmadden
Data & Documents Listed

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.

0 Updated 1 weeks ago
dimaad5017-dotcom