agentsclimarketplace

Config audit checklist

Skill baronguyen001/ai-automation-skills/skills/config-audit-checklist

8 production-tested Claude skills: automation, Gemini cost/structured output, OSS bounty scouting, ML validation.

Install
npx -y skills add baronguyen001/ai-automation-skills --skill config-audit-checklist

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

  • 0 stars0 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

Audit a project for config drift before a backtest or deploy - compare the documented config snapshot against .env and README defaults, flag mismatches, and check the snapshot last-verified date. Use for config audit, params drift, pre-deploy checklist, or production config check.

SKILL.md

1.9 KB, as published. Nobody here has run it

Config Audit Checklist

Use this skill before validating or deploying a project whose behavior depends on documented parameters. It forces the user to reconcile the live environment, the snapshot document, and README defaults before trusting results.

When to invoke

  • User says: "config audit" / "params drift" / "pre-deploy checklist" / "production config check"
  • Code in the conversation uses: .env, README defaults, or a config snapshot document.

When NOT to invoke

  • The project has no config snapshot document yet; recommend creating one first.
  • The project has no externally configurable parameters.

Concrete example

User input:

Audit this strategy config before I run the validation job.

Output:

Auditing strategy config...
  ENTRY_COOLDOWN_HOURS:  README=12   .env=6    CONFIG.md=8     warn: 3-way drift
  STOP_LOSS_PCT:         README=-10  .env=-10  CONFIG.md=-10   ok
  CONFIG.md "Last verified": 2026-03-01 (89 days ago)         warn: stale (>30d)
Verdict: DO NOT backtest against README defaults. Reconcile the live config first.

Pattern to apply

  1. Find the config snapshot document, usually PRODUCTION_CONFIG.md or CONFIG.md.
  2. Read the last verified date and flag stale snapshots.
  3. Extract values from the snapshot, .env, and README defaults.
  4. Report mismatches row by row and name the source of truth.
  5. Refuse to proceed with validation until drift is reconciled.

Reference: assets/checklist.md.

Source

Distilled from production use across the author's automation projects. v0.1.0. See also: [[walk-forward-runner]].

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.