Token导航 LogoToken导航TokenDH.com
研究检索external-servicegithub未标认证来源可访问clear审计提醒

ln-115-devops-docs-creatorln 115 devops 文档创建者

Agent Skill

用于辅助云资源、部署、容器、基础设施和运维自动化任务。它适合让 Agent 检查配置、整理部署步骤、分析资源状态、生成排障思路或辅助云服务接入。使用时需要明确目标环境、账号权限、区域和资源组,区分本地测试与生产操作;涉及删除资源、重启服务、修改网络或权限配置时,应先确认影响范围。

总安装

6,634

周安装

271

GitHub Stars

437

下载量

2,125
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:ln-115-devops-docs-creator(ln 115 devops 文档创建者)
来源仓库:https://github.com/levnikolaevich/claude-code-skills
仓库路径:skills/ln-115-devops-docs-creator
安装命令:
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-115-devops-docs-creator
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-115-devops-docs-creator

简介

用于辅助云资源、部署和运维自动化任务。

  • 适合检查配置、整理部署步骤、ln-115-devops-docs-creator 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 分析资源状态或生成排障思路。
  • 使用时需要明确目标环境、账号权限和操作边界;
  • 涉及删除资源或修改网络配置时应先确认影响范围。

SKILL.md

Paths: File paths (shared/, references/, ../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root. If shared/ is missing, fetch files via WebFetch from https://raw.githubusercontent.com/levnikolaevich/claude-code-skills/master/skills/{path}.

DevOps Documentation Creator

Type: L3 Worker

L3 Worker that creates infrastructure.md and runbook.md. Infrastructure inventory is always created; runbook is conditional on Docker presence.

Purpose & Scope

  • Creates infrastructure.md (always) — declarative inventory: WHAT is deployed WHERE
  • Creates runbook.md (if hasDocker) — procedural guide: HOW to deploy/restart/troubleshoot
  • Receives Context Store from ln-110-project-docs-coordinator
  • Never gathers context itself; uses coordinator input

Invocation (who/when)

  • ln-110-project-docs-coordinator: ALWAYS invoked (infrastructure.md is unconditional)
  • Never called directly by users

Inputs

From coordinator:

  • contextStore: Context Store with DevOps-specific data

- DOCKER_COMPOSE_DEV (development setup) - DOCKER_COMPOSE_PROD (production setup) - ENV_VARIABLES (from.env.example) - STARTUP_SEQUENCE (services order) - DEPLOYMENT_TARGET (AWS, Vercel, Heroku) - CI_CD_PIPELINE (from.github/workflows) - DOCKER_SERVICES (parsed from docker-compose.yml services) - DEPLOYMENT_SCALE ("single" | "multi" | "auto-scaling" | "gpu-based") - DEVOPS_CONTACTS (from CODEOWNERS, package.json author, git log) - HAS_GPU (detected from docker-compose nvidia runtime) - SERVER_INVENTORY (from SSH config, deploy targets) - DOMAIN_DNS (from docker-compose VIRTUAL_HOST vars, nginx configs) - ARTIFACT_REPOSITORY (from.env registry URLs,.npmrc, pip.conf) - HOST_REQUIREMENTS (from docker-compose deploy.resources.limits)

  • targetDir: Project root directory
  • flags: {hasDocker}

MANDATORY READ: Load shared/references/docs_quality_contract.md, shared/references/docs_quality_rules.json, and shared/references/markdown_read_protocol.md.

Documents Created (2: 1 always + 1 conditional)

FileConditionQuestionsAuto-Discovery
docs/project/infrastructure.mdAlwaysQ52-Q55Medium
docs/project/runbook.mdhasDockerQ46-Q51High

Workflow

Phase 1: Check Conditions

  1. Parse flags from coordinator
  2. infrastructure.md: ALWAYS proceeds (no condition check)
  3. runbook.md: Create ONLY if hasDocker=true
  4. If target file already exists: skip that file (idempotent)

Phase 2a: Create infrastructure.md (unconditional)

  1. Check if docs/project/infrastructure.md exists
  2. If exists: skip with log
  3. If not exists:

- Copy references/templates/infrastructure_template.md - Replace placeholders with Context Store values - Preserve the shared opening contract and standard top sections from the template - Populate Server Inventory from SERVER_INVENTORY - Populate Port Allocation from DOCKER_SERVICES port mappings - Populate Deployed Services from DOCKER_SERVICES - Populate CI/CD Pipeline from CI_CD_PIPELINE - Never leave template markers in published infrastructure docs - If data is missing: omit the claim or use a concise neutral fallback, but do NOT emit [TBD:...]

  1. Conditional Section Pruning:

- If no CI/CD detected: replace with concise empty-state note, not [TBD:...] - If no ARTIFACT_REPOSITORY: replace with concise empty-state note, not [TBD:...] - If single server / no SERVER_INVENTORY: simplify to single-column table - If!HAS_GPU: remove GPU column from Server Inventory and Deployed Services - Populate Deployed Services ONLY from DOCKER_SERVICES (no generic examples)

Phase 2b: Create runbook.md (conditional)

  1. If !hasDocker: skip entirely
  2. Check if docs/project/runbook.md exists
  3. If exists: skip with log
  4. If not exists:

- Copy references/templates/runbook_template.md - Replace placeholders with Context Store values - Preserve the shared opening contract and standard top sections from the template - Populate setup steps from package.json scripts - Extract env vars from.env.example - Never leave template markers in published runbooks - If data is missing: omit the claim or use a concise neutral fallback, but do NOT emit [TBD:...]

  1. Conditional Section Pruning:

- If DEPLOYMENT_SCALE!= "multi" or "auto-scaling": Remove scaling/load balancer sections - If!HAS_GPU: Remove GPU-related sections (nvidia runtime, CUDA) - If service not in DOCKER_SERVICES: Remove that service's examples - If DEVOPS_CONTACTS empty: replace with concise empty-state note, not [TBD:...] - Populate service dependencies ONLY from DOCKER_SERVICES - Populate port mapping ONLY from docker-compose.yml ports section

Phase 3: Self-Validate

For infrastructure.md:

  1. Check SCOPE tag and metadata markers
  2. Check required top sections (Quick Navigation, Agent Entry, Maintenance)
  3. Validate sections: Server Inventory, Port Allocation, Deployed Services
  4. Check no procedural content leaked (belongs in runbook.md)
  5. Check docs-quality contract compliance (no forbidden placeholders, no leaked template metadata, valid doc kind/role)

For runbook.md (if created):

  1. Check SCOPE tag and metadata markers
  2. Check required top sections (Quick Navigation, Agent Entry, Maintenance)
  3. Validate sections: Local Development Setup, Deployment, Troubleshooting
  4. Check env vars documented
  5. Check docs-quality contract compliance (no forbidden placeholders, no leaked template metadata, valid doc kind/role)

Phase 4: Return Status

{
  "created_files": ["docs/project/infrastructure.md", "docs/project/runbook.md"],
  "skipped_files": [],
  "quality_inputs": {
    "doc_paths": ["docs/project/infrastructure.md", "docs/project/runbook.md"],
    "owners": {
      "docs/project/infrastructure.md": "ln-115-devops-docs-creator",
      "docs/project/runbook.md": "ln-115-devops-docs-creator"
    }
  },
  "validation_status": "passed"
}

Critical Notes

Core Rules

  • infrastructure.md: Always created, no condition
  • runbook.md: Conditional on hasDocker
  • Heavy auto-discovery: Most data from docker-compose.yml,.env.example, package.json, SSH config
  • Reproducible: Setup steps must be testable and repeatable
  • Idempotent: Never overwrite existing files
  • Publishable output: No [TBD:...], TODO, or leaked template metadata in DevOps docs

NO_CODE_EXAMPLES Rule (MANDATORY)

Both documents describe inventory/procedures, NOT implementations:

  • FORBIDDEN: Full Docker configs, CI/CD pipelines (>5 lines), full nginx configs
  • ALLOWED: Command examples (1-3 lines), env var tables, step lists, verification commands
  • INSTEAD OF CODE: "See docker-compose.yml"

Stack Adaptation Rule (MANDATORY)

  • Commands must match project stack (npm vs pip vs go)
  • Link to correct cloud provider docs (AWS/Azure/GCP)
  • Never mix stack references (no npm commands in Python project)

Format Priority (MANDATORY)

Tables (env vars, ports, services, servers) > Lists (setup steps) > Text

Runtime Summary Artifact

MANDATORY READ: Load shared/references/docs_generation_summary_contract.md

Accept optional summaryArtifactPath.

Summary kind:

  • docs-generation

Required payload semantics:

  • worker = "ln-115"
  • status
  • created_files
  • skipped_files
  • quality_inputs
  • validation_status
  • warnings

Write the summary to the provided artifact path or return the same envelope in structured output.

Definition of Done

  • infrastructure.md created (always)
  • runbook.md created if hasDocker
  • Infrastructure: server inventory, ports, services documented
  • Runbook: setup steps, deployment, troubleshooting documented
  • All env vars from.env.example included in runbook
  • Actuality verified: all document facts match current code (paths, functions, APIs, configs exist and are accurate)
  • Status returned

Reference Files

  • Templates: references/templates/infrastructure_template.md, references/templates/runbook_template.md
  • Questions: references/questions_devops.md (Q46-Q51 runbook, Q52-Q55 infrastructure)

Version: 2.0.0 Last Updated: 2025-01-12

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

27.83%
按下载量换算591

Gemini CLI

22.6%
按下载量换算480

OpenCode

17.19%
按下载量换算365

Antigravity

12.79%
按下载量换算272

Codex

8.45%
按下载量换算180

Cursor

3.88%
按下载量换算82

安全审计

Gen Agent Trust Hub

可疑

Socket

通过

Snyk

可疑

权限和风险

external-service

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。

来源信息

继续浏览同类 Skills