1passwordlisted
Install: claude install-skill kcmadden/claude-code-1password-skill
# 1Password Skill
> **Platform:** macOS. The Terminal-launch secret-entry flow uses AppleScript and Terminal.app.
> The `op` CLI commands themselves work on any OS, but this skill's secret-entry pattern is macOS-only.
## Critical: Never Type Secrets Into Claude Code
**Claude Code can see everything typed in its terminal and chat.**
When a user needs to store a secret, ALWAYS use the Terminal launch pattern:
1. Generate a pre-filled script with known values already set
2. Use `launch-in-terminal.sh` to open it in Terminal.app
3. User types secrets in that window - Claude Code cannot see it
4. 1Password stores the secret, outputs `op://` references back to Claude
```bash
# Claude generates the script, then launches it outside its own view:
bash scripts/launch-in-terminal.sh /tmp/setup-my-service.sh "Service Name Setup"
```
Never ask users to paste API keys, passwords, or tokens into:
- The Claude Code chat
- A Bash tool call visible in Claude Code
- Any file Claude Code writes before it's stored in 1Password
---
## Setup Check
Always verify the CLI is ready before any operation:
```bash
bash scripts/check_setup.sh
```
If not installed: https://developer.1password.com/docs/cli/get-started/
If not signed in: unlock the **1Password desktop app** (after Mac restart, the app must be unlocked before the CLI works)
---
## Storing Secrets: The Terminal Launch Pattern
When a user needs to store a new secret or credential:
**Step 1 - Generate the script** (Claude does this