env-secrets-manager

Audit environment files and detect secret leaks in repositories and CI/CD pipelines.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ThalesAndrades/forumfoup2026 --skill env-secrets-manager-thalesandrades
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: env-secrets-manager
Source: https://github.com/ThalesAndrades/forumfoup2026/tree/main/.claude/skills/env-secrets-manager
Command: npx skills add https://github.com/ThalesAndrades/forumfoup2026 --skill env-secrets-manager-thalesandrades

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires scripts/env_auditor.py, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Managing environment variables and secrets securely across development and production environments can be complex and error-prone.

Core Features & Use Cases

  • Secrets auditing and leak detection in repositories and CI/CD pipelines.
  • Lifecycle guidance for environment files like .env and .env.example.
  • Rotation readiness and operational pointers for credential management.
  • Integration outputs for automation tools like CI pipelines and secret managers.
  • Use case: Ensure all secrets are rotated regularly and not hardcoded, reducing security risks during development or incident response.

Quick Start

Run the env auditor script to scan project directories for potential secret leaks and review findings in a report.

Frequently Asked Questions about env-secrets-manager

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

FAQPage Schema
How do I scan my repository for environment variable leaks and hardcoded secrets?

To scan for environment variable leaks, run the env auditor script against project directories. It detects hardcoded secrets in repositories and CI/CD pipelines, then generates a report of findings to review.

What is the best way to manage .env file lifecycle and enforce secret hygiene across environments?

Managing .env file lifecycle requires following operational pointers and rotation readiness guidelines. This approach prevents hardcoded credentials and enforces secret hygiene across development and production environments.

Can I integrate secret leak detection into CI pipelines and pre-commit checks?

Yes, you can integrate secret leak detection into CI pipelines and pre-commit checks. The skill provides integration outputs for automation tools to prevent leaks and enforce hygiene during development.

How do I prepare for credential rotation and incident response involving exposed environment secrets?

Preparing for credential rotation involves following the rotation readiness guidance and operational pointers provided. This facilitates rapid incident response and helps maintain compliance when environment secrets are exposed.

Does this approach work with existing secret stores and external secret managers?

Yes, this approach works with existing secret stores and external secret managers. It provides integration outputs designed to connect with automation tools and secret managers to securely manage environment variables.