agentleFS
jhutchison0jhutchison0/tacsop/.claude/skills/configuration-management/SKILL.md

configuration-management

Skill0 starsChanged 25 days agoApache-2.0View on GitHub

Hierarchical YAML configuration systems with profiles, secrets management, environment-based overrides, schema validation, and testing. Use when setting up config systems, managing secrets, switching environments, refactoring hardcoded values, or auditing configuration architecture.

  • Reads credentials

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Hardcoded secrets in YAML: Always ${API_KEY} from environment.

    line 71

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

Externalize application behavior into structured, version-controlled files that can be changed without code modifications. This SKILL.md is the entry point; deep procedural content lives in sidecar files loaded on demand.

Philosophy: "Configuration is code. Version it, test it, document it, and never commit secrets."

When to Use

  • Setting up a configuration system for a new project
  • Managing secrets without committing them
  • Adding profile-based environments (dev / test / staging / production)
  • Refactoring hardcoded values out of code
  • Auditing an existing config system for security or maintainability issues
  • Designing config validation that catches misconfiguration at startup

Core Principles

Four rules that govern everything else in this skill:

  1. Hierarchical, layered, last-wins. Defaults at the base, environment overrides on top, secrets last via environment variables.
  2. Secrets never in config files. .env (gitignored) for secrets; .env.example (committed) as the template. No exceptions.
  3. Validate at startup. A config error at app launch is recoverable; a config error in production at 3am is not. See VALIDATION.md.
  4. Test configs like code. Override-able for tests; loading and merging behavior covered by tests; secrets never logged.

Quick Reference

Priority Order (last wins)

1. default.yaml          (system-wide defaults)
2. components/*.yaml     (component-specific settings)
3. profiles/{mode}.yaml  (environment overrides)
4. Environment variables (secrets and local overrides)
5. Programmatic overrides (testing only)

Common Operations

TaskPattern
Load configconfig = ConfigLoader.load(profile='development')
Override for testingconfig = ConfigLoader.load(overrides={'debug': True})
Access nested valuevalue = config['component']['subsystem']['setting']
Set profile via env varexport PROJECT_CONFIG_PROFILE=production
Validate against schemaSee VALIDATION.md

Environment Variable Syntax in YAML

  • ${VAR} — required (error if not set)
  • ${VAR:default} — optional, defaults to literal value
  • ${VAR:} — optional, defaults to empty string

Sidecar Files

Loaded on demand when this SKILL.md cites them.

  • STRUCTURE-AND-FILES.md — directory layout, what gets committed vs ignored, the four file types (default, component, profile, .env) with worked examples.
  • LOADER.md — Python ConfigLoader implementation, deep-merge logic, env-var expansion, usage examples.
  • SECRETS.md — .env management, .gitignore patterns, secret rotation workflow, production secret stores.
  • VALIDATION.md — Pydantic schemas, runtime validation, the configuration audit checklist.
  • TESTING-AND-PATTERNS.md — testing the loader and overrides; common patterns (feature flags, environment detection, graceful degradation, YAML anchors); troubleshooting.

Quick Anti-Pattern Reference

  • Hardcoded secrets in YAML. Always ${API_KEY} from environment.
  • Logging the whole config dict. Secrets leak. See SECRETS.md for sanitization.
  • One giant config.yaml. Split by component; merge hierarchically. See STRUCTURE-AND-FILES.md.
  • Production debug endpoints. Profile-gate them: false in default.yaml, false in profiles/production.yaml, never overridden.
  • Auto-migrate in production. database.migrations.auto_migrate must be false in production. Surprising data loss when this is wrong.

References

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.