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
- dbtinoy-/lexigram-framework-skillstheir own version, first seen Aug 24, 2026
- saitarrun/Devforge-aitheir own version, first seen Jun 20, 2026
- ffsshhttiikk/opencode-agents-skillstheir own version, first seen Feb 28, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- saitarrun/Devforge-ai★ 4same name
- ffsshhttiikk/opencode-agents-skills★ 2same name
- dbtinoy-/lexigram-framework-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- designing-clear-data-displaysSkill
- lake-conventionsSkill
- maintaining-project-contextSkill
- maintaining-the-common-operating-pictureSkill
- maintaining-ubiquitous-languageSkill
- python-venv-managementSkill
- recording-architecture-decisionsSkill
- shift-left-testingSkill
- traversing-the-knowledge-baseSkill
- using-topic-branchesSkill
- verifying-claimsSkill
- writing-simple-and-directSkill
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
- Very specific: line 71
Hardcoded secrets in YAML: Always ${API_KEY} from environment.
≈ “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.
Files
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:
- Hierarchical, layered, last-wins. Defaults at the base, environment overrides on top, secrets last via environment variables.
- Secrets never in config files.
.env(gitignored) for secrets;.env.example(committed) as the template. No exceptions. - Validate at startup. A config error at app launch is recoverable; a config error in production at 3am is not. See
VALIDATION.md. - 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
| Task | Pattern |
| Load config | config = ConfigLoader.load(profile='development') |
| Override for testing | config = ConfigLoader.load(overrides={'debug': True}) |
| Access nested value | value = config['component']['subsystem']['setting'] |
| Set profile via env var | export PROJECT_CONFIG_PROFILE=production |
| Validate against schema | See 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
ConfigLoaderimplementation, deep-merge logic, env-var expansion, usage examples. - SECRETS.md —
.envmanagement,.gitignorepatterns, 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.mdfor sanitization. - One giant
config.yaml. Split by component; merge hierarchically. SeeSTRUCTURE-AND-FILES.md. - Production debug endpoints. Profile-gate them: false in
default.yaml, false inprofiles/production.yaml, never overridden. - Auto-migrate in production.
database.migrations.auto_migratemust befalsein production. Surprising data loss when this is wrong.
References
- 12-Factor App: Config — the foundational pattern this skill implements.
- Pydantic — schema validation, used in
VALIDATION.md. - python-dotenv —
.envfile loading, used inLOADER.md. - YAML Specification — YAML reference (including anchors used in
TESTING-AND-PATTERNS.md).
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
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.

