agentleFS
Sign inStart free
XakkiXakki/ai-agents-skills/skills/code-config-audit/SKILL.md

code-config-audit

Skill6 starsChanged 3 months agoMITView on GitHub

Trace configuration, defaults, generated catalogs, startup wiring and readiness across services and environments. Use when implementing or reviewing configuration. RU: конфигурация, настройки, готовность сервиса.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Use when implementing or reviewing configuration, defaults, generated catalogs, process wiring or readiness.

    line 9
  2. Distinctive:

    Use configuration and rollout verification for defaults, configuration formats and generated artifacts, and startup and readiness for …

    line 13

≈ “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

Configuration contracts

Use when implementing or reviewing configuration, defaults, generated catalogs, process wiring or readiness. Establish the exact requested change and whether the task permits mutation; a read-only review does not authorize restart, build, deployment or secret access.

Trace each relevant key from its authoritative source and precedence through parsing, overrides, serialization, generated projections, startup guard and actual consumers. Distinguish absent, explicitly empty, invalid, disabled and false values according to the documented contract. Keep saved configuration, effective settings and already-running or persisted process state separate. Preserve unrelated credentials without opening, printing or exporting them.

Use configuration and rollout verification for defaults, configuration formats and generated artifacts, and startup and readiness for credential-gated endpoints and cross-process state. Report exact evidence, observed runtime scope and reload requirements; static validation alone does not prove an activated service.

For registries and published catalogs, read registry and catalog consistency.

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