AI Agent Hub
Back to skills
Workplace Communication Scenario Simulator icon

Workplace Communication Scenario Simulator

Education Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please install @user_fa14b5bc/workplace-communication by following the guide at https://skillhub.cn/install/skillhub.md.

About this skill

Problem It Addresses

Many workplace communication failures are not about “not knowing what to say,” but about lacking reusable structure: progress reports reduce to “it’s coming soon,” refusals become “can’t do it,” and meeting objections trigger defensiveness or silence. Workplace Communication Scenario Simulator targets these high-frequency situations for engineers and managers, using fictional cases to practice upward management, peer collaboration, meeting delivery, written communication, and downward management.

How It Works

The skill starts by confirming the communication direction, then works through a concrete scenario:
- Common mistake: shows low-information, emotional, or blame-shifting phrasing and explains why it fails.
- Recommended approach: provides a 3–5 sentence script, such as conclusion + progress + risk + time expectation + escalation path.
- Strategy analysis: breaks down moves like empathy, quantifying the gap, offering choices, and involving the listener in the decision.
It treats scripts as references rather than rigid templates that must fit real relationships and authority boundaries. Its anomaly handling also asks users to abstract strong emotions or identifying details into a discussable scenario type, rather than commenting on real people or companies.

Boundaries

It is useful for rehearsing progress reporting, resource requests, pushing back on unreasonable asks, cross-team follow-up, and performance feedback. It does not encourage manipulative workplace tactics, and it should not be used to craft conflict scripts aimed at specific real individuals or organizations; if the case falls outside the five directions, the skill states its boundary and only adapts when the pattern can be generalized.

Use Cases

  • Report project status to a manager with conclusion, risks, timing, and fallback.
  • Chase cross-team support by proposing a low-effort review and letting them choose timing.
  • Give a peer private feedback on a flawed plan using acknowledgment and specific data.
  • Tell a subordinate their promotion was denied, explain directly, validate effort, and point to a new direction.

Best For

  • Engineers who need to report project risks and request resources from managers.
  • Product or engineering leads chasing cross-team sign-off on interfaces or requirements.
  • New managers who need to deliver performance feedback or bad news to direct reports.
  • Technical owners who must write status emails, weekly reports, and retro notes without sounding like a log.