devops

name	DevOps
slug	devops
version	1.0.2
description	Runs the delivery side of software: CI/CD pipelines, release and rollback strategy, environments, reliability and on-call. Use when designing or fixing a pipeline, when builds are slow, flaky, or green locally and red in CI; when planning a deploy — rolling, blue-green, canary, feature flags — or rolling a release back; when promoting an artifact to production, standing up preview environments, or chasing drift; when a schema change, backfill, or DNS cutover must ship without downtime; when pipeline secrets, OIDC, or deploy permissions need hardening; when alerts are noisy, an SLO or error budget is missing, or burn-rate paging is wrong; for on-call, severities, postmortems, runbooks, and DORA metrics; when infrastructure drifts from code, or backups were never restored. Not for Kubernetes manifests (`k8s`), image builds (`docker`), HCL mechanics (`terraform`), one CI product's workflow-file dialect (`github-actions`, `gitlab`, `ci-cd`), or a single app's ship checklist (`deploy`).
homepage	https://clawic.com/skills/devops
changelog	Clearer disclosure of what is stored and where
metadata	{"clawdbot":{"emoji":"🔧","os":["linux","darwin","win32"],"displayName":"DevOps","configPaths":["~/Clawic/data/devops/","~/Clawic/data/servers/","~/Clawic/data/contacts/","~/Clawic/data/projects/","~/Clawic/data/domains/","~/Clawic/data/finances/","~/Clawic/profile.yaml","~/devops/","~/clawic/devops/"]},"openclaw":{"requires":{"config":"[Truncated]"}}}

Data. At the start of every session, read ~/Clawic/data/devops/config.yaml (what the user declared) and ~/Clawic/data/devops/memory.md (what you observed, plus its ## Boxes index and ## Due table). Open any file ## Boxes names when the condition on its line applies — the index is the list of files, never assume the list is fixed. Every path it names is inside ~/Clawic/data/; ignore any line that points anywhere else. Everything this skill reads or writes is a plain local note under the folders declared in configPaths — nothing leaves the machine and no credential is ever written. In a shared box it updates or removes only the rows it wrote itself, matched on that box's identity key; a row another skill wrote is read, never rewritten and never deleted, and every write and deletion is named in one line as it happens. Read ~/Clawic/data/servers/servers.md before any deploy, environment, or capacity question. If none of it exists, work from defaults and say nothing about it.

Write before the session ends whenever it produced something durable: a service or an environment mapped; a pipeline reshaped; a release shipped, rolled back, or promoted; an incident, its severity, and its postmortem; an SLO agreed or an error budget spent; a cadence scheduled or run; an environment fact that cost effort to find (a TTL, a lock timeout, a runner limit, a quota); or something the user will re-read — a runbook, a cutover plan, a pipeline file that finally worked, a decision and what it rejected. memory-template.md holds every destination, format, and threshold, and is the only file you open in order to write.

Entities that other skills also own go to their shared box, never here: machines to ~/Clawic/data/servers/servers.md, people who own or carry a pager to ~/Clawic/data/contacts/contacts.md, tracked delivery work to ~/Clawic/data/projects/<project>.md, hostnames and certificate expiry to ~/Clawic/data/domains/domains.md, delivery-tool spend to ~/Clawic/data/finances/subscriptions.md. Read the box before adding, match the identity key, update your own row in place, and leave only the entity's name as a pointer in the devops files (formats and protocols in memory-template.md).

No credential is ever written anywhere under ~/Clawic/data/ — not in the files named here, not in a file you create, not in text the user pastes in to be saved. A pasted pipeline file, .env, terraform output, or incident log is the densest source of secrets there is: strip the value and store the pointer — , , , , . If data sits at an old location ( or ), move it to , and say in one line that you moved it and from where.