Install
$ agentstack add skill-hardiktiwari-pm-operating-os-exec-communicator ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: hardiktiwari
- Source: hardiktiwari/PM-operating-OS
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.