exec-communicator
Skill1 starsChanged 7 months agoMITView on GitHub
Help PMs write clear, executive-ready communications. Use for status updates, escalations, decision requests, launch announcements, or leadership briefings.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Sach1ng/PM-operating-OSword for word, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 1
- Sach1ng/PM-operating-OS★ 3100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- app-store-analyzerSkill
- brainstormingSkill
- competitor-trackerSkill
- continual-learningSkill
- decision-loggerSkill
- experiment-designerSkill
- experiment-writeupSkill
- growth-loop-mapperSkill
- jtbd-extractorSkill
- knowledge-updaterSkill
- launch-postSkill
- launch-readinessSkill
- meeting-to-actionsSkill
- metric-storytellerSkill
- one-pagerSkill
- pptx-creatorSkill
- prd-writerSkill
- prioritization-scorerSkill
- retro-runnerSkill
- stakeholder-updateSkill
- strategy-connectorSkill
- user-interview-synthSkill
- what-ifSkill
- working-backwardsSkill
- writing-clearlySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
When asked "help me write this for leadership"
- Distinctive: line 23
Ask: What type of communication is needed?
- Distinctive: line 34
When is the deadline?
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Exec Communicator
Help PMs write clear, executive-ready communications using BLUF (Bottom Line Up Front) format. Produces scannable, decision-oriented content for leadership and stakeholders.
When to Use
- Writing weekly or bi-weekly status updates
- Escalating a risk or blocker to leadership
- Requesting a decision from stakeholders
- Drafting internal launch announcements for executives
- Preparing quarterly business review input
- When asked "help me write this for leadership"
Process / Template
1. Identify Communication Type
Ask: What type of communication is needed?
- Status update — progress vs. plan, metrics, risks
- Escalation — issue, impact, options, recommendation
- Decision request — context, options, trade-offs, deadline
- Launch announcement — what shipped, who it's for, impact
2. Gather Key Inputs
- What happened? (facts, metrics, outcomes)
- What's at risk? (blockers, dependencies)
- What do you need? (decision, resources, air cover)
- When is the deadline?
3. Apply BLUF Principles
- Lead with the "so what" — one sentence summary first
- Be specific — numbers, dates, named stakeholders
- Tie to metrics and strategy — connect to goals and OKRs
- Anticipate questions — address likely objections proactively
- Keep it scannable — bullets over paragraphs, headers for sections
4. Use the Right Template
Status Update:
- TL;DR — one sentence summary
- Progress vs. Plan — on track / at risk / behind
- Key Metrics — numbers that matter
- Risks/Blockers — what could derail
- Asks — what you need from leadership
Escalation:
- Issue — what's wrong (1–2 sentences)
- Impact — quantified (revenue, timeline, customers)
- Options — 2–3 paths forward with pros/cons
- Recommendation — what you recommend and why
- Timeline — when a decision is needed
Decision Request:
- Context — 2 sentences max
- Decision Needed — explicit ask
- Options with Trade-offs — pros/cons per option
- Recommendation — your call
- Deadline — when to decide
Output
A polished, executive-ready communication in the requested format. Scannable, specific, and action-oriented. Ready to paste into email, Slack, or a deck.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.