Agent skill

ln-647-configuration-boundary-auditor

Audits architecture config boundaries: typed settings, scattered env reads, config leakage, and layer ownership. Use for config architecture.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill ln-647-configuration-boundary-auditor --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 7 KB
Bundled scripts: none
Allowed tools: ReadGrepGlobBashmcp__hex-graph__find_symbolsmcp__hex-graph__find_referencesmcp__hex-line__read_filemcp__hex-line__grep_searchmcp__hex-line__outline
Path: skills/analysis/ln-647-configuration-boundary-auditor/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

> **Paths:** File paths (`references/`, `../ln-*`) are relative to this skill directory. # Configuration Boundary Auditor **Type:** L3 Worker Specialized worker auditing whether configuration access has a clear architectural boundary. ## Purpose & Scope - Audit typed settings boundaries, scattered env reads, config leakage across layers, and configuration ownership - Identify architecture problems where code reads raw environment/config directly instead of depending on a settings contract - Emit `ADD_SETTINGS_BOUNDARY`, `STOP_SCATTERED_ENV_READS`, or `TYPE_CONFIG_CONTRACT` - Calculate compliance score (X/10) **Out of Scope:** - `.env` inventory, `.env.example` completeness, committed env files, or secrets hygiene - Package security, build gates, runtime startup validation, and lifecycle readiness - Generating env files or modifying configuration ## Inputs **MANDATORY READ:** Load `references/audit_worker_core_contract.md`. Tool policy: follow host AGENTS.md MCP preferences; load `references/mcp_tool_preferences.md` and `references/mcp_integration_patterns.md` only when host policy is absent or MCP behavior is unclear. Receives `contextStore` with tech stack, codebase root, output_d

What's inside
Steps it walks through
  1. Purpose & Scope
  2. Inputs
  3. Workflow
  4. Audit Rules
  5. 1. Scattered Env Reads
  6. 2. Missing Typed Settings Boundary
  7. 3. Config Ownership Leakage
  8. Scoring Algorithm
  9. Output Format
  10. Critical Rules
  11. Definition of Done
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the ln-647-configuration-boundary-auditor skill do?

Audits architecture config boundaries: typed settings, scattered env reads, config leakage, and layer ownership. Use for config architecture.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill ln-647-configuration-boundary-auditor --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going