agentleFS
Sign inStart free
ByronScottJonesByronScottJones/Agents/skills/review-configuration/SKILL.md

review-configuration

Skill7 starsChanged 2 months agoMITView on GitHub

Use when auditing application configuration for secret exposure, precedence conflicts, missing validation, undocumented defaults, environment drift, or unsafe public variables. Produces a report and does not modify configuration by default.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check schema validation and startup failure behavior.

    line 28
  2. Distinctive:

    Never print secret values.

    line 33
  3. Distinctive:

    Do not load production secrets into the agent context.

    line 34
  4. Distinctive:

    Do not change precedence or defaults without identifying compatibility impact.

    line 35
  5. Distinctive:

    Treat browser-exposed variables as public.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Review Configuration

Audit configuration against configuration.md, platform guidance, and project conventions.

Parameters

  • projectPath: project root; default workspace root.
  • scope: files, environment variables, deployment configuration, or all; default all.
  • environment: optional target environment.
  • checkSecrets, checkPrecedence, checkSchemas, checkPublicVariables: default true.
  • fix: default false.
  • format: summary or json; default summary.

Workflow

  1. Discover config files, environment examples, schemas, deployment manifests, and code paths that load settings.
  2. Detect secrets, credentials, unsafe defaults, missing types, undocumented variables, precedence conflicts, and client-exposed sensitive values.
  3. Compare development, staging, and production configuration expectations.
  4. Check schema validation and startup failure behavior.
  5. In fix mode, propose narrowly scoped documentation or configuration changes.

Safety

  • Never print secret values; report only names and locations.
  • Do not load production secrets into the agent context.
  • Do not change precedence or defaults without identifying compatibility impact.
  • Treat browser-exposed variables as public.

Output

Return files and variables reviewed, findings by severity, secret locations with values redacted, precedence issues, missing documentation, and remediation steps.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free