intimidation

Draft escalation messages stating risk, action, deadline, and owner.

105|13|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Hmbown/Wizards-of-the-Ghosts --skill intimidation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: intimidation
Source: https://github.com/Hmbown/Wizards-of-the-Ghosts/tree/main/generated/hermes/messaging-and-coordination/intimidation
Command: npx skills add https://github.com/Hmbown/Wizards-of-the-Ghosts --skill intimidation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides calibrated, serious-toned messaging to communicate risk, urgency, and required actions, ensuring stakeholders act without unnecessary delay.

Core Features & Use Cases

  • Calibrated tone for security findings, compliance obligations, deadline-driven escalations, and remediation notices.
  • Structured deliverables that state risk, action, deadline, and owner, with justification and next steps.
  • Clear handoffs and accountability guidance for cross-team coordination in high-stakes contexts.

Quick Start

Draft a stern but defensible escalation message that clearly states the risk, required action, deadline, and owner.

Frequently Asked Questions about intimidation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an escalation message that clearly communicates risk and deadlines?

An escalation message must include a risk rationale, required action, deadline, owner, and consequences of inaction. Structuring communications this way ensures stakeholders understand accountability and act without delay on security findings or compliance obligations.

What is the best way to enforce accountability in deadline-driven remediation notices?

Enforce accountability in remediation notices by explicitly stating the owner, deadline, and consequences of inaction. This calibrated, serious-toned messaging provides clear handoffs for cross-team coordination in high-stakes contexts.

How do I draft a stern but defensible compliance notice for unresolved security findings?

Draft a defensible compliance notice by incorporating a structured risk rationale alongside the required remediation action. This approach calibrates the tone to be serious while ensuring the message remains defensible and clearly states the necessary next steps.

Does this approach to assertive messaging work for cross-team coordination in risk management?

Yes, assertive messaging works for cross-team coordination by providing clear handoffs and accountability guidance. It structures deliverables to state risk, action, deadline, and owner, which is essential for managing risk across multiple teams.

When should I use authoritative messaging for compliance obligations?

Use authoritative messaging for compliance obligations when deadline-driven remediation is required and accountability must be explicit. It ensures stakeholders understand the urgency and necessary actions without unnecessary delay.

What limitations exist when using calibrated tone for escalation messages?

Calibrated tone messaging is limited to contexts requiring serious, defensible communication like security findings or compliance notices. It is not suitable for routine updates, as its structured focus on risk, deadlines, and consequences may appear overly aggressive in low-stakes situations.