dotenc

Manage Git-native encrypted environment variables using SSH keys.

Updated Mar 29, 2025
One-click install
npx skills add https://github.com/ivanfilhoz/dotenc --skill dotenc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotenc
Source: https://github.com/ivanfilhoz/dotenc/tree/main/skills/dotenc
Command: npx skills add https://github.com/ivanfilhoz/dotenc --skill dotenc

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a secure, Git-native way to manage environment secrets for applications, eliminating the need for external secret management services and leveraging existing SSH keys for encryption.

Core Features & Use Cases

  • Encrypted Environments: Store sensitive variables in encrypted .env files committed to your repository.
  • SSH Key Integration: Uses your existing SSH keys for encryption and decryption, avoiding extra key management.
  • Secure Command Execution: Run commands with secrets automatically decrypted and injected into the environment.
  • Team Collaboration: Securely grant and revoke access to environments for team members.
  • Use Case: A developer needs to run a local development server that requires API keys. They can use dotenc dev to start the server with their encrypted API keys automatically loaded, without exposing them in plain text.

Quick Start

Use the dotenc skill to initialize dotenc in the current repository for the user 'alice'.

Frequently Asked Questions about dotenc

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

FAQPage Schema
How do I encrypt environment variables using SSH keys?

You can encrypt environment variables using SSH keys by initializing a Git-native environment that stores sensitive data in encrypted `.env` files. This leverages your existing SSH keys for decryption, avoiding the need for external secret management services.

Can I store encrypted `.env` files directly in my Git repository?

Yes, you can store encrypted `.env` files directly in your Git repository. This approach secures application secrets at rest and enables team collaboration by granting access to environments through SSH key management.

What is the best way to run local development servers with encrypted API keys?

The best way to run local servers with encrypted API keys is using secure command execution. This automatically decrypts your secrets and injects them into the environment, allowing you to start servers without exposing plain text.

Does this approach work for CI/CD pipelines and team access control?

Yes, this approach supports CI/CD integration and team access control. It facilitates secure command execution within repositories and allows you to securely grant or revoke environment access for team members using SSH keys.

Do I need an external secret management service to manage application secrets?

No, you do not need an external secret management service. This method provides a Git-native way to manage environment secrets by leveraging existing SSH keys for encryption and decryption directly within your repository.