From skills-for-humanity
Guides the selection of the right communication medium (sync vs async, email vs meeting, etc.) based on message goal, urgency, emotional weight, and complexity.
How this skill is triggered — by the user, by Claude, or both
Slash command
/skills-for-humanity:s4h-communication-medium-selectionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The same content delivered through the wrong medium loses most of its effect. Bad news in
The same content delivered through the wrong medium loses most of its effect. Bad news in Slack destroys trust. A complex decision in an email generates confusion. A routine update in a meeting wastes an hour. Medium selection is not a logistics question — it is a communication design decision that determines whether the message can land at all.
Step 1: Message Goal What must the receiver do, feel, or understand as a result of this communication? Be specific. "Understand the situation" is not a goal. "Approve the budget by Friday" is. "Feel heard about the reorg" is.
Framing check: Confirm the message, the audience, and the goal before continuing. State what you've identified — the actual communication being designed and its key parameters — in one sentence, then use AskUserQuestion:
Step 2: Urgency How quickly must they act or respond? Hours, days, weeks? Urgency drives the sync vs async question more than any other factor.
Step 3: Emotional Weight Is this message carrying emotional content? Difficult news, a sensitive correction, a celebration, a request that requires trust, a change that affects someone's identity or security? Emotional weight requires channels that allow nuance and reaction.
Step 4: Complexity Does this require back-and-forth to resolve, or can it land cleanly in a single read? Complex decisions with multiple unknowns require synchronous dialogue. Clear information transfers can be async.
Step 5: Match to Medium Apply the selection logic:
Step 6: Choose Primary and Secondary Medium
Before narrowing: Show the complete set of candidate media that matched in Step 5 to the user first. Use AskUserQuestion:
Select the primary channel. If the message needs reinforcement (complex, high-stakes, or high emotional weight), add a secondary: e.g., meeting followed by written summary.
Before proceeding, use the AskUserQuestion tool. State your interpretation of the situation in 1–2 sentences — what is being analyzed and what the core question is — then ask:
Proceed based on their selection. If the user reframes, incorporate the correction before running any analysis.
Message assessment:
| Dimension | Assessment |
|---|---|
| Goal | [What must receiver do/feel/understand] |
| Urgency | [Timeline] |
| Emotional weight | [None / Low / Medium / High — why] |
| Complexity | [One-way or requires dialogue] |
Recommended medium: [Primary channel] Secondary medium (if needed): [Reinforcement channel + why]
Rationale:
[2-3 sentences on why this medium fits this message — and what would go wrong in the next-most-obvious alternative]
The most common error is defaulting to async written (Slack, email) for messages with high emotional weight, because it feels faster and less confrontational. The short-term comfort always costs more in trust and rework than the difficult conversation would have.
After delivering this output, use AskUserQuestion to offer the next move:
/s4h-communication-audience-modeling — Model the audience for the selected medium/s4h-writing-audience-calibration — Calibrate the writing for the chosen medium/s4h-communication-clarity-audit — Audit clarity for the selected mediumnpx claudepluginhub human-avatar/skills-for-humanityRoutes communication requests to the right skill (audience-modeling, clarity-audit, medium-selection, objection-mapping) based on situation. Use when unsure which tool fits.
Writes status updates, executive summaries, and project communications tailored to stakeholder roles and seniority levels. Helps structure messaging, manage up, and communicate delays or bad news.
Drafts one cold outreach message (email, LinkedIn note, or follow-up) from a signal and persona, with variants and a self-check lint. Reads company voice and proof from a context file.