agentsclimarketplace

Environment config audit

Skill motao123/dev-workflow-kit/environment-config-audit

21 markdown-first software delivery workflow skills for Claude Code, Codex, and compatible agents. Standalone skill kit covering planning, debugging, CI, review, security, rollout, performance, data quality, and post-incident workflows.

Install
npx -y skills add motao123/dev-workflow-kit --skill environment-config-audit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when the main risk is environment parity, config drift, secrets wiring, flags, defaults, or deployment-time assumptions rather than code logic itself.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.9 KB, as published. Nobody here has run it

Environment Config Audit

Use this skill when a change may fail because environments or configuration assumptions are inconsistent.

Trigger Conditions

Use this skill when:

  • staging, production, or local behavior may differ because of config
  • env vars, secrets, feature flags, or defaults are part of the risk
  • deployment-time assumptions are unclear
  • the user wants to audit environment parity before release
  • a config or secrets issue is more likely than a code bug

Do not use this skill for pure code debugging when configuration is clearly not involved.

Workflow

  1. Identify the relevant environments and config surfaces.
  2. Map env vars, flags, defaults, secrets, and deployment assumptions.
  3. Identify mismatches, missing pieces, or risky defaults.
  4. Separate release-blocking config risk from lower-priority cleanup.
  5. Recommend the smallest useful fixes or checks.
  6. Call out what should be documented or reverified.

Output

For non-trivial work, provide:

  • environments reviewed
  • config surfaces reviewed
  • parity or drift risks
  • release blockers vs lower-priority issues
  • recommended next checks or fixes

Coordination

After config audit:

  • use release-rollout-strategy if rollout depends on flags or staged config
  • use ship-readiness if config parity is the final blocker
  • use docs-writer if setup or migration docs need to be updated

Invocation Examples

  • "Use environment-config-audit before release to compare local, staging, and prod assumptions."
  • "Use environment-config-audit to check whether secrets, flags, and defaults are wired consistently."
  • "Use environment-config-audit because this smells like config drift, not a code bug."

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.