sync-env-from-1password

Synchronize environment variables from 1Password to a local .env file.

27|4|Updated Jun 19, 2025
One-click install
npx skills add https://github.com/markmhendrickson/neotoma --skill sync-env-from-1password
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-env-from-1password
Source: https://github.com/markmhendrickson/neotoma/tree/main/.cursor/skills/sync-env-from-1password
Command: npx skills add https://github.com/markmhendrickson/neotoma --skill sync-env-from-1password

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the secure synchronization of environment variables from 1Password to your local .env file, preventing manual errors and ensuring sensitive credentials are managed safely.

Core Features & Use Cases

  • Secure Credential Management: Fetches secrets directly from 1Password, never exposing them in logs or plain text.
  • Automated .env Updates: Updates your local .env file based on predefined mappings.
  • Environment-Specific Keys: Supports different keys for development, production, and other environments.
  • Use Case: Ensure your local development environment always has the latest API keys for various services by running this sync command before starting your development server.

Quick Start

Run the sync_env_from_1password command to update your local .env file.

Frequently Asked Questions about sync-env-from-1password

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

FAQPage Schema
How do I sync environment variables from 1Password to a local .env file?

This Skill synchronizes environment variables from 1Password to your local .env file by fetching secrets via the 1Password MCP server or CLI and applying configurable mappings.

What is the best way to automate .env updates for different environments?

Automating .env updates is handled through environment-specific configurations, allowing you to define dynamic credential mappings for development, production, or other target environments securely.

Does syncing .env from 1Password preserve my existing unmanaged variables?

Yes, syncing .env from 1Password preserves unmanaged variables by creating automatic backups and only updating the specific credentials defined in your predefined mappings.

Do I need the 1Password CLI to retrieve secrets for my environment variables?

You do not strictly need the 1Password CLI as the Skill can retrieve secrets via the 1Password MCP server, but it supports either method for secure credential management.

Can I use this to fetch secrets for local development without exposing them in logs?

Yes, you can fetch secrets for local development without exposing them in logs, as the synchronization mechanism retrieves credentials securely and never writes them to plain text outputs.