- name
SKILL.md
Файл навыка остаётся в репозитории издателя.
Вставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add levnikolaevich/claude-code-skills --skill ln-63-deployment-engineer -a cursor -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add levnikolaevich/claude-code-skills --skill ln-63-deployment-engineer -a claude-code -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add levnikolaevich/claude-code-skills --skill ln-63-deployment-engineer -a codex -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add levnikolaevich/claude-code-skills --skill ln-63-deployment-engineer -a grok -yОтправьте скопированное сообщение в чат Grok Bot. Бот загрузит этот SKILL.md с GitHub и добавит его к навыкам, общим для всех ваших ботов.
Install this skill: https://github.com/levnikolaevich/claude-code-skills/tree/HEAD/plugins/delivery-suite/skills/ln-63-deployment-engineerОт издателя
Goal: Prepare and, when authorized, deploy one bounded change through the established delivery platform. Modify only approved CI/CD, IaC, configuration and deployment documentation; external actions remain limited to the named environment and 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.
This workflow owns delivery topology, pipeline triggers, permissions, credentials, environments, artifact publication, remote infrastructure, rollout and observed health. Quality-gate configuration owns check semantics and commands; it may connect them to existing local/CI entrypoints without changing these delivery aspects. Consume those commands instead of duplicating rules in pipelines. Container engineering owns image/local packaging; configuration engineering owns value semantics; database lifecycle owns migration semantics. Consume those existing contracts and evidence without requiring another skill or copying their checklists. Execute only the authorized delivery step; a migration or policy redesign needs its own explicit scope.
Select the delivery mode from the current request and project configuration. Use the established pipeline when authorized. For an authorized manual rollout, including requests to avoid paid CI, read Manual rollout. Manual delivery does not require a push, pipeline run, registry publication or a new deployment platform. Preserve required local verification in either mode.
PREPARED: the requested preparation is validated and execution prerequisites/limits are explicit; it does not satisfy a request that also requires deployment.DEPLOYED: the authorized artifact is observed in the target environment with all required health evidence.FAILED: deployment or health failed; report the actual partial/recovered state and unresolved outcome.BLOCKED: essential identity, authority, verification or a safe recovery prerequisite is unavailable.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: Requested mode, target/account/environment, source and artifact identity, approved diff, validation, rollout operation, health/window evidence, recovery and actual final state; separate readiness from execution.
Prepares delivery pipelines and remote infrastructure, then executes authorized rollouts; not standalone quality-gate setup or local container packaging.
---name: ln-63-deployment-engineerdescription: Prepares delivery pipelines and remote infrastructure, then executes authorized rollouts; not standalone…---# plugins/delivery-suite/skills/ln-63-deployment-engineer/SKILL.mdFAQ
Скачайте plugins/delivery-suite/skills/ln-63-deployment-engineer/SKILL.md у издателя или скопируйте путь и откройте репозиторий. PlugMCP только показывает навык в каталоге и не хранит файл.
Издатель хранит его в https://github.com/levnikolaevich/claude-code-skills.
Claude, Cursor, Codex и Grok Build могут читать SKILL.md, который вы добавляете из репозитория издателя. Grok Bot устанавливает его, когда вы отправляете в чат ссылку на папку навыка на GitHub.