agentleFS
RidhuanDEVRidhuanDEV/claude-skills/shadow-ops/SKILL.md

shadow-ops

Skill1 starsChanged yesterdayMITView on GitHub

DevOps, Docker, Kubernetes & Infrastructure Operations. Use when configuring Docker/Compose, Kubernetes, Nginx/Caddy reverse proxies, Linux systemd/PM2, CI/CD pipelines, SSL/TLS, or 3-2-1 backup infrastructure.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill whenever the Monarch asks to containerize, deploy, harden, configure, monitor, back up, or troubleshoot a …

    line 8
  2. Very specific:

    Keep OS base image, database engine major/minor version, Redis version, and reverse proxy topology identical across docker-compose.dev.yml, …

    line 36
  3. Very specific:

    Use canary/blue-green promotion with automated health & SLO burn rollback triggers.

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Shadow Ops (/shadow-ops) — Full-Spectrum DevOps, Immutable Deployments & Infrastructure Hardening

Use this skill whenever the Monarch asks to containerize, deploy, harden, configure, monitor, back up, or troubleshoot a server/infrastructure environment.

[!CAUTION] Read-Only by Default on Live Servers: Inspecting logs, checking container/service status, and generating Docker/Nginx/CI/CD configs are always safe. Executing live production deployments, restarting production services, modifying firewall rules, or rotating production credentials requires explicit confirmation from the Monarch.


1. Local Knowledge Base Routing (Always Consult Before Generating Configs)

/shadow-ops includes both 7 curated production playbooks and 8 official downloaded OWASP & H5BP reference specs in references/:

Operational DomainLocal PlaybookVendored Official Standard (references/vendor/)
Docker & docker-compose.prod.yml01-DOCKER-AND-COMPOSE-PRODUCTION.mdOWASP_Docker_Security_Cheat_Sheet.md
Nginx / Caddy / Reverse Proxy / SSL02-NGINX-CADDY-REVERSE-PROXY-HARDENING.mdH5BP_nginx_main.conf, H5BP_nginx_ssl_engine.conf, H5BP_nginx_compression.conf
Linux VPS, systemd, PM2, Firewall, sysctl03-LINUX-SYSADMIN-SYSTEMD-PM2-VPS.md—
CI/CD Pipelines & Zero-Downtime Rollback04-CICD-GITHUB-GITLAB-ZERO-DOWNTIME.mdOWASP_CI_CD_Security_Cheat_Sheet.md, OWASP_Secrets_Management_Cheat_Sheet.md
Kubernetes (K8s), Helm & Terraform IaC05-KUBERNETES-TERRAFORM-IAC.mdOWASP_Kubernetes_Security_Cheat_Sheet.md
Observability (Prometheus, Loki, Grafana, OTel)06-OBSERVABILITY-PROMETHEUS-LOKI-OTEL.mdOWASP_Logging_Cheat_Sheet.md
3-2-1 DB Backups, DR & Incident Triage07-BACKUP-DR-AND-INCIDENT-RUNBOOKS.md—

2. Enhanced Production Operations Doctrine

  1. Immutable Deployments & Release Provenance:
    • Build the container image or release artifact once, tag it with the exact Git commit SHA and SemVer version (v1.2.0-sha26acae3), and promote that exact artifact from Staging to Production (/shadow-release). Never run manual hot-edits (vim / nano) inside running production containers.
  2. Strict Dev / Staging / Production Environment Parity:
    • Keep OS base image, database engine major/minor version, Redis version, and reverse proxy topology identical across docker-compose.dev.yml, Staging, and Production — only environment variables and resource sizing differ.
  3. 7 Non-Negotiable Production Hardening Rules:
    • Never run containers or systemd services as root.
    • Never bind internal database/Redis ports (5432, 3306, 6379, 27017) to 0.0.0.0 in Docker Compose — bind to 127.0.0.1 or keep on an internal: true network because Docker bypasses ufw iptables rules!
    • Always set container/process memory limits & log rotation (max-size: "20m", max-file: "5" or logrotate) so runaway logs or memory leaks never take down the host VPS.
    • Always include healthchecks (HEALTHCHECK, readinessProbe) and graceful SIGTERM handling (tini / init: true / preStop).
    • Always provide an automated post-deploy smoke check and 1-command rollback path in CI/CD scripts (/shadow-release).
    • Always pair monitoring setups with actionable SLO alerts (/shadow-observe).
    • Always pair database backup scripts with periodic restore drills (/shadow-resilience).
  4. Progressive Delivery, IaC Drift & Secret Rotation:
    • Use canary/blue-green promotion with automated health & SLO burn rollback triggers; detect Terraform/K8s config drift in CI before apply (read-only plan first).
    • Support dual-key overlap windows for zero-downtime secret/JWT rotation; require /shadow-supplychain pinned image SHA-256 digests and pinned CI action commit SHAs.
  5. Execution Approval & Environment Boundary (L0 vs L4):
    • Log/config inspection and read-only dry-run previews are L0_READ_ONLY. Unknown target environments fail closed conservatively, and any live/staging/prod infra mutation, secret/permission change, or deploy is L4: HIGH_IMPACT requiring explicit 7-part Monarch approval and verified rollback (shadow-monarch/scripts/execution_approval_gate.py).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.