env-secrets-manager

Audit environment-variable hygiene and detect leaked secrets in codebases.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/Godhand-Arnav/Scalar-finals --skill env-secrets-manager-godhand-arnav
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: env-secrets-manager
Source: https://github.com/Godhand-Arnav/Scalar-finals/tree/main/.claude/skills/env-secrets-manager
Command: npx skills add https://github.com/Godhand-Arnav/Scalar-finals --skill env-secrets-manager-godhand-arnav

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Manage environment-variable hygiene and secrets safety across local development and production workflows. Audit env files (.env and .env.example) lifecycle, detect secret leakage in repository work trees, and provide rotation-ready guidance.

Core Features & Use Cases

  • .env and .env.example lifecycle guidance
  • Secret leak detection for repository working trees
  • Severity-based findings for likely credentials
  • Operational pointers for rotation and containment
  • Integration-ready outputs for CI checks

Quick Start

Run the env_auditor.py script on a repository to detect secret leaks and generate a CI-friendly JSON 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 detect hard-coded secrets and credentials in my repository?

Detect hard-coded secrets by running an audit script on your repository work tree to scan for leaked credentials. It analyzes your codebase and generates a CI-friendly JSON report with severity-based findings for likely exposed secrets.

What is the best way to audit .env file hygiene in a CI pipeline?

Audit .env file hygiene in a CI pipeline using a script that evaluates .env and .env.example lifecycle guidance. It outputs integration-ready JSON reports with severity-based findings, enabling automated environment-variable checks during continuous integration.

How do I check if my environment variables are ready for rotation?

Check rotation readiness by auditing your environment variables for configuration drift and leaked credentials. The audit provides operational pointers for containment and rotation, ensuring your environment is prepared for secure secret lifecycle management.

Can I use this to scan my local development environment for secret leaks?

You can scan your local development environment for secret leaks by running the audit script on your local repository. It identifies exposed credentials in your work tree and provides operational pointers for immediate containment and rotation.

What is .env lifecycle guidance and why do I need it?

.env lifecycle guidance manages environment-variable hygiene across development and production workflows by auditing .env and .env.example files. You need it to detect configuration drift, identify leaked secrets, and maintain secure credential rotation practices.