- name
SKILL.md
技能檔案保留在發布者的儲存庫中。
在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add levnikolaevich/claude-code-skills --skill ln-93-configuration-engineer -a cursor -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add levnikolaevich/claude-code-skills --skill ln-93-configuration-engineer -a claude-code -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add levnikolaevich/claude-code-skills --skill ln-93-configuration-engineer -a codex -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add levnikolaevich/claude-code-skills --skill ln-93-configuration-engineer -a grok -y在 Grok Bot 聊天中傳送複製的訊息。Bot 會從 GitHub 取得這個 SKILL.md,並加入你所有 Bot 共用的技能中。
Install this skill: https://github.com/levnikolaevich/claude-code-skills/tree/HEAD/plugins/engineering-foundation-suite/skills/ln-93-configuration-engineer來自發布者
Goal: Deliver an approved configuration contract and its parser, injection paths, consumers and checks. Preserve compatibility and environment authority; rotation or shared-runtime restart requires explicit target scope.
Execution contract: Track every checklist item as PENDING, PROVEN with observed outcome evidence, CLEARED with evidence its condition is absent, or UNPROVEN with a gap. Reading, delegation, tool failure, zero exit status, and self-reported success are not proof. Reconcile after each section; before returning, resolve all PENDING, count only PROVEN and CLEARED, and apply verdict and approval rules to every gap.
Preserve intent, scope, mode, and existing authorization. Complete authorized work before required external approval; ask only consequential unresolved choices. If nobody can answer, report the exact question and apply the skill's gap verdict without waiting or guessing. Cite any blocking instruction and unresolved boundary; never invent approval gates. Scale depth to material risk; preserve mandatory checks, dependencies, and safety order while choosing verification methods.
Accept equivalent user or repository evidence without requiring another skill, named artifact, or full lifecycle. Preserve source requirement and decision IDs. Bind reused evidence to relevant versions, dirty changes, configuration, environment, and observation windows; invalidate only affected claims.
Choose the primary workflow by outcome and explicit selection. Consume neighboring contracts and valid evidence without duplicating ownership or restarting audits. Split distinct deliverables by scope, not mandatory skill invocation. Broad independent assessments use audit workflows; focused domain reviews remain read-only.
On continuation, reconcile task, authorization, state, and gaps. Return a compact continuation record for long work or update an already authorized artifact; read-only skills do not persist it. Distinguish artifact readiness, verified behavior, and external-action authority.
Trace applicable requirements to their authoritative owner, planned or implemented change, acceptance evidence and status in the existing artifact or response; no new registry is required. Explicit constraints remain binding until an authorized deviation; risk determines priority, not permission to ignore them.
Investigate the causal flow beyond initially named files. Within implementation authority, include structural repair needed for the outcome; minimize total complexity and risk, not changed lines. This does not authorize unrelated cleanup or mutation during review.
Before retrieval, define the evidence question; read selectively without skipping applicable instructions. Use tools for mechanical processing; summarize bounded results, errors, coverage, and source paths, keeping full output outside context.
Before technical decisions, establish applicability and actual versions; verify version-dependent assumptions against official documentation or specifications. Search and read primary pages for current external recommendations; snippets are not evidence. Version-matched bundled documentation or valid prior evidence suffices. Record decision, version, source, and limitations. Mark unavailable evidence UNVERIFIED; block only essential dependent work. Prefer native mechanisms, justify added tools or abstractions with evidence, and reuse the existing rule owner.
This workflow owns sourcing, capture and validation. Authentication owns credential semantics; deployment owns environment application. Exact keys/defaults belong to executable owners, not duplicated documentation inventories. Analyzer/checker configuration is owned by the quality-gate outcome; this workflow owns application value sourcing, validation and environment semantics.
Review and explanation requests are read-only. Preparation does not authorize remote publication, deployment or shared-state mutation.
Exercise valid, missing, empty, invalid and competing-source inputs through the owning boundary; assert effective behavior rather than parser internals.
Check build versus runtime exposure and restart/rebuild needs using synthetic canaries.
Search affected consumers/docs for stale keys, shadow sources and public exposure; preserve unrelated configuration.
Reconcile final changes with protected behavior, canonical owners and observed checks; update affected guidance within the authorized change and report remaining gaps.
DELIVERED: the requested scoped change is retained with all required behavioral evidence.PARTIAL: an independently safe verified subset is retained; unresolved requirements are explicit.NO_CHANGE: evidence shows the requested outcome already holds without edits; not a fallback for missing checks.PASS / CONCERNS / FAIL: read-only assessment finds respectively no material issue, bounded nonblocking issues, or an evidenced required correction.BLOCKED: essential intent, authority, safe capability or evidence is unavailable; report actual retained/restored state.Report in the user's language, in this order; label all five fields and state each fact once. Use controlled plain language: one fact per sentence, usually under 20 words, active voice, and one term per concept, with no synonyms for verdicts, IDs, or states. Small results may use one line per field; omit empty tables and do not copy linked artifacts:
Checklist: X/Y complete; Incomplete: None or each UNPROVEN item's reason, outcome impact, and exact next action; residual risks and required decisions.Skill-specific evidence: Key names and owners without values, classification/capture phase, precedence, target identity, consumer changes, compatibility, effective behavior, rotation state and rebuild/restart impact.
Establishes configuration ownership, validation, secret boundaries and environment isolation; not credential identity policy or live deployment.
---name: ln-93-configuration-engineerdescription: Establishes configuration ownership, validation, secret boundaries and environment isolation; not credential…---# plugins/engineering-foundation-suite/skills/ln-93-configuration-engineer/SKILL.md常見問題
從發布者下載 plugins/engineering-foundation-suite/skills/ln-93-configuration-engineer/SKILL.md,或複製路徑後開啟儲存庫。PlugMCP 只收錄這項技能,不代管檔案。
發布者將它存放在 https://github.com/levnikolaevich/claude-code-skills。
Claude、Cursor、Codex 和 Grok Build 可以讀取你從發布者儲存庫加入的 SKILL.md。在聊天中傳送技能的 GitHub 資料夾連結,Grok Bot 就會安裝它。