- name
SKILL.md
技能文件保留在发布者的仓库中。
在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add levnikolaevich/claude-code-skills --skill ln-92-container-engineer -a cursor -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add levnikolaevich/claude-code-skills --skill ln-92-container-engineer -a claude-code -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add levnikolaevich/claude-code-skills --skill ln-92-container-engineer -a codex -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add levnikolaevich/claude-code-skills --skill ln-92-container-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-92-container-engineer来自发布者
Goal: Deliver approved container build and local runtime packaging changes with executable evidence. Limit edits to packaging, necessary scoped lifecycle integration and related checks/guidance. Publishing images, deploying and changing shared hosts require separate authority.
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.
Packaging owns image contents, process lifecycle and local composition. Deployment owns remote topology, rollout and operational health. Configuration owns value semantics; consume its contract instead of adding alternate environment selectors. Docker-specific practices apply only when Docker is selected. Honor accepted digest, checksum and licensing policy; prove clean-input build and real startup on required targets rather than accepting local cache or host tooling as dependencies.
When the primary outcome is a base-image or runtime version upgrade, dependency upgrading owns compatibility and regression evidence. Packaging work may include a necessary compatible image change within its approved scope; it does not authorize a broader dependency upgrade.
Review and explanation requests are read-only. Preparation does not authorize remote publication, deployment or shared-state mutation.
For a source-only review, assess applicable packaging requirements without building or starting containers. Clear execution-only steps as outside the requested scope, disclose unverified runtime behavior, and never describe inferred build/start/stop outcomes as observed. Findings require a concrete defect or applicable requirement; an untested platform assumption is an evidence gap.
Build the actual target image with locked inputs and record identity; lint alone is not build proof.
Start that image in isolation and exercise real entrypoint, required assets/dependencies, health and failure diagnostics.
Observe stop/restart, process exit and persistence; check permissions and absence of synthetic test secrets in image metadata/layers.
Clean only run-owned containers, networks and volumes by verified identity; disclose unavailable runtime/platform evidence.
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: Packaging boundary, platforms and dependency identities, actual build/image identity, startup/health/stop observations, secret/permission checks, cleanup and remaining deployment work.
Builds, hardens or reviews container images and local runtime packaging with startup and shutdown evidence; not remote deployment or host administration.
---name: ln-92-container-engineerdescription: Builds, hardens or reviews container images and local runtime packaging with startup and shutdown evidence…---# plugins/engineering-foundation-suite/skills/ln-92-container-engineer/SKILL.md常见问题
从发布者处下载 plugins/engineering-foundation-suite/skills/ln-92-container-engineer/SKILL.md,或复制路径后打开仓库。PlugMCP 只收录该技能,不托管文件。
发布者将它存放在 https://github.com/levnikolaevich/claude-code-skills。
Claude、Cursor、Codex 和 Grok Build 可以读取你从发布者仓库添加的 SKILL.md。在聊天中发送技能的 GitHub 文件夹链接,Grok Bot 就会安装它。