1password

Manage application secrets via the 1Password CLI (op) with op:// paths.

Updated May 3, 2026
One-click install
npx skills add https://github.com/Yangel-hide/video-production-planner-agent --skill 1password-yangel-hide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1password
Source: https://github.com/Yangel-hide/video-production-planner-agent/tree/main/optional-skills/security/1password
Command: npx skills add https://github.com/Yangel-hide/video-production-planner-agent --skill 1password-yangel-hide

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Centralizes and secures secrets management by leveraging the 1Password CLI (op) to install, authenticate, and read/inject secrets in workflows.

Core Features & Use Cases

  • Setup and authentication using 1Password CLI (op)
  • Read secrets with op read from op:// paths
  • Inject secrets into templates or configs with op inject
  • Run commands with secrets via op run
  • Desktop app integration or service-account-based authentication for non-interactive use
  • Use cases include CI/CD pipelines, local development, and cloud deployments

Quick Start

Install the op CLI, sign in with a suitable method, and read a secret using an example path

Frequently Asked Questions about 1password

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

FAQPage Schema
How do I inject secrets into configuration files using the 1Password CLI?

Secret injection uses the 1Password CLI to populate configuration templates with secrets retrieved from op://vault/item paths, minimizing plaintext token exposure in development and production workflows.

Can I use 1Password CLI for non-interactive secret retrieval in CI/CD pipelines?

Yes, non-interactive CI/CD secret retrieval uses service-account-based authentication with the 1Password CLI to read and inject secrets into automated deployments without manual sign-in.

What is the best way to manage application secrets across staging and production environments?

Managing application secrets across environments uses the 1Password CLI to read secrets from structured op:// paths and inject them into workflows, centralizing access control and secret rotation.

Do I need a service token to read secrets with op CLI?

Reading secrets with the op CLI requires a configured account using either a service token for non-interactive automation or desktop app integration for local development access.

Why minimize plaintext token exposure when using secret management in deployments?

Minimizing plaintext token exposure prevents credential leakage by using the 1Password CLI to directly run commands and inject secrets into templates rather than storing them in plaintext configuration files.

What are the limitations of using desktop integration for secret retrieval in automated workflows?

Desktop integration for secret retrieval requires interactive sign-in, making it unsuitable for automated cloud deployments where service-account-based authentication is necessary for non-interactive op CLI access.