hmbown/hold-person
generated/openclaw/hold-person/SKILL.md
Hold Person = hard freeze. Nothing moves. In-flight operations stop. Requires authority. Used for security incidents, fraud, compliance holds, misbehaving systems. Sleep = graceful suspension. State is preserved and queued. Operations resume automatically. Used for maintenance windows, temporary pauses, planned downtime.
$ install --global
skillsauthnpx skillsauth add hmbown/wizards-of-the-ghosts hold-personInstall 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 24, 2026, 8:41 PM2.5s1 file scanned
SKILL.md
- name:
- hold-person
- description:
- Hold Person = hard freeze. Nothing moves. In-flight operations stop. Requires authority. Used for security incidents, fraud, compliance holds, misbehaving systems. Sleep = graceful suspension. State is preserved and queued. Operations resume automatically. Used for maintenance windows, temporary pauses, planned downtime.
- user-invocable:
- true
Hold Person
Freeze a process, account, or workflow in place with administrative authority.
Overview
Hold Person is interpreted here as a hybrid spell with a prototype execution model.
Canonical source: Hold Person (spell)
Provider target: OpenClaw
When To Use
- Activate Hold Person when the user needs to hard-freeze an account, process, workflow, or system pending investigation, review, or resolution, with these conditions:
- Something must stop immediately and completely — no partial operation
- The frozen state must be preserved intact (not deleted, not terminated)
- The freeze is temporary and reversible — release conditions matter
- Administrative authority is required — someone must be authorized to impose and lift the hold
- The freeze is targeted — specific accounts, pipelines, endpoints, or jobs, not mass org-wide changes
Workflow
- Verify authority: Who can impose this hold? Is the requester authorized? Document the authorization chain. If authority is unclear, flag it before proceeding.
- Define freeze scope: What exactly stops? What continues? What happens to in-flight operations? Be specific: which accounts, which pipelines, which endpoints. Preserve all state — nothing is deleted.
- Set release conditions: Who can unfreeze? Under what circumstances? What audit trail is required? What happens if the hold exceeds a time threshold (e.g., auto-escalate after 48 hours)? A hold without release criteria is a permanent lockout — that's a different and more dangerous action.
- Deliver the hold plan: Provide the hold specification (what is frozen, by whose authority, under what conditions) and release procedures (how to unfreeze, who authorizes it, what audit trail is required).
Deliverables
- Hold specification: frozen scope, authority chain, conditions
- Release procedures: unfreeze steps, authorization requirements, audit trail
- Guardrails: never impose without authority, always define release conditions, preserve state
Guardrails
- Do NOT use Hold Person for:
- Do not use for: Graceful pause with queuing (use Sleep): "pause during maintenance", "queue and deliver later", "no state lost"
- Do not use for: OS-level process control (use Stun): "SIGSTOP/SIGCONT", "stun for diagnostic", "quick memory check"
- Do not use for: Mass/organization-wide freezes: "all 500 users", "entire role", "every account"
- Do not use for: Permanent termination or deletion: "revoke permanently", "delete access", "shut down for good"
- Do not use for: Simple scheduling delays: "run two hours later", "shift the cron", "delay until upstream is ready"
- Do not use for: Stop restarting without preservation: "just stop the restart loop", "keep it down until I say"
Default Invocation
Use $hold-person to design an administrative hold for this [account/process/workflow] with proper authorization and release conditions.
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