
ln-115-devops-docs-creator
Creates infrastructure.md and runbook.md (Docker-conditional). Use for DevOps documentation in any project.
- Installs
- 384
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-115-devops-docs-creator- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads ln-115-devops-docs-creator automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Paths: File paths (
references/,../ln-*) are relative to this skill directory.
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 directoryflags: { hasDocker }
MANDATORY READ: Load references/docs_quality_contract.md, and references/markdown_read_protocol.md.
Optional rule catalog: load references/docs_quality_rules.json only when exact rule IDs, path matrices, or allowlisted placeholder exceptions are needed.
Documents Created (2: 1 always + 1 conditional)
| File | Condition | Questions | Auto-Discovery |
|---|---|---|---|
| docs/project/infrastructure.md | Always | Q52-Q55 | Medium |
| docs/project/runbook.md | hasDocker | Q46-Q51 | High |
Workflow
Phase 1: Check Conditions
- Parse flags from coordinator
- infrastructure.md: ALWAYS proceeds (no condition check)
- runbook.md: Create ONLY if
hasDocker=true - If target file already exists: skip that file (idempotent)
Phase 2a: Create infrastructure.md (unconditional)
- Check if
docs/project/infrastructure.mdexists - If exists: skip with log
- 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: ...]
- Copy
- 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)
- If no CI/CD detected: replace with concise empty-state note, not
Phase 2b: Create runbook.md (conditional)
- If
!hasDocker: skip entirely - Check if
docs/project/runbook.mdexists - If exists: skip with log
- 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: ...]
- Copy
- 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:
- Check SCOPE tag and metadata markers
- Check required top sections (
Quick Navigation,Agent Entry,Maintenance) - Validate sections: Server Inventory, Port Allocation, Deployed Services
- Check no procedural content leaked (belongs in runbook.md)
- Check docs-quality contract compliance (no forbidden placeholders, no leaked template metadata, valid doc kind/role)
For runbook.md (if created):
- Check SCOPE tag and metadata markers
- Check required top sections (
Quick Navigation,Agent Entry,Maintenance) - Validate sections: Local Development Setup, Deployment, Troubleshooting
- Check env vars documented
- 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 references/docs_generation_summary_contract.md
Accept optional summaryArtifactPath.
Summary kind:
docs-generation
Required payload semantics:
worker = "ln-115"statuscreated_filesskipped_filesquality_inputsvalidation_statuswarnings
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
FAQ
What does the ln-115-devops-docs-creator skill do?
Creates infrastructure.md and runbook.md (Docker-conditional). Use for DevOps documentation in any project.
How do I install ln-115-devops-docs-creator?
Run npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-115-devops-docs-creator in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/ln-115-devops-docs-creator/ (personal) or .claude/skills/ln-115-devops-docs-creator/ (project).
Which AI agents can use ln-115-devops-docs-creator?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is ln-115-devops-docs-creator safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains ln-115-devops-docs-creator?
It is published by levnikolaevich in levnikolaevich/claude-code-skills. It has 384 recorded installs.
More from levnikolaevich/claude-code-skills
ln-100-documents-pipeline
levnikolaevich/claude-code-skills
Creates complete project documentation system (project docs, reference, tasks, tests). Use when bootstrapping docs from scratch or regenerating all.
ln-620-codebase-auditor
levnikolaevich/claude-code-skills
Use when auditing the codebase through the evaluation platform with mandatory research, coordinated domain audit workers, and structured summaries.
ln-775-api-docs-generator
levnikolaevich/claude-code-skills
Configures Swagger/OpenAPI documentation for backend APIs. Use when adding interactive API docs to a project.
ln-624-code-quality-auditor
levnikolaevich/claude-code-skills
Checks cyclomatic complexity, nesting, long methods, god classes, O(n2), N+1 queries, constants management. Use when auditing code quality.
ln-782-test-runner
levnikolaevich/claude-code-skills
Executes all test suites and reports results with coverage. Use when verifying that test infrastructure works after bootstrap.
ln-634-test-coverage-auditor
levnikolaevich/claude-code-skills
Open the skill to read its SKILL.md instructions.
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.