setup-env

Detect and execute scripts/setup-env.sh to restore credentials from 1Password vaults.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ebijun1007/vibe-coding --skill setup-env-ebijun1007
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-env
Source: https://github.com/ebijun1007/vibe-coding/tree/main/.claude/skills/setup-env
Command: npx skills add https://github.com/ebijun1007/vibe-coding --skill setup-env-ebijun1007

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the secure setup of development environment credentials by leveraging 1Password vaults and per-project scripts to quickly restore required config and secrets for a project.

Core Features & Use Cases

  • Detects and proposes execution of project-specific scripts/setup-env.sh to restore credentials and environment configuration.
  • Validates that 1Password CLI is installed and vault access is available, with clear guidance if prerequisites are missing.
  • Safeguards user consent and preserves existing settings, offering safe behavior in non-interactive environments.

Quick Start

Run the skill in a project directory that contains scripts/setup-env.sh to fetch and apply credentials from 1Password.

Frequently Asked Questions about setup-env

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

FAQPage Schema
How do I automate development environment setup with 1Password?

Automate development environment setup by detecting and executing project-specific scripts/setup-env.sh to securely fetch and apply credentials from 1Password vaults. The process validates 1Password CLI access and requires explicit user consent before running any setup scripts.

What are the prerequisites for using 1Password vaults to restore project credentials?

Prerequisites for restoring project credentials include having the 1Password CLI installed and vault access granted. The target project must also contain a scripts/setup-env.sh file to be detected and executed.

How does this environment setup handle existing configuration files?

Environment setup preserves existing settings by safeguarding user consent before applying credentials. It offers safe behavior in non-interactive environments, ensuring current configuration files are not overwritten without explicit approval.

What happens if 1Password CLI is missing or vault access is denied during env setup?

If 1Password CLI is missing or vault access is denied during environment setup, the process provides clear guidance on the missing prerequisites. It will not execute the setup scripts until the required access is restored.

Can I run project credential setup scripts in non-interactive environments?

Yes, you can run project credential setup scripts in non-interactive environments. The setup process includes specific safeguards to handle non-interactive contexts securely without requiring manual consent prompts.

When do I need a per-project script to fetch development secrets?

You need a per-project script like scripts/setup-env.sh when your project stores credentials in 1Password and requires automated restoration of local environment configuration and secrets to run correctly.