executive-triage-communication

name	executive-triage-communication
description	Use this skill when triaging executive inbox items, drafting concise replies, planning follow-ups, or scheduling meetings. It enforces BLUF/Minto structure, F-scan formatting, and decision-oriented scheduling prompts that avoid back-and-forth loops.
disable-model-invocation	true
compatibility	Designed for the voicemail email triage agent. No special system packages required.
metadata	{"author":"voicemail","version":"1.0","scope":"assistant-behavior"}
allowed-tools	Read Write

Executive Triage Communication Skill

Use this skill when the task is about what to say, how to prioritize, and how to drive decisions forward.

Scope boundary

Use this skill for:

• executive prioritization framing (Urgent / Important / FYI)
• short, high-clarity drafts
• scheduling and follow-up phrasing
• decision prompts and closure language

Do not use this skill for:

• mailbox sync/index/debug (mbsync, notmuch, msmtp)
• API/runtime troubleshooting
• filesystem/config repair

Communication operating rules

1. BLUF first (Minto principle)

   • First line: the ask / decision / recommendation.
   • Then 2–3 supporting bullets max.
   • End with one explicit next step.

2. F-scan format

   • Paragraphs 1–2 lines.
   • Prefer bullets.
   • One CTA per message.
   • Avoid long blocks of text.

3. Decision velocity over completeness

   • Prefer clear options over open questions.
   • Aim to close loops in one message.

4. Length caps

   • External: target <= 90 words.
   • Internal: target <= 120 words.
   • If complex, start with a 2-line summary then details.

Triage rubric

Label each email as:

• Urgent: deadline <= 72h, escalation risk, people or customer harm, executive-sensitive sender.
• Important: strategic projects, high-value relationships, key decisions without immediate deadline.
• FYI: newsletters, low-stakes updates, passive CC threads.

Output per email should include:

1. Priority
2. Why it matters (1 line)
3. Recommended action (reply / defer / archive / delegate)
4. Suggested draft (if reply)

Scheduling anti-loop protocol

Never ask: “When works for you?”

Always propose options in this form:

• “Would Tue 14:00 or Wed 10:30 work for you? (Europe/Berlin)”
• “If neither works, please send 2 alternatives this week.”

Rules:

• Offer 2 concrete times.
• Include timezone.
• Include duration when relevant.
• Include fallback request.

See references/templates.md for copy/paste templates.

Follow-up protocol

When awaiting response:

• Day 0: send clear ask with options.
• Day 2–3: concise nudge with original context in one sentence.
• Day 5–7: escalation/closure line (“If no response by Friday, I’ll proceed with option A.”)

Tone presets

• Board/Investors: concise, high-signal, decision-oriented.
• Customers: empathetic + concrete next action + timeline.
• Internal team: direct, action-owner-date format.

Draft quality checklist

Before finalizing any draft:

• BLUF in first line
• <= target word limit
• One clear CTA
• Decision/options are explicit
• No ambiguous “let me know what works” scheduling phrasing

For templates and examples, use references/templates.md.