360 Secure SkillHub
360 安全技能中心

Cross Team Plain Language

该 Skill 将零散、情绪化、过于内部化或术语密集的原始想法，按目标受众（老板、产品、工程、运营、跨职能群聊）改写为清晰、易回应、易转发的表达，显式呈现诉求，并保持“现象→影响→建议/请求”的因果；可按需给出更短、更正式或更柔和的多个版本。信息不足时会指出缺失项并只追问最小必要信息。

nickzhangai
nickzhangai
热度 55.97
最近更新 2026-05-11 17:33:17
分类：效率依赖：纯提示词应用场景：摘要总结 / 邮件起草 / 模板

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add cross-team-plain-language
Metadata
name
cross-team-plain-language
description
Rewrite messy, internal, emotional, or jargon-heavy thoughts into clear language that other teams can immediately understand and respond to. Use when the user says things like “我知道我要表达什么，但不会写成别人能接住的话”, wants to explain context to product/ops/engineering/bosses, needs a summary others can follow, or wants multiple tones such as concise, formal, or chat-friendly.

Cross Team Plain Language

Turn raw thoughts into language other people can catch, understand, and continue.

Core Job

Take material that is:

  • scattered
  • emotionally loaded
  • too insider-ish
  • too technical for the audience
  • technically correct but socially hard to receive

Then rewrite it into a version that is:

  • easier to understand
  • easier to reply to
  • easier to forward
  • aligned to the audience's concerns

Workflow

  1. Identify the audience.
    • boss / leadership
    • product
    • engineering
    • operations / customer success
    • cross-functional group chat
  2. Extract the real message.
    • what happened
    • why it matters
    • what decision or response is needed
  3. Remove blockers.
    • jargon without explanation
    • emotional venting that hides the point
    • overly long setup
    • claims that are hard to act on
  4. Rebuild the message in plain language.
  5. Offer 2-4 variants when useful:
    • short chat version
    • formal update version
    • structured bullet version
    • push-without-sounding-pushy version

Output Pattern

Default to this structure unless the user asks otherwise:

  1. 你原本想表达的核心
  2. 别人更容易接住的版本
  3. 如果要更短/更正式/更柔和，可以改成

Editing Rules

  • Preserve intent, not exact wording.
  • Prefer concrete nouns over abstract phrases.
  • Replace insider shorthand with terms outsiders understand.
  • Surface the ask explicitly.
  • Keep causality clear: “现象 → 影响 → 建议/请求”.
  • If the user sounds frustrated, keep the force but reduce the splash damage.

Good Delivery Shapes

A. Cross-team alignment

Use when the goal is shared understanding.

目前看到的问题是……
它带来的影响是……
我建议下一步先……

B. Friendly but useful group-chat summary

Use when the message should feel natural, not like a memo.

我先帮大家收一下：
现在讨论里比较集中的点是……
如果按优先级看，我会先……

C. Decision-ready summary

Use when the reader needs to decide or allocate resources.

这不是单点反馈，而是一个模式：……
当前最优先要解决的是……
后续再扩展……

When To Push Back

If the source material is too vague, say what is missing instead of pretending clarity exists. Ask only for the minimum missing piece, such as:

  • audience
  • desired tone
  • whether the user wants explanation, persuasion, or status update

References

  • See references/patterns.md for rewrite patterns and before/after templates.