1password-sync

Synchronize local secret files with 1Password via the op CLI.

8|1|Updated Jul 7, 2025
One-click install
npx skills add https://github.com/dasheck0/qraft-templates --skill 1password-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1password-sync
Source: https://github.com/dasheck0/qraft-templates/tree/main/opencode-global-skills/1password-sync
Command: npx skills add https://github.com/dasheck0/qraft-templates --skill 1password-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Syncs local secret files (like .env, provisioning profiles, certificates, or any secret file) with 1Password using the op CLI. Handles uploading files as Secure Notes, checking for updates, downloading and replacing local files, and managing a project-local mapping file (.op-sync.json) that maps local paths to 1Password vault items — so team members can stay in sync. Also helps with installing the op CLI and signing in if needed.

Core Features & Use Cases

  • Upload local secret files to 1Password as Secure Notes with content stored in the notesPlain field.
  • Maintain a project-local .op-sync.json mapping file to link local paths to 1Password items, enabling team-wide consistency.
  • Download secrets from 1Password to replace local files, and check for changes or diffs before syncing.
  • Guide user through op CLI authentication, vault/account selection, and safe diff/check workflows.

Quick Start

Create your first mapping by syncing a local secret file to 1Password using the op CLI after signing in.

Frequently Asked Questions about 1password-sync

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

FAQPage Schema
How do I sync local .env files with 1Password Secure Notes?

To sync local .env files with 1Password, you use the op CLI to upload file contents as Secure Notes, storing data in the notesPlain field. A project-local .op-sync.json mapping file tracks the link between local paths and 1Password vault items for consistent team access.

What is the best way to manage team secrets stored in local files using 1Password?

Managing team secrets with 1Password involves maintaining a project-local .op-sync.json mapping file. This file links local file paths to specific 1Password vault items, allowing team members to download replacements, check diffs, and stay in sync across the project.

Do I need the op CLI installed to synchronize secrets with 1Password?

Yes, the op CLI is required to synchronize secrets with 1Password. The synchronization process relies on the op CLI for authentication, vault detection, and transferring file contents to and from 1Password Secure Notes.

Can I check for differences between local secret files and 1Password vault items before downloading?

Yes, you can perform diff checks between local files and 1Password vault items before downloading. The sync workflow supports safe diff and check operations to identify changes, ensuring you only replace local files when updates are confirmed.

How does 1Password synchronization handle vault and account selection for different projects?

1Password synchronization handles vault and account selection through optional configuration within the .op-sync.json mapping file. It guides users through op CLI authentication and vault detection to ensure secrets are synced to the correct destination.