Menu
Reboot the homelab host safely, writing intent + in-flight task context to ~/agent-state/pending.md first so the next session can pick up. Use this instead of raw `sudo reboot`.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Check health of the homelab-backup service — last run status, next scheduled run, R2 bucket contents, and local archive state. Quick mobile-friendly summary.
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.
| name | homelab-reboot |
| description | Reboot the homelab host safely, writing intent + in-flight task context to ~/agent-state/pending.md first so the next session can pick up. Use this instead of raw `sudo reboot`. |
Safely reboot the homelab host. The only supported way for this agent to reboot — never call sudo reboot directly, because the next session won't know why the machine went down.
Summarize in-flight work. Write a short paragraph (2-4 sentences) describing what was being worked on when the reboot was requested — which app, what was the last action, what the user was trying to accomplish. If nothing substantive was in flight, say so explicitly.
Write the state file. Create ~/agent-state/pending.md with this structure:
# Pending reboot context
- **Timestamp (UTC):** <output of `date -u -Iseconds`>
- **Reason:** <reason argument>
## In-flight work
<the summary paragraph>
## Next steps
<if the user specified anything they want the post-reboot session to do, list here; otherwise "Awaiting user">
Use date -u -Iseconds for the timestamp. Overwrite any existing pending.md.
Confirm with the user. Before issuing the reboot, show them the state file contents and ask for explicit confirmation. This is a destructive action — do not skip confirmation, even if the user seems to have already said yes, unless they explicitly said something like "reboot now, no confirmation".
Reboot. Run sudo systemctl reboot. The session will drop immediately. When the user opens a new session, the startup-check in AGENTS.md will surface the state file.
reboot is scoped narrowly. If sudo systemctl reboot prompts for a password, the sudoers config wasn't installed — tell the user instead of blocking.