agent-configlisted

Set up, repair, or relocate the settings and credentials a skill, subagent, command, or hook depends on — layered `.agents/config` files plus credential *references* (1Password, environment variable, dotenv, macOS Keychain, any shell command) that keep secrets out of git. Use when a component reports missing or incomplete configuration, when its credential won't resolve, when the user asks where an API key or setting is stored or wants to move one between the global, repo, and local layers, and when a skill author is adding configuration to a new skill or subagent. Other skills invoke this instead of restating any of it.
Max-Levitskiy/skills · ★ 0 · AI & Automation · score 66

Install: claude install-skill Max-Levitskiy/skills

# Agent Config (ACS v1) The rules live in [`standards/agent-config.md`](../../../../standards/agent-config.md) — precedence, merge semantics, every credential shape, the full checklist. This skill makes them actionable and deliberately does not repeat them; read the standard when something here doesn't answer the question. Two jobs arrive here: a user needs configuring → [Onboarding](#onboarding); a skill needs config wired into it → [Wiring config into a component](#wiring-config-into-a-component). ## The shape Three layers, later overrides earlier: | layer | path | committed | | --- | --- | --- | | global | `~/.agents/config/<name>/config.json` | outside the repo | | repo | `<repo>/.agents/config/<name>/config.json` | **yes** | | local | `<repo>/.agents/config/<name>/config.local.json` | **no — gitignored** | `<name>` is the plugin name: one namespace, so a plugin's skill and its subagent read the same file instead of asking the user the same questions twice. `version` and `credentials` are reserved; every other key belongs to the component. Outside a git repo only the global layer exists, and a component must still work there. ## Onboarding Missing config is the expected first-run state, not a failure — never report it to the user as an error. It is re-runnable: changing an answer means writing the layer again, not hand-editing JSON. 1. **Detect before doing any work.** Run the calling skill's config check — `fellow.ts config check`, `orchestrate-config.ts check`.