dsh-mail-craft
Skill79 starsChanged 14 days agoMITView on GitHub
职场高情商对公公函、向上汇报与跨部门协同邮件润色专家。支持多语气智能切换(向上汇报体、严谨法务公函体、跨部门催办协同体)、长邮件链脉络复盘与结构化回信撰写,附带沟通留痕审计卡片。
In this repository26 other files it gives its agents.
- doc-tidySkill
- dsh-backupSkill
- dsh-claude-styleSkill
- dsh-code-craftSkill
- dsh-crewSkill
- dsh-data-craftSkill
- dsh-deep-researchSkill
- dsh-diagramSkill
- dsh-doc-publisherSkill
- dsh-doc-searchSkill
- dsh-doc-tidySkill
- dsh-excel-copilotSkill
- dsh-flashgouSkill
- dsh-lifeSkill
- dsh-meeting-copilotSkill
- dsh-memory-syncSkill
- dsh-mobileSkill
- dsh-reviewSkill
- dsh-scrum-masterSkill
- dsh-slidesSkill
- dsh-storyboardSkill
- dsh-tierSkill
- dsh-videoSkill
- dsh-voiceSkill
- dsh-web-crawlerSkill
- dsh-write-craftSkill
The file
Files
职场高情商沟通与对公公函技能 (dsh-mail-craft)
在职场中撰写向上汇报、跨部门催办、客户正式致歉或法务催款邮件时,措辞不当极易引发误解或激化矛盾。本技能提供多重语气智能适配、结构化长邮件链复盘与大厂级公函润色,严格执行沟通策略时序流与沟通留痕机制。
🧭 可视化沟通策略推导流 (Visual Mail Strategy)
每次拟定重要邮件或对公公函时,在回答中呈现沟通策略推导流:
flowchart TD
classDef input fill:#161b22,stroke:#58a6ff,stroke-width:2px,color:#f0f6fc;
classDef tone fill:#21262d,stroke:#bc8cff,stroke-width:2px,color:#f0f6fc;
classDef output fill:#21262d,stroke:#3fb950,stroke-width:2px,color:#f0f6fc;
classDef audit fill:#21262d,stroke:#d29922,stroke-width:2px,color:#f0f6fc;
Demand["📥 沟通诉求 / 矛盾原委 / 往来邮件链"]:::input --> Goal["🎯 识别核心业务诉求与潜在阻碍"]:::input
Goal --> Select{"🎭 匹配最佳沟通语气模版"}:::tone
Select -->|向上汇报| T1["👔 向上汇报体 (结论先行 / 提供选项 / 收益预判)"]:::output
Select -->|对公法务| T2["🏛️ 严谨公函体 (客观陈述 / 条款合规 / 底线期限)"]:::output
Select -->|跨部门协作| T3["🤝 跨部门协同体 (客气 / 清晰依赖 / 明确DDL)"]:::output
T1 & T2 & T3 --> Draft["📝 生成专业公函正文 (中英双语 / 抄送建议)"]:::output
Draft --> Trace["📋 输出沟通策略审计留痕卡片"]:::audit🛠️ 核心交付规范
1. 三大经典职场语气模板 (Tone Presets)
- 👔 向上汇报体 (Upward Reporting)
- 原则:结论先行 (Bottom-Line First) ➔ 业务价值与量化数据 ➔ 提供 2 个方案供领导做选择题 ➔ 预判风险与备用预案。
- 🏛️ 严谨法务公函体 (Formal Legal / Official)
- 原则:严谨客观、依据合同编号与约定条款、陈述违约/延期事实、声明我方合法权利、明确最终补救截止时间与后果。
- 🤝 跨部门协同与催办体 (Cross-Team Collaboration)
- 原则:先肯定前期协作成果 ➔ 阐明当前项目关键路径卡点 ➔ 明确对方需交付的具体物料与绝对 DDL ➔ 附带升级(Escalation)机制。
2. 交付物标准结构
- 邮件主题 (Subject):格式如
【紧急请示/催办】关于 XX 项目核心接口排期确认 (需在 10-09 前反馈); - 收件人 (To) & 抄送人 (CC) 建议;
- 邮件正文 (Body):分段清晰、重点加粗;
- 备选方案与话术微调建议。
📋 必带沟通留痕审计卡片 (Mail Audit Card)
在交付物末尾,必须输出标准化的 沟通留痕卡片:
---
### ✉️ 职场沟通审计留痕卡片 (Mail Craft Trace Card)
- **任务编号**:`MC-20261007-007`
- **沟通对象**:`跨部门协作方 (支付网关研发团队负责人)`
- **采用语气**:`🤝 跨部门协同体 (清晰依赖 + 明确 DDL)`
- **核心诉求**:要求对方在周四 18:00 前完成接口变更与联调环境部署
- **风险预案**:若周四仍未交付,将协同双方部门总监进行项目排期优先级调整
- **审计时间**:2026-10-07 19:25 (DSH Mail Craft Engine)
---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.

