agentleFS
Sign inStart free
MesteriisMesteriis/Engineering-Bible-AI/skills/secrets-and-config-review/SKILL.md

secrets-and-config-review

Skill0 starsChanged 4 months agoMITView on GitHub

Reviews secrets, config defaults, environment variables, logs, credentials, CI secrets, and unsafe settings.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Avoid reading secret values unless the user explicitly scopes break-glass handling and it is safe.

    line 13
  2. Distinctive:

    Check logs, docs, tests, CI, Docker files, and sample env files for leakage.

    line 15
  3. Distinctive:

    Verify defaults, required variables, permissions, and error behavior.

    line 16
  4. Distinctive:

    Never print secret values.

    line 30
  5. Distinctive:

    Do not commit or document credentials.

    line 31
  6. Distinctive:

    Prefer key names, metadata, and redacted evidence.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Secrets And Config Review

Review configuration without exposing secret values.

Workflow

  1. Inspect config keys, file metadata, templates, and redacted examples first.
  2. Avoid reading secret values unless the user explicitly scopes break-glass handling and it is safe.
  3. Check logs, docs, tests, CI, Docker files, and sample env files for leakage.
  4. Verify defaults, required variables, permissions, and error behavior.
  5. Report risks and minimal mitigations.

Output

  • config surfaces reviewed
  • secret exposure risks
  • unsafe defaults
  • logging/documentation risks
  • remediation
  • validation gaps

Rules

  • Never print secret values.
  • Do not commit or document credentials.
  • Prefer key names, metadata, and redacted evidence.

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