config-secrets

Manage AICP runtime secrets across env vars, tokens, and webhooks.

Updated Mar 26, 2026

Search Tags:#security #ci-cd #dotenv #env-vars #secrets-management #rotation

Ready to run

npx skills add https://github.com/cyberpunk042/devops-expert-local-ai --skill config-secrets

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: config-secrets
Source: https://github.com/cyberpunk042/devops-expert-local-ai/tree/main/.claude/skills/config-secrets
Command: npx skills add https://github.com/cyberpunk042/devops-expert-local-ai --skill config-secrets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage AICP's runtime secrets across env vars, tokens, and webhooks, ensuring secrets are added, rotated, and wired safely without leaking in code or logs.

Core Features & Use Cases

Inventory and catalog secrets (NAME, PURPOSE, SCOPE, LIFETIME, BLAST RADIUS) for operational readiness.
Rotate and wire secrets into the runtime (loader, consumer, and CI/CD) to support cloud backends and integrations.
Audit .env.example drift and ensure all env vars are declared and consumed by code.

Quick Start

Describe a secret to add or rotate and follow the four-step process to update .env, loader, and CI/CD configurations.

Frequently Asked Questions about config-secrets

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

FAQPage Schema

How do I manage environment variables and tokens to prevent secret leakage in CI/CD pipelines?▼

Secrets management prevents leakage by routing env vars, cloud backend tokens, and notification endpoints through a centralized loader. This enforces lifecycle controls and ensures sensitive values are never logged during execution.

How do I rotate existing tokens and wire them into a runtime configuration?▼

Rotating tokens involves a four-step process to update the .env file, the configuration loader, and CI/CD pipelines. This safely wires new tokens into their consumers across local and production runtimes without logging sensitive values.

What is the best way to audit .env.example drift and track undeclared environment variables?▼

Auditing .env.example drift involves cataloging all environment variables to ensure they are declared and actively consumed by code. This tracks placeholder drift and maintains operational readiness by preventing orphaned variables.

Can I catalog secrets with metadata like blast radius and lifetime for operational readiness?▼

Secret cataloging supports operational readiness by tracking each secret's NAME, PURPOSE, SCOPE, LIFETIME, and BLAST RADIUS. This inventory ensures all tokens and endpoints are documented for safe lifecycle management.

Does adding new environment variables require updating the config loader and CI/CD configurations simultaneously?▼

Adding new environment variables requires updating the .env file, the config loader, and CI/CD configurations simultaneously. This end-to-end process ensures secrets are wired to their consumers and tracked in .env.example without leaking.

Why do I need runbooks and tests when managing secrets across local and production runtimes?▼

Runbooks and tests are maintained alongside secrets management to enforce lifecycle controls and verify safe wiring across local and production runtimes. They ensure sensitive values are loaded correctly and validate operational readiness.

Clear-Capabilities