env-management

Rotate and audit environment secrets across organizations and agents.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MrWest3/west-command-center --skill env-management-mrwest3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: env-management
Source: https://github.com/MrWest3/west-command-center/tree/main/templates/analyst/.claude/skills/env-management
Command: npx skills add https://github.com/MrWest3/west-command-center --skill env-management-mrwest3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

West Command Center needs a robust system to manage, rotate, and audit environment variables and credentials across an organization and its agents, ensuring secure access and quick recovery after credential changes.

Core Features & Use Cases

  • Hierarchical secret scope: supports 4-layer env hierarchy (base shell, CTX vars, org-level, agent-level) with proper overrides.
  • Rotation governance: prompts hard-restarts when keys rotate and supports agent-specific vs org-wide secrets.
  • Onboarding & auditing: onboard new tools that require credentials, check existing secrets, and diagnose missing keys.
  • Use Case: When a key is compromised, rotate it across the org and propagate updates to all agents to restore access.

Quick Start

Rotate a compromised API key across the organization and propagate the change to all affected agents.

Frequently Asked Questions about env-management

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

FAQPage Schema
How do I rotate compromised environment secrets across my organization?

The environment secret hierarchy supports a 4-layer override system: base shell, CTX vars, org-level, and agent-level. This structure properly isolates agent-specific credentials from org-wide secrets to prevent unauthorized cross-scope access.

How do I audit existing credentials and diagnose missing environment keys?

You can audit existing credentials and diagnose missing environment keys by running the secret management diagnostic check. It scans across orgs and agents to identify missing keys, validate existing credentials, and onboard new tools requiring access.

Do I need to manually restart agents when environment variables change?

Manual restarts are not required when environment variables change. The rotation governance automatically prompts hard-restarts for affected agents, ensuring safe updates and quick recovery of access after credential changes without manual intervention.

What's the best way to separate org-wide secrets from agent-specific secrets?

The best way to separate org-wide secrets from agent-specific secrets is using the hierarchical secret scope. It enforces strict separation between org-level and agent-level environment variables, applying proper overrides to maintain secure access boundaries.

Why does credential rotation require controlled restarts for agents?

Credential rotation requires controlled restarts because agents must reload their environment variables to apply the updated secrets safely. This hard-restart mechanism ensures agents restore access securely without retaining stale or compromised credentials in memory.