← ClaudeAtlas

secrets-architectlisted

Secret-handling standards for one external store consumed by reference — consumer decision matrix (Compose secrets, *_FILE, systemd LoadCredential, plain bind mount, CI), permission/uid rules, naming, migration workflow, live verification, pitfalls. Use when wiring a credential into a repo, container, systemd unit or CI job, migrating secrets out of .env or git, or auditing a secrets store.
ralvarez-ai/ralvaskills · ★ 4 · DevOps & Infrastructure · score 77
Install: claude install-skill ralvarez-ai/ralvaskills
# Secrets Architect **Every credential lives in one secrets store, outside every repo. Consumers read it by reference — never a copied value.** No secret value in git, in a `.env`, or in a container environment. Targets **`$SECRETS_DIR`** (default `~/Secrets`) as the store. The canonical long-form walkthrough — the full narrative, verification log and instance layout — lives in the chezmoi repo's `docs/secrets-methodology.md`; this skill is the portable, agent-facing core. ## 1. Principles - **One store, many consumers.** `$SECRETS_DIR` is the single source of truth; repos reference paths, never values. - **Match the mechanism to the consumer** (see §3). The consumer's shape — file reader, env app, oneshot, shell, writable state, CI — picks the mechanism. - **Paths have a default.** Build from `${SECRETS_DIR:-$HOME/Secrets}` so a stack works without a per-secret variable being defined. - **Least privilege, but respect the reader's uid.** Default `600`, except files a non-root process opens directly. - **Verify against the running system, not just the source.** The deployed artifact can lag the repo. - **Nothing changes without a live check.** Config-render, recreate, and prove the secret was actually used. ## 2. The store: layout and permissions Layout is **by kind, then owner** (`<kind>/<owner>/<name>`): ``` $SECRETS_DIR/ # 0700 ├── cloudflare/ │ ├── api/ddns-token # 0600 API tokens │ ├── tunnels/<tunnel-name> # 0644 tunnel tokens (non-