1password

Set up 1Password CLI authentication and manage secrets via the op command.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/RobbyMo81/assistantrobby --skill 1password-robbymo81
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1password
Source: https://github.com/RobbyMo81/assistantrobby/tree/main/skills/1password
Command: npx skills add https://github.com/RobbyMo81/assistantrobby --skill 1password-robbymo81

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents insecure or failing CLI secret access by guiding users through installing and signing in to the 1Password CLI, enabling desktop app integration, and enforcing a dedicated tmux session to avoid repeated prompts and leaked credentials.

Core Features & Use Cases

  • Install and verify the op CLI and confirm desktop app integration for seamless authentication.
  • Secure sign-in and authorization using a fresh tmux session and verification steps before any secret operations.
  • Safe secret operations including reading, injecting, and running secrets, with support for multi-account workflows and OP_ACCOUNT selection.
  • Use case: a developer or sysadmin who must retrieve or inject credentials during deployment or maintenance without exposing keys or breaking interactive authorization flows.

Quick Start

Start a fresh tmux session, sign in with the 1Password CLI inside it, and verify access before reading or injecting secrets.

Frequently Asked Questions about 1password

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I access 1Password secrets from the command line without exposing credentials?

To securely access 1Password secrets from the command line, use the op CLI with desktop app integration enabled. This allows you to read, inject, and run secrets without exposing credentials by authorizing access through the 1Password desktop app.

Why does the 1Password CLI keep prompting me for authorization during terminal workflows?

Repeated 1Password CLI authorization prompts occur when not using a dedicated tmux session. Starting a fresh tmux session for your op commands maintains persistent authentication and prevents interactive authorization flows from breaking.

What do I need to use the op CLI for secure secret management on macOS and Linux?

Using the op CLI for secure secret management requires installing the op binary, enabling desktop app integration, and running commands within a fresh tmux session to authorize access via the 1Password desktop app.

Can I manage multi-account workflows when injecting secrets with the 1Password CLI?

Yes, you can manage multi-account workflows when injecting secrets with the 1Password CLI by using the OP_ACCOUNT selection variable. This supports retrieving and running credentials across different accounts within your secure tmux session.

Does the 1Password CLI work with Windows for deployment and maintenance tasks?

Yes, the 1Password CLI works with Windows, macOS, and Linux for deployment and maintenance tasks. It enables developers to safely retrieve or inject credentials by requiring desktop app integration and a tmux session for terminal workflows.

What is the best way to prevent insecure CLI secret access during automated deployments?

The best way to prevent insecure CLI secret access during deployments is enforcing a dedicated tmux session with the op CLI. This approach verifies access via the 1Password desktop app, avoiding leaked credentials and repeated prompts.