api-key-env-migration

Migrates plaintext API keys in Hermes config files to environment variable references.

Updated May 24, 2026

Search Tags:#secret management #api keys #hermes #env variables #config migration

Ready to run

npx skills add https://github.com/anxiety135790/hermes-skills --skill api-key-env-migration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: api-key-env-migration
Source: https://github.com/anxiety135790/hermes-skills/tree/main/.archive/security/api-key-env-migration
Command: npx skills add https://github.com/anxiety135790/hermes-skills --skill api-key-env-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps remove plaintext API keys from Hermes config files so secrets are easier to manage, safer to share, and less likely to be exposed accidentally.

Core Features & Use Cases

Secret migration: Replaces hardcoded API key values in config.yaml with environment variable references.
Environment setup: Stores keys in ~/.hermes/.env using standard VARNAME=value entries for cleaner secret management.
Safety and rotation: Supports separate variables for different providers, making key rotation and sharing safer without editing config files.

Quick Start

Ask the Skill to migrate the API keys in your Hermes configuration from plaintext values to .env variables and update the config to use environment references.

Frequently Asked Questions about api-key-env-migration

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

FAQPage Schema

How do I move plaintext API keys out of a Hermes config.yaml file?▼

Migrating API keys out of config.yaml involves replacing hardcoded values with environment variable references. This process secures secrets by storing them in a .env file while preserving the original configuration structure.

Why should I use environment variables for API key management in config files?▼

Using environment variables for API key management prevents accidental secret exposure. It separates credentials from configuration files, making keys easier to manage, safer to share, and simpler to rotate without editing config.

How do I configure multiple provider API keys in a .env file?▼

Configuring multiple provider API keys in a .env file uses standard VARNAME=value entries. This supports separate variables for different providers, enabling safe key rotation and sharing without altering the config.yaml file.

Does migrating secrets to .env variables preserve my existing Hermes configuration structure?▼

Migrating secrets to .env variables preserves your existing Hermes configuration structure. The process updates key bindings to secure variable names without altering the overall layout or breaking the config.yaml file.

What is the best way to separate API keys for different providers in Hermes?▼

The best way to separate API keys for different providers is using a .env file with distinct variable names. This allows independent key rotation and safer credential sharing without modifying the Hermes config.yaml.