configuration-audit
Skill1 starsChanged 4 months agoMITView on GitHub
Explicit-invocation audit of configuration sources, precedence, overrides, defaults, validation, drift, dangerous settings, undocumented variables, and credential-commit risk using repository evidence. Do not trigger for one settled config edit, read sensitive values, connect to external environments, or modify configuration. 仅显式调用:基于仓库证据审计配置来源、优先级、覆盖、默认值、校验、漂移、危险设置、未文档化变量和凭据误提交风险。不得因一个已确定配置修改而触发,不读取敏感值、不连接外部环境,也不修改配置。
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 10
Default to standard; explicit invocation is required.
- Distinctive: line 21
Never read, print, store, or request credential values, personal data, or private configuration contents.
- Distinctive: line 22
Do not connect to external environments.
- Distinctive: line 28
Check drift, obsolete keys, conflicting defaults, unsafe fail-open behavior, undocumented variables, inconsistent names/types, committed …
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
English
Execution Contract
Default to standard; explicit invocation is required.
Complete one primary task by default. Continue an authorized end-to-end workflow within each Skill's permissions; Router remains recommendation-only. Pause for new material decisions or scope, not authorization already given.
For a human-only blocker, give location, action, success signal and resume step; never request secret values or assume completion.
Validate according to actual risk; security, production, migrations, releases and other high-risk work use audit. Read references/execution-modes.en.md only when mode selection is unclear.
Configuration Audit
Audit a defined configuration surface from repository evidence. Keep configuration and external environments unchanged.
Boundary
- Route broad repository health to
project-health-check, generic change impact tochange-impact-analysis, and edits tosafe-fix-implementation. - Never read, print, store, or request credential values, personal data, or private configuration contents. Report variable names, file locations, and validation behavior only.
- Do not connect to external environments. Treat environment state supplied by the user as unverified unless evidence supports it.
Workflow
- Inventory configuration sources: files, environment variables, flags, remote references, defaults, generated config, and runtime overrides.
- Establish precedence, merge behavior, environment selection, requiredness, types, parsing, validation, fallback, reload, and failure behavior.
- Build a development/test/staging/production matrix using names and evidence only; mark unavailable environments unknown.
- Check drift, obsolete keys, conflicting defaults, unsafe fail-open behavior, undocumented variables, inconsistent names/types, committed sensitive-file patterns, and missing validation.
- Trace configuration to consumers, startup behavior, deployment templates, tests, and documentation.
- Report evidence, severity/priority, impact, confidence, recommendations, validation, and unknowns without showing values or editing config.
Output Contract
- Scope and configuration source/precedence map
- Evidence
- Environment matrix without sensitive values
- Findings with severity, impact, confidence, and affected consumers
- Recommendations and validation
- Undocumented, obsolete, or dangerous settings
- Unknowns
简体中文
执行契约
默认使用 standard;仅允许用户显式调用。
默认完成一个主任务。用户已授权完整流程时,在各 Skill 权限内连续完成;Router 仍只推荐。新重大决策或超出授权时暂停,不重复索取已有授权。
必须由用户完成的阻塞步骤:给出操作位置、具体动作、成功标志、恢复步骤;不要求粘贴秘密值,不代替用户确认完成。
按实际风险选择验证;安全、生产、迁移、发布等高风险工作使用 audit。模式不明确时才读取 references/execution-modes.zh-CN.md。
配置审计
基于仓库证据审计一个明确配置表面,保持配置和外部环境不变。
职责边界
- 广泛项目健康交给
project-health-check,通用影响交给change-impact-analysis,修改交给safe-fix-implementation。 - 不读取、输出、记录或索取凭证值、个人数据和私有配置内容,只报告变量名称、文件位置和校验行为。
- 不连接外部环境;用户提供的环境状态在没有证据时标为未验证。
工作流程
- 盘点配置来源:文件、环境变量、flag、远程引用、默认值、生成配置和运行时覆盖。
- 明确优先级、合并行为、环境选择、必填、类型、解析、校验、fallback、重载和失败行为。
- 仅使用名称和证据建立开发/测试/预发/生产矩阵;不可用环境标为未知。
- 检查漂移、过期键、冲突默认值、危险 fail-open、未文档化变量、名称/类型不一致、敏感文件误提交模式和缺失校验。
- 将配置追踪到消费者、启动行为、部署模板、测试和文档。
- 不显示值或修改配置,报告证据、严重度/优先级、影响、置信度、建议、验证和未知项。
输出契约
- 范围与配置来源/优先级映射
- 证据
- 不含敏感值的环境矩阵
- 发现、严重度、影响、置信度和受影响消费者
- 建议与验证
- 未文档化、过期或危险配置
- 未知项
In this repository40 other files it gives its agents.
- api-contract-reviewSkill
- architecture-decision-recordSkill
- architecture-deepening-analysisSkill
- bug-root-cause-analysisSkill
- change-impact-analysisSkill
- ci-failure-diagnosisSkill
- content-consistency-checkSkill
- database-migration-reviewSkill
- dead-code-verificationSkill
- decision-prototypeSkill
- dependency-upgrade-analysisSkill
- documentation-syncSkill
- document-reviewSkill
- excel-data-quality-check-basicSkill
- feature-implementationSkill
- meeting-notes-to-actionsSkill
- pdf-review-basicSkill
- pdf-reviewSkill
- performance-regression-analysisSkill
- presentation-outlineSkill
- project-health-checkSkill
- release-readiness-checkSkill
- repo-doctor-routerSkill
- repo-onboardingSkill
- report-writerSkill
- requirements-clarificationSkill
- requirements-to-specSkill
- research-briefSkill
- safe-change-planSkill
- safe-code-reviewSkill
- safe-fix-implementationSkill
- safe-test-implementationSkill
- security-focused-reviewSkill
- session-handoffSkill
- skill-authoringSkill
- skill-quality-auditSkill
- spec-to-work-itemsSkill
- spreadsheet-data-cleaningSkill
- test-gap-analysisSkill
- word-document-review-basicSkill
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.

