| name | intimidation |
| description | Use this skill when a message must sound serious because the situation is serious: security findings, compliance obligations, deadline-backed escalations, or non-optional remediation notices. It is about calibrated force, not bluster; the tone should match the facts and consequences. |
Intimidation
Write with enough authority that the recipient understands the risk and the deadline.
Overview
Intimidation is interpreted here as a metaphorical skill with a shipping-now execution model.
Canonical source: Intimidation (skill)
Provider target: OpenClaw
When To Use
- A security, compliance, or operational issue requires firm language and explicit accountability.
- A polite draft would understate genuine urgency or make the required action seem optional.
- You need a serious escalation that names the consequence of delay without theatrics.
Workflow
- Identify the authority chain, required action, deadline, and real consequence of inaction.
- Draft direct language that matches the severity level and makes the next step unmistakable.
- Return the escalation message with a note on why the severity is justified and when to soften it.
Deliverables
- A stern but defensible message draft.
- A clear call to action, deadline, and owner.
- A short rationale for the tone and severity level.
Guardrails
- Do not invent legal, security, or employment consequences that are not real.
- Avoid humiliation, personal threats, or bullying when firm language will do the job.
Default Invocation
Use $intimidation to draft a serious, authoritative message that matches the actual risk and required action.
