Skip to content
Back to skills

Review Configuration

ASecurity

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.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 17, 2026
ai-agentsdocumentation

Works with

  • cli

Security analysis

A100/100

Scanned October 17, 2026

npx -y skills add ByronScottJones/Agents --skill review-configuration --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Review Configuration?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Review Configuration
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/byronscottjones-review-configuration/badge)](https://www.skillsdirectory.com/skills/byronscottjones-review-configuration)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: review-configuration
user-invocable: false
description: "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."
---

# 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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.