heinzel-fleet-audit

Solid

Compare key policies across all servers in memory/servers/ to surface silent drift. Makes no configuration changes; writes one audit-trail line to each host's journal. Probes unattended-upgrades, sshd effective config, firewall posture, MTA, time sync, and auto-reboot behaviour. Use when the user asks to "fleet audit", "vergleiche alle server", "policy drift check", "are my servers configured the same?", or after a fix on one host to find which others carry the same bug.

DevOps & Infrastructure 82 stars 13 forks Updated today MIT

Install

View on GitHub

Quality Score: 88/100

Stars 20%
64
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# heinzel-fleet-audit Cross-server policy audit. Heinzel knows every host individually but has nothing that holds hosts against each other. This skill closes that gap by probing the same set of settings on every server in `memory/servers/` and rendering a side-by-side comparison so silent drift becomes visible. **No configuration changes.** The audit never alters any host's configuration. The only write is a single audit-trail line to each host's system journal (step 6 below). Acting on findings is a separate step (heinzel-housekeeping for per-host fixes, or manual edits with explicit user approval). **Never run automatically** — only on explicit user request. ## When to use - "Run a fleet audit" - "Vergleiche die Policies auf allen Servern" - "Drift check across the fleet" - After fixing a config bug on one host: "which other hosts have the same problem?" Do NOT auto-invoke for generic phrases like "check my servers" — that maps to single-host housekeeping. ## Workflow 1. **Discover hosts.** List directories under `memory/servers/` whose name resolves to a real host (skip placeholders like `server1.example.com` and `192.168.64.20` unless the user names them explicitly). The user may pass an explicit subset as arguments — in that case audit only those. 2. **Resolve SSH users.** Read `memory/user.md` for the per-host SSH user. Hosts without a mapping go on a "skipped: no SSH user known" list (do not prompt — just report). 3. **Probe in paral...

Details

Author
wintermeyer
Repository
wintermeyer/heinzel
Created
5 months ago
Last Updated
today
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Solid

heinzel-security

Run a heinzel security audit on a server — SSH hardening (password auth, weak algos, root login), firewall, user account hygiene, listening services, kernel hardening (ASLR, IP forwarding), file permissions, SUID/SGID audit, fail2ban. Use when the user asks for a "security audit", "security review", "hardening check", or to "audit security on <host>". Do NOT auto-invoke on generic phrases like "check server <host>". Covers Linux (Debian, Ubuntu, RHEL, CentOS, Fedora, SUSE) and macOS (SIP, FileVault, Gatekeeper).

82 Updated today
wintermeyer
DevOps & Infrastructure Solid

infra-audit

Server / infrastructure security audit of LIVE hosts over SSH (12 dimensions IS1-IS12: SSH hardening, accounts, network exposure, TLS, firewall, patch posture, logging, web services, Docker, databases, filesystem, host secrets). Deterministic collector + parallel LLM analysts; dual-vantage (internal SSH + external via proxy); per-target authorization gate; consent-gated tool installs; read-only with one consented exception. Flags: --host user@addr[:port] (single ad-hoc host), --quick (IS1+IS3+IS4, <3 min/host), --dimensions IS1,IS3,… (explicit subset), --no-install (hard read-only), --dry-run (print commands, no connections), --resume <run-dir> (continue interrupted run), --proxy <url> (external-scan proxy), --external direct (proxyless external scan, polite timing), --skip-external (internal vantage only), --deep-scan (nmap -p- full port sweep), --confirm-targets <sha256> (non-interactive authorization).

6 Updated today
greglas75
DevOps & Infrastructure Solid

heinzel-housekeeping

Run a heinzel housekeeping (health) inspection on a server — disk, memory, load, pending updates, firewall, SSL certs, failed systemd units, logs, kernel reboot status, and service-specific checks. Use when the user asks to "run housekeeping", "housekeeping report", "run a health check on <host>", or "do routine inspection". Do NOT auto-invoke for ambiguous requests like "check server <host>" — that's reserved for quick queries. Covers Linux (Debian, Ubuntu, RHEL, CentOS, Fedora, SUSE) and macOS.

82 Updated today
wintermeyer