homelab-terminal-report-deliverylisted

This skill should be used when building or modifying a homelab automation that needs to deliver a status report via email + Telegram + (optionally) a GitHub-hosted markdown archive — the shared report system (resilience-ledger-styled HTML as of 2026-08-17, previously Kanagawa-Wave-terminal-styled) already used by the weekly housekeeping sweep, the nightly backup summary, and the R2/B2 offsite sync emails. Also covers choosing between a minimal-link Telegram ping and a rich bulleted Telegram-as-primary-channel with conditional email (added 2026-08-20 to cut Postmark's 100/month free-tier quota). Trigger phrases include "homelab status report", "ledger styled email", "kanagawa wave email", "render-terminal-report", "homelab-report-lib", "consolidate emails into a digest", "add a new homelab report automation", "resilience-ledger design system", "claude_code_prompts schema", "push report to obsidian-vault", "deploy report script to a host other than ansible-ctrl", "raw ISO timestamp in email/telegram", "human re
jackson2w/claude-code-skills · ★ 1 · Data & Documents · score 64

Install: claude install-skill jackson2w/claude-code-skills

# Homelab terminal-report delivery system A shared, reusable pattern for any homelab automation that needs to tell Will "here's the status" via email, a Telegram ping, and (optionally) a durable GitHub-hosted record — instead of each automation inventing its own formatting and delivery plumbing. Built 2026-07-18/19 for the weekly housekeeping sweep, extended 2026-07-19 for the nightly backup summary and 2026-07-20 for the R2 offsite sync's email; reach for it again before writing a new bespoke report/notification flow. The first two run from `ansible-ctrl`; the R2 sync report runs locally on `pbs` instead (see "Deploying to a host other than ansible-ctrl" below) — the pattern isn't tied to any one host. ## What it looks like **Updated 2026-08-17**: the email HTML is now styled with the **resilience-ledger design system** (warm-paper/dark-ink "systems report" look — see `~/Desktop/resilience-ledger-design-system/` and `project_dfw_vultr_buildout` memory for the full design-token detail), not the earlier Kanagawa Wave terminal-window chrome. This was a **visual-only swap of `render_html()`** in `render-terminal-report.py` — the JSON schema below, the CLI interface, `render_markdown()`, and every calling orchestrator are all byte-for-byte unchanged (verified via diff before/after deploying). A colored callout box carries the BLUF (`OK`/`WARN`/`FAIL` label + tinted background, not emoji), each category renders as a list of status-pill + headline + optional detail rows, and a "