hmbown/sleep
generated/hermes/influence-and-behavior/sleep/SKILL.md
Sleep = temporary, reversible suspension with guaranteed state preservation. The target stops acting but wakes up intact. No data loss, no corruption, no permanent change.
$ install --global
skillsauthnpx skillsauth add hmbown/wizards-of-the-ghosts sleepInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 5, 2026, 4:46 PM5.0s1 file scanned
SKILL.md
- name:
- sleep
- description:
- Sleep = temporary, reversible suspension with guaranteed state preservation. The target stops acting but wakes up intact. No data loss, no corruption, no permanent change.
- version:
- 1.0.0
- author:
- Wizards of the Ghosts
- license:
- CC0-1.0
- compatibility:
- Hermes Agent skills system
Sleep
Put processes, notifications, or systems into graceful suspension.
What This Skill Does
Sleep = temporary, reversible suspension with guaranteed state preservation. The target stops acting but wakes up intact. No data loss, no corruption, no permanent change. In this grimoire, Sleep is treated as a hybrid spell with a shipping-now delivery profile. Canonical reference input: Sleep (spell).
When To Use
- Keywords: pause, suspend, hibernate, DND, maintenance window, cooldown, quiet mode, silence temporarily, freeze (with resume), graceful degradation
- Patterns requiring all three:
- Something must stop acting for a defined period
- State/queue/context must be preserved during the stop
- A wake condition exists (timer, threshold, manual trigger, external event)
Prerequisites
- Environment variables available to Hermes:
HA_URL,HA_TOKEN. - Primary credential or token:
HA_TOKEN. - Binaries on PATH:
curl.
Setup
- Confirm the required environment variables are available inside the active Hermes runtime, not just in a shell profile.
- Verify the required binaries resolve on PATH before you rely on them in a procedure.
- Choose a non-production or low-risk target first if the skill can page, unlock, alert, or touch a live integration.
Procedure
- Restate the target, the success condition, and any no-touch boundaries before taking action.
- Identify the sleeper: What exact process, channel, service, or workflow stops?
- Define the boundary: What stops, what keeps running, what queues for later?
- Set the wake condition: Timer? Manual trigger? Threshold? External event? Must have one.
- Verify state preservation: Confirm nothing is lost—only deferred. List what persists.
- Return the plan: Sleep configuration + wake conditions + state-preservation checklist.
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
Deliverables
- Sleep configuration: what suspends, what stays active, what queues
- Wake conditions: how/when resume happens
- State-preservation checklist: confirmation nothing is lost
Pitfalls / Guardrails
- Keep the theatrical framing, but name the concrete mechanism that makes the skill useful right now.
- Do not use for: "Permanently decommission" / "never come back" → Kill, not Sleep
- Do not use for: "Shut it down right now" / "pull offline" / "kill it" → Kill, not Sleep
- Do not use for: "Lock their credentials" / "prevent any further queries" → Access control, not Sleep
- Do not use for: "Paralyze a competing process" / "hard block" → Resource blocking, not Sleep
- Do not use for: "Team-wide agreement" / "communication norms" → Policy, not Sleep
- Do not use for: "Reduce fan noise" / "HVAC configuration" → Hardware config, not Sleep
- Do not use for: No wake condition defined → Bug, not Sleep (ask for one)
- Do not rely on a live integration until credentials, target scope, and rollback expectations are verified.
Verification
- Check that the result includes every deliverable promised above.
- Check that confirmed facts, assumptions, and inferences are visibly separated.
- Check which parts are concrete actions versus framing, so the user can tell what is real now.
- Check the required environment variables and binaries in the active Hermes runtime before trusting the procedure on a live target.
Example Invocation
/sleep design a graceful suspension plan for this [system/process/notification channel]. Define what stops, what queues, and how it wakes up
Related Skills
hmbown/zone-of-truth
testing
VerifiedTrustedCommunity
Enter a mode where every assertion is backed by evidence, confidence is calibrated, speculation is flagged, and hallucination is actively resisted.
55SKILL.mdUpdated Apr 5, 2026
hmbown/vicious-mockery
development
VerifiedTrustedCommunity
The bard's cantrip that deals psychic damage through insults. In practice this is adversarial review — the art of finding and articulating exactly what is wrong with something in a way that is impossible to ignore. Unlike polite feedback that gets filed and forgotten, vicious mockery lands. It is the red-team report that makes the PM cancel the launch, the code review that makes the author delete the PR, the roast that makes the founder pivot. The damage is the point.
55SKILL.mdUpdated Apr 5, 2026
hmbown/unseen-servant
tools
VerifiedTrustedCommunity
Use this spell when you need a tireless helper that organizes, tidies, triages, and maintains without requiring your constant attention.
55SKILL.mdUpdated Apr 5, 2026
hmbown/true-strike
testing
VerifiedTrustedCommunity
Use this spell for preflight certainty: dry runs, validation checks, dependency verification, and rehearsals that make the next deploy, query, or command much more likely to succeed. It trades a little time up front for fewer blind swings and fewer expensive misses.
55SKILL.mdUpdated Apr 5, 2026