env-guard

Detect secret leakage and unsafe environment handling across workspace files.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/EnesMeyzin98/Meridian --skill env-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: env-guard
Source: https://github.com/EnesMeyzin98/Meridian/tree/main/agents/skills/env-guard
Command: npx skills add https://github.com/EnesMeyzin98/Meridian --skill env-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Check for secret leakage and unsafe environment handling across the workspace, including tracked files, docs, panel settings, logs, scripts, and packaging artifacts.

Core Features & Use Cases

  • Scans for secrets in .env templates, config files, and startup helpers.
  • Validates operator panel settings do not expose secrets in responses or UI.
  • Reports findings with a clear guard verdict and actionable remediation steps.

Quick Start

Run the env-guard scan to verify secrets are not leaked and environment handling is safe.

Frequently Asked Questions about env-guard

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

FAQPage Schema
How do I scan my workspace for secret leakage in .env templates and config files?

To scan for secret leakage, target .env templates and config files to detect tracked secrets. The scan validates placeholder usage and reports findings with a clear guard verdict and actionable remediation steps.

What is unsafe environment handling in startup scripts and packaging paths?

Unsafe environment handling occurs when startup scripts and packaging paths expose or track secrets. Scanning these paths verifies secrets are not tracked, placeholders are used, and environment handling remains safe across the software workspace.

How do I prevent operator panel settings from exposing secrets in UI responses?

Prevent exposing secrets by validating operator panel settings. The scan verifies that panel settings and UI responses never expose secrets, reporting findings with a clear guard verdict and remediation steps.

Can I use this to check log safety and verify secrets are not tracked in docs?

Yes, you can check log safety and verify secrets are not tracked in docs. The scan targets logs, docs, and scripts to detect potential leaks, ensuring secrets remain untracked and environment handling is safe.

Does env-guard work without external dependencies for environment security scanning?

Yes, env-guard operates without external dependencies to scan for environment security risks. It independently identifies secret leakage and unsafe handling across .env templates, config files, logs, and packaging paths.

What's the best way to detect potential leaks across config parsing and startup helpers?

Apply a comprehensive scan to config parsing and startup helpers to detect potential leaks. This verifies placeholders are used, secrets are not tracked, and reports findings with a clear guard verdict and actionable remediation steps.