1password
Set up and use 1Password CLI for sign-in, desktop integration, and reading or injecting secrets.
Security Assessment
Detected risks:
About 1password
The 1Password skill provides a structured workflow for integrating 1Password CLI into development environments, enabling secure access to credentials and secrets without exposing them in code or configuration files. It solves the common problem of managing sensitive data during development by leveraging 1Password's desktop app integration and CLI tools to inject secrets directly into commands and environments at runtime.
This skill implements a tmux-based session management approach to handle 1Password CLI authentication reliably. Since the shell tool creates fresh TTYs per command, direct `op` invocations would trigger repeated authentication prompts. By running all `op` commands within a persistent tmux session, the skill maintains authenticated state across multiple operations, streamlining workflows that require reading vaults, listing items, or injecting secrets into running processes.
The primary use case targets developers who need to access production credentials, API keys, or environment-specific secrets during local development, testing, or deployment tasks. It's particularly valuable for teams already using 1Password for credential management, as it extends that security model into CLI-based workflows. DevOps engineers automating deployments, backend developers working with external APIs, and security-conscious teams can use this skill to eliminate hardcoded secrets while maintaining productivity.
FAQ
Why is tmux required for 1Password CLI operations?
The shell tool creates a fresh TTY for each command, which would cause 1Password CLI to prompt for authentication repeatedly. Running `op` commands inside a tmux session maintains an authenticated state across multiple operations, avoiding re-authentication prompts and failures.
What are the prerequisites for using this skill?
You need the 1Password CLI (`op`) installed, the 1Password desktop app running and unlocked, and desktop app integration enabled. The skill also requires tmux for session management. If working with multiple accounts, you'll need to specify which account to use via `--account` flag or `OP_ACCOUNT` environment variable.
How does this skill prevent secret exposure?
The skill enforces guardrails that prevent pasting secrets into logs, chat, or code. It prefers using `op run` or `op inject` commands that inject secrets directly into command environments at runtime rather than writing them to disk or displaying them in output.
What should I do if I get 'account is not signed in' errors?
Re-run `op signin` inside the tmux session and authorize the request in the 1Password desktop app. The skill requires successful `op whoami` verification before attempting any secret read operations.
Can I use 1Password CLI without the desktop app?
While the skill primarily uses desktop app integration for authentication, you can use `op account add` for sign-in without app integration if needed. However, the recommended workflow leverages the desktop app for streamlined authentication.
Install 1password
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
steipete/clawdis