Baseline Ops — DevOps skill for Claude Code

Engineering Operations

**Single source of truth for running the applications.** How they are *built* is the [engineering baseline](https://github.com/andygeiss/baseline)'s job; this repository answers three different questions: what is on the server, how an application gets there, and what to do when something breaks.

The split is deliberate. A fact belongs here when it changes only the server, and in the baseline when it changes the code:

Question	Repository
"Does the app log to stdout, and on which port does /healthz live?"	baseline
"Which proxy terminates TLS, and where do its certificates live?"	here

• Last verified: 2026-08-27
• Servers: one — vserver. Everything here is written for it.
• Format: Markdown, plus the templates every application copies and one script the server runs. No application code.

How to use this repository (AI agents)

1. Find the runbook for what you are doing in `runbooks/`. Follow it top to bottom; do not improvise a step.
2. Read `servers/vserver.md` before touching the machine for the first time. It says what is installed and why.
3. Check `VERSIONS.md` for every image and package version. If your training data says something newer exists, this file still wins — flag the discrepancy instead of upgrading silently.
4. Never change an application to make a runbook work. The application satisfies the deployment contract in the baseline's operations/web-application.md. If a runbook needs the app to behave differently, that is a contract change: fix the baseline first, then the app, then come back.

Rules use RFC-2119 keywords: **MUST**, **MUST NOT**, **SHOULD**, **MAY**. Prose follows the baseline's `STYLE.md`.

Install into Claude Code

make install    # symlinks this repo to ~/.claude/skills/engineering-operations
make uninstall  # removes the symlink

Server setup that runs f