Menu
Check health of the homelab-backup service — last run status, next scheduled run, R2 bucket contents, and local archive state. Quick mobile-friendly summary.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Delete a blog post or review from blog.carter2099.com. Soft-deletes the markdown file (moved to deleted/ directory) and destroys the database record.
Edit an existing blog post or review on blog.carter2099.com. Find by title/ID, show current content, collaboratively revise, preview changes, then update.
Create a new blog post on blog.carter2099.com. Collaboratively draft and polish markdown content, preview it, then publish — triggering subscriber email notifications via the Rails app.
Create a new review on blog.carter2099.com (Book, Movie, Show, Product, or Video Game). Collaboratively draft content, preview it, then publish — triggering subscriber email notifications via the Rails app.
Audit the homelab for outdated software and report findings. Use when user says "check for updates", "what's outdated", "audit the homelab", "run update check", or wants a system health report.
Create a new scheduled agent that runs on a systemd timer — recurring maintenance, checks, reports, or any task you want automated. Use when user says "set up a scheduled agent", "automate this to run daily", "I want a cron job for X".
| name | backup-health |
| description | Check health of the homelab-backup service — last run status, next scheduled run, R2 bucket contents, and local archive state. Quick mobile-friendly summary. |
Health check for the homelab-backup systemd timer + R2 upload pipeline.
systemctl --user list-timers homelab-backup.timer --no-pager to show next/last fire time.systemctl --user status homelab-backup.service --no-pager -l to check exit status of the most recent run.journalctl --user -u homelab-backup.service -n 25 --no-pager for the last run's output. Look for errors, partial failures, or integrity check issues.list subcommand (no aws CLI / rclone is installed on this host):
set -a && source ~/homelab-backup/.env && set +a
~/homelab-backup/homelab-backup list
systemctl --user list-timers homelab-backup-restore-drill.timer --no-pager (monthly, 1st 12:00 UTC) and systemctl --user status homelab-backup-restore-drill.service --no-pager for the last drill result. Report last drill date + PASS/FAIL.ls -lht ~/backups/ | head -10 to show recent local backups and sizes.du -sh ~/backups/ to report total local backup footprint.Summarize as a short mobile-friendly checklist:
Note: if the main run fails, homelab-backup-notify.service (OnFailure=) emails Carter automatically — a health check showing failure means that email was already sent (unless SMTP itself is down).
Keep it concise — this is meant to be glanced at on a phone.