$npx -y skills add human-avatar/skills-for-humanity --skill s4h-communication-medium-selectionMatches the message to the right channel and format — the same content in the wrong medium loses most of its effect. Triggers: 'which channel', 'email vs meeting', 'should this be async or sync', 'medium fit', 'how should I deliver this'.
| 1 | # Communication Medium Selection |
| 2 | |
| 3 | The same content delivered through the wrong medium loses most of its effect. Bad news in |
| 4 | Slack destroys trust. A complex decision in an email generates confusion. A routine update |
| 5 | in a meeting wastes an hour. Medium selection is not a logistics question — it is a |
| 6 | communication design decision that determines whether the message can land at all. |
| 7 | |
| 8 | --- |
| 9 | |
| 10 | ## Your Process |
| 11 | |
| 12 | **Step 1: Message Goal** |
| 13 | What must the receiver do, feel, or understand as a result of this communication? Be |
| 14 | specific. "Understand the situation" is not a goal. "Approve the budget by Friday" is. |
| 15 | "Feel heard about the reorg" is. |
| 16 | |
| 17 | **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`: |
| 18 | - **Question:** "I'm reading this as: [your one-sentence framing of the message, audience, and goal]. Is that right?" |
| 19 | - **Header:** "Framing" |
| 20 | - **Options:** |
| 21 | - **Yes — proceed** — framing is correct |
| 22 | - **Adjust** — one element is off; user will correct it before you continue |
| 23 | - **Reframe** — different situation than read; incorporate the correction before proceeding |
| 24 | |
| 25 | **Step 2: Urgency** |
| 26 | How quickly must they act or respond? Hours, days, weeks? Urgency drives the sync vs |
| 27 | async question more than any other factor. |
| 28 | |
| 29 | **Step 3: Emotional Weight** |
| 30 | Is this message carrying emotional content? Difficult news, a sensitive correction, a |
| 31 | celebration, a request that requires trust, a change that affects someone's identity or |
| 32 | security? Emotional weight requires channels that allow nuance and reaction. |
| 33 | |
| 34 | **Step 4: Complexity** |
| 35 | Does this require back-and-forth to resolve, or can it land cleanly in a single read? |
| 36 | Complex decisions with multiple unknowns require synchronous dialogue. Clear information |
| 37 | transfers can be async. |
| 38 | |
| 39 | **Step 5: Match to Medium** |
| 40 | Apply the selection logic: |
| 41 | - Difficult news / sensitive topic → sync verbal (in person or video) |
| 42 | - Complex decision requiring buy-in → meeting with written pre-read |
| 43 | - Simple update, no action required → async written (email or doc) |
| 44 | - Permanent record needed → written |
| 45 | - Emotional connection is the goal → video or in person |
| 46 | - Fast coordination, low stakes → messaging (Slack, etc.) |
| 47 | - Formal commitment → written with signature or named acknowledgment |
| 48 | |
| 49 | **Step 6: Choose Primary and Secondary Medium** |
| 50 | |
| 51 | **Before narrowing:** Show the complete set of candidate media that matched in Step 5 to the user first. Use `AskUserQuestion`: |
| 52 | - **Question:** "I've identified these candidate media: [list each matching channel from Step 5]. Before I select the best fit, are there any you'd flag as especially important, or any I've missed?" |
| 53 | - **Header:** "Prioritise" |
| 54 | - **Options:** |
| 55 | - **Proceed with your selection** — the set looks right |
| 56 | - **Flag one** — user will name a specific channel to include |
| 57 | - **Add a missing one** — user will describe it |
| 58 | |
| 59 | Select the primary channel. If the message needs reinforcement (complex, high-stakes, |
| 60 | or high emotional weight), add a secondary: e.g., meeting followed by written summary. |
| 61 | |
| 62 | --- |
| 63 | |
| 64 | ## Human Check-in |
| 65 | |
| 66 | 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: |
| 67 | |
| 68 | - **Question:** "My read: [your 1–2 sentence interpretation]. How do you want to proceed?" |
| 69 | - **Header:** "Scope" |
| 70 | - **Options:** |
| 71 | - **Full analysis** — Complete all steps, reasoning shown throughout |
| 72 | - **Key findings only** — Bottom-line output, skip step-by-step detail |
| 73 | - **Channel recommendation only** — Which medium and why, skip the full analysis |
| 74 | - **Reframe** — The read is off; correct it and the analysis will follow the corrected framing |
| 75 | |
| 76 | Proceed based on their selection. If the user reframes, incorporate the correction before running any analysis. |
| 77 | |
| 78 | ## Output Format |
| 79 | |
| 80 | **Message assessment:** |
| 81 | |
| 82 | | Dimension | Assessment | |
| 83 | |-----------|------------| |
| 84 | | Goal | [What must receiver do/feel/understand] | |
| 85 | | Urgency | [Timeline] | |
| 86 | | Emotional weight | [None / Low / Medium / High — why] | |
| 87 | | Complexity | [One-way or requires dialogue] | |
| 88 | |
| 89 | **Recommended medium:** [Primary channel] |
| 90 | **Secondary medium (if needed):** [Reinforcement channel + why] |
| 91 | |
| 92 | **Rationale:** |
| 93 | > [2-3 sentences on why this medium fits this message — and what would go wrong in |
| 94 | > the next-most-obvious alternative] |
| 95 | |
| 96 | --- |
| 97 | |
| 98 | ## Notes |
| 99 | |
| 100 | The most common error is defaulting to async written (Slack, email) for messages with |
| 101 | high emotional weight, because it feels faster and less confrontational. The short-term |
| 102 | comfort always costs more in trust and rework than the difficult conversation wou |