shelve

Manage secrets and environment variables via CLI with cloud synchronization.

Updated Jan 2, 2026

Search Tags:#devops #security #cli #secrets management #environment variables #sync

Ready to run

npx skills add https://github.com/onmax/claude-config --skill shelve-onmax

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: shelve
Source: https://github.com/onmax/claude-config/tree/main/skills/shelve
Command: npx skills add https://github.com/onmax/claude-config --skill shelve-onmax

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the secure management and synchronization of environment variables across different projects and team members, ensuring consistency and reducing security risks.

Core Features & Use Cases

Secrets Management: Securely store and retrieve sensitive environment variables.
Local Synchronization: Sync cloud-stored secrets to local .env files.
Command Execution: Run commands with secrets automatically injected, eliminating the need for manual .env file management.
Use Case: A development team can use Shelve to ensure all members are using the same production API keys and database credentials without ever sharing them directly or committing them to version control.

Quick Start

Use the shelve skill to pull the latest environment variables for the production environment.

Frequently Asked Questions about shelve

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

FAQPage Schema

How do I securely manage environment variables for a development team?▼

Securely manage environment variables by using a CLI tool to store secrets in cloud storage and synchronize them to local .env files. This ensures team members share configurations without committing sensitive data to version control.

How do I sync cloud-stored secrets to local .env files?▼

Sync cloud-stored secrets to local .env files by running a CLI command that pulls the latest project configurations. This automatically updates your local environment variables to match the cloud-stored values.

Can I run commands with secrets automatically injected instead of using a .env file?▼

Run commands with secrets automatically injected by using the CLI tool to execute your scripts. This eliminates manual .env file management by directly passing environment variables into the command execution context.

Does this secrets management approach support monorepo structures?▼

Yes, this secrets management approach supports monorepo structures. The CLI tool accommodates project-specific configurations, allowing you to manage distinct sets of environment variables across different packages within a single repository.

What is the best way to share production API keys without committing them to version control?▼

The best way to share production API keys safely is to use a CLI tool that synchronizes cloud-stored secrets to local environments. This ensures all team members use identical credentials without exposing them in version control.

Why use a dedicated secrets management tool instead of sharing .env files directly?▼

Use a dedicated secrets management tool instead of sharing .env files directly to eliminate security risks. It securely synchronizes environment variables from cloud storage, ensuring consistency across team members without exposing sensitive data.