training-report

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Training Report

培训报告

Iterate the full report in Markdown first. Generate the .docx last, once, when the content is final. The .md is the canonical artifact; the .docx is a terminal derivative.

Discipline-agnostic: coding workshop, leadership seminar, safety training, onboarding, creative workshop — all apply equally.

Voice mode: this conversation may be conducted by voice. Transcription can introduce homophones, missing punctuation, or ambiguous proper nouns (names, company names, tool names). If any answer is unclear after transcription, ask a short clarifying question before moving on — do not guess.

先以Markdown格式完成完整报告的迭代。仅当内容最终确定后，再生成**.docx文件**。.md文件是标准文件，.docx是最终衍生文件。

适用于所有领域：编程研讨会、领导力讲座、安全培训、入职培训、创意工作坊等，均同等适用。

语音模式说明：本次对话可通过语音进行。转录可能会出现同音词、标点缺失或专有名词（姓名、公司名称、工具名称）模糊的情况。如果转录后的内容存在不明确之处，请先提出简短的澄清问题，再继续处理——切勿猜测。

Reference files

参考文件

Load these files at the steps indicated. Do not load them all upfront.

File	Load at
`references/tone-of-voice.md`	Step 1 (after language + audience confirmed)
`references/markdown-draft.md`	Step 5 (before writing the draft)
`references/docx-generation.md`	Step 6 (before generating the .docx)

在指定步骤加载以下文件，请勿提前全部加载。

文件	加载时机
`references/tone-of-voice.md`	步骤1（确认语言和受众后）
`references/markdown-draft.md`	步骤5（撰写草稿前）
`references/docx-generation.md`	步骤6（生成.docx前）

Step 0 — Check dependencies

步骤0 — 检查依赖项

Before asking the user anything, verify skill availability.

docx
skill (required for Step 6)

If found: note it; load it at Step 6
If not found: warn the user — it is required to generate the final Word document and can be installed from Anthropic's official skill library. Offer to proceed with the Markdown draft in the meantime.

Humanizer skill (recommended)

After Step 1, look for a humanizer skill matching the chosen language
If found: load it and apply it during the humanization pass in Step 5
If not found: tell the user once, then fall back to inline humanization rules (Step 5b). Suggest installing a humanizer skill for the chosen language.

在向用户提问之前，先验证技能可用性。

docx
技能（步骤6必需）

若已找到：记录下来；在步骤6加载
若未找到：向用户发出警告——该技能是生成最终Word文档的必需项，可从Anthropic官方技能库安装。同时提议先继续完成Markdown草稿。

Humanizer技能（推荐使用）

步骤1之后，查找与所选语言匹配的Humanizer技能
若已找到：加载该技能，并在步骤5的人性化处理阶段应用
若未找到：告知用户一次，然后退而使用内置人性化规则（步骤5b）。建议用户安装对应语言的Humanizer技能。

Step 1 — Language & audience

步骤1 — 语言与受众

Ask:

"In what language should I write the report? (French / English / other)"
"Who is the primary reader? (executive / HR / direct management / external client / internal archive)"

Then load

references/tone-of-voice.md

and apply its guidance throughout.

询问：

"报告应使用哪种语言撰写？（法语/英语/其他）"
"主要读者是谁？（高管/人力资源/直属管理层/外部客户/内部存档）"

随后加载

references/tone-of-voice.md

，并全程遵循其指导。

Step 2 — Template

步骤2 — 模板

Ask:

"Do you have a Word (.docx) template for this report? (company header/footer, logo, branded fonts, color scheme)"

Yes → ask them to upload it; use it as the base at Step 6 (unpack/inject/repack)
No → proceed with a clean document; ask for a brand color before defaulting to blue
```
#2E75B6
```

询问：

"您是否有此报告的Word（.docx）模板？（包含公司页眉/页脚、logo、品牌字体、配色方案）"

是 → 请用户上传模板；在步骤6中以此为基础进行处理（解压/注入内容/重新打包）
否 → 使用空白文档继续；在默认使用蓝色
```
#2E75B6
```
之前，先询问品牌配色

Step 3 — Interview

步骤3 — 访谈

Conduct a structured interview in batches. Wait for answers before moving on. Extract what the user already told you from the conversation before asking.

分批次进行结构化访谈。等待用户回答后再进入下一环节。先从对话中提取用户已告知的信息，再提出问题。

Batch A — Session metadata

批次A — 课程元数据

Trainer name and role
Date, location, company/team name
Duration
Total number of participants
Confirm or refine: who is the document for?

培训师姓名及职位
日期、地点、公司/团队名称
时长
参与者总人数
确认或细化：文档的受众是谁？

Batch B — Session context

批次B — 课程背景

Stated goal of the training
Subject, topic, tool, or material used as practical support
Any rules or constraints set at the start
Materials, accounts, licenses, or equipment provided to participants

培训的既定目标
作为实践支撑的主题、话题、工具或材料
课程开始时设定的任何规则或限制
向参与者提供的材料、账户、许可证或设备

Batch C — Starting levels

批次C — 初始水平

Distribution of familiarity across the group (any beginners? any experts?)
Notable outliers at either end

群体中对主题的熟悉程度分布（是否有初学者？是否有专家？）
两端的突出特例

Batch D — Session walkthrough

批次D — 课程流程梳理

Walk through the session step by step. For each step:

Objective
What participants actually did
Materials, tools, or exercises involved
First exposure to this concept or not
How it landed; any difficulties

Probe until complete: "What happened next?", "Did anything go differently than planned?", "Were there any pivots?"

逐步梳理课程流程。针对每个步骤：

目标
参与者实际完成的内容
涉及的材料、工具或练习
是否是首次接触该概念
接受情况；遇到的任何困难

追问直至信息完整："接下来发生了什么？"、"是否有与计划不同的地方？"、"是否有调整过流程？"

Batch E — Deliverables

批次E — 产出成果

Ask: "Did participants produce anything during the session?"

Probe for:

Documents, files, diagrams, prototypes, or any output created during exercises
Collaborative work produced as a group
Individual work produced autonomously
Anything left incomplete or started but not finished

These may appear in the Annexes and/or be referenced in the Session Walkthrough.

询问："参与者在课程中是否产出了任何成果？"

追问以下内容：

练习中创建的文档、文件、图表、原型或任何输出
团队协作完成的成果
个人独立完成的成果
未完成或已开始但未结束的内容

这些内容可放入附录，或在课程流程梳理部分中提及。

Batch F — General observations

批次F — 总体观察

Overall energy and engagement of the group
Any incidents, surprises, or notable moments
Schedule: did it hold, or were sections cut/extended?
Logistical issues (room, materials, setup)

General Observations is optional. If the trainer has nothing notable to add beyond the walkthrough, skip this section entirely.

群体的整体活力与参与度
任何事件、意外或值得关注的时刻
日程：是否按计划进行，还是有部分内容被删减/延长？
后勤问题（场地、材料、设备设置）

总体观察为可选内容。如果培训师除流程梳理外没有其他值得提及的内容，可完全跳过此部分。

Batch G — Individual feedback

批次G — 个人反馈

Ask: "Do you have specific observations for any individual participant?"

For each named participant, extract:

Role or background
Starting level
Behavior/engagement (positive and negative)
Notable evolution, breakthrough, or resistance
How they ended the session

Individual Feedback is optional. Only write it if the trainer explicitly provides meaningful observations. Do not prompt for feedback on every participant.

Be diplomatic. Describe behaviors, not character. Name problems factually; do not editorialize. When writing for an external client about a team you don't know, consider whether naming individuals is appropriate at all.

See

references/tone-of-voice.md

— Diplomatic framing section.

询问："您是否对特定参与者有具体观察？"

针对每个被提及的参与者，提取以下信息：

职位或背景
初始水平
行为/参与度（正面和负面）
显著的进步、突破或抵触情绪
课程结束时的状态

个人反馈为可选内容。仅当培训师明确提供有意义的观察时才撰写此部分。无需要求对每位参与者都提供反馈。

措辞需委婉。描述行为而非性格。如实指出问题；不要发表主观评论。当为外部客户撰写关于陌生团队的报告时，需考虑提及个人姓名是否合适。

请参阅

references/tone-of-voice.md

中的“委婉措辞”部分。

Batch H — Recommendations & next steps

批次H — 建议与后续步骤

Ask: "What would you recommend to the direction/client to build on this session?"

Probe for:

Resources and access to provide (licenses, books, platforms, communities)
Practices to anchor in daily work
What to pace carefully — basics before advanced material
Follow-up sessions (refresher, coaching, Q&A after a few weeks)
Assessment and validation (quiz, practical challenge, peer review, checklist)
Knowledge-sharing rituals (Slack/Teams channel, recurring meeting, Loom demos, buddy system, monthly show-and-tell)
Management involvement (protect practice time, 1:1 check-ins, celebrate wins)
External resources (books, courses, certifications) for self-driven participants
Specific warnings or caveats for management

询问："您对管理层/客户有哪些基于本次课程的建议？"

追问以下内容：

需提供的资源与权限（许可证、书籍、平台、社群）
需融入日常工作的实践方法
需循序渐进的内容——先掌握基础再学习进阶内容
后续课程（复习、辅导、几周后的问答环节）
评估与验证方式（测验、实践挑战、同行评审、检查清单）
知识分享机制（Slack/Teams频道、定期会议、Loom演示、结对互助、月度成果展示）
管理层的参与（保障实践时间、一对一沟通、庆祝成果）
供自主学习参与者使用的外部资源（书籍、课程、认证）
需向管理层提出的特定警告或注意事项

Batch I — Annexes

批次I — 附录

Ask: "Do you have any annexes to attach to the report?"

Annexes can include:

Photos from the session
Satisfaction survey results (NPS, ratings, verbatim comments)
Slides or handouts distributed during the session
Work produced by participants (exercises, prototypes, documents, diagrams)
Reference documents used during the session
Any other supporting material

For each annex:

Image → attempt auto-embed at Step 6
File (PDF, slides, spreadsheet) → reference in the Annexes section; do not embed
Survey data → synthesize in Step 4, then include as a dedicated section in the doc
Participant deliverable → reference in the relevant Walkthrough step AND in Annexes

询问："您是否有需要附加到报告中的附录内容？"

附录可包括：

课程照片
满意度调查结果（NPS评分、等级评价、原话反馈）
课程中分发的幻灯片或讲义
参与者完成的作业（练习、原型、文档、图表）
课程中使用的参考文档
其他任何支持材料

针对每个附录：

图片 → 在步骤6中尝试自动嵌入
文件（PDF、幻灯片、电子表格）→ 在附录部分提及；不嵌入
调查数据 → 在步骤4中进行整合，然后在文档中设置专门章节
参与者成果 → 在相关的流程梳理步骤中提及，同时放入附录

Batch J — Closing & contact

批次J — 结束语与联系方式

Ask: "May I include a closing note thanking the team for the invitation, and your contact details for future collaboration? (email + phone)"

If yes: collect name, email, phone. The closing is written in the document language, personal in tone, brief. See

references/markdown-draft.md

— Closing paragraph section.

询问："我是否可以在报告中加入感谢团队邀请的结束语，以及您用于未来合作的联系方式？（邮箱+电话）"

若同意：收集姓名、邮箱、电话。结束语需使用文档语言，语气亲切简洁。请参阅

references/markdown-draft.md

中的“结束语段落”部分。

Step 4 — Feedback synthesis (if survey data provided)

步骤4 — 反馈整合（若提供调查数据）

Produce a synthesis in the conversation before drafting:

Overall score / NPS
Rating distribution
Top 3 positive themes
Top 3 areas for improvement
Any outlier responses

Ask the user to confirm before it enters the document.

在撰写草稿前，先在对话中生成整合内容：

总体评分/NPS
评分分布
排名前三的正面主题
排名前三的改进方向
任何异常反馈

请用户确认后再将内容纳入文档。

Step 4b — Confirm outline

步骤4b — 确认大纲

Here's what I'll draft:
1. Context
2. Starting Levels
3. Session Walkthrough (N steps)
4. General Observations         [optional — include if trainer provided content]
5. Participant Satisfaction     [only if survey data provided]
6. Individual Feedback          [optional — include if trainer provided feedback]
7. Recommendations & Next Steps
8. Annexes                      [only if annexes provided]
[Closing + contact]

Language: [language] | Audience: [target] | Template: [yes/no]

Ask: "Anything to adjust before I start the draft?"

以下是我将撰写的草稿大纲：
1. 背景
2. 初始水平
3. 课程流程梳理（共N步）
4. 总体观察         [可选——仅当培训师提供相关内容时包含]
5. 参与者满意度     [仅当提供调查数据时包含]
6. 个人反馈          [可选——仅当培训师提供反馈时包含]
7. 建议与后续步骤
8. 附录              [仅当提供附录内容时包含]
[结束语+联系方式]

语言：[语言] | 受众：[目标群体] | 模板：[是/否]

询问："开始撰写草稿前，是否需要调整任何内容？"

Step 5 — Markdown draft

步骤5 — Markdown草稿

Load
references/markdown-draft.md
before writing. It contains the full section-by- section writing guide, Markdown limitations, HTML table workarounds, and closing paragraph guidance.

撰写前请加载
references/markdown-draft.md
。该文件包含分章节的完整撰写指南、Markdown限制说明、HTML表格解决方案及结束语撰写指导。

Humanization pass

人性化处理

Before presenting the draft, apply the humanizer skill (loaded in Step 0). If no humanizer skill is available, apply these rules inline:

Cut all AI throat-clearing openers and sentence starters
Cut adjective doublets — pick the more precise word
Replace passive voice with active wherever natural
Replace vague praise or criticism with specific behaviors or facts
Short sentences over long ones
Adapt to the document language (see
```
references/tone-of-voice.md
```
)

Do not present an un-humanized draft.

在展示草稿前，应用Humanizer技能（步骤0中加载的技能）。若没有可用的Humanizer技能，则直接应用以下规则：

删除所有AI式的开场白和句子开头
删除重复形容词——选择更精准的词汇
尽可能将被动语态改为主动语态
用具体行为或事实替代模糊的表扬或批评
优先使用短句而非长句
根据文档语言调整措辞（请参阅
```
references/tone-of-voice.md
```
）

请勿展示未经过人性化处理的草稿。

Iteration loop

迭代循环

Present the draft inline in the conversation. Let the user lead. Update the

.md

file for every change. One canonical file, no versions. Only move to Step 6 when the user explicitly confirms the content is final.

在对话中直接展示草稿。由用户主导修改。每次修改后更新

.md

文件。仅保留一份标准文件，不保留版本。仅当用户明确确认内容最终确定后，再进入步骤6。

Step 6 — Final .docx generation

步骤6 — 最终.docx生成

Load
references/docx-generation.md
and the
docx
skill before starting.

This step runs once. It is terminal: if the user requests changes after the .docx is generated, update the

.md

and regenerate from scratch.

Deliver both files. If the environment supports inline file delivery (e.g.

present_files

on Claude.ai), use it. Otherwise, print the absolute paths to both files.

开始前请加载
references/docx-generation.md
和
docx
技能。

此步骤仅执行一次，为最终步骤：若用户在生成.docx后请求修改，需先更新

.md

文件，再重新生成.docx。

交付两个文件。若环境支持直接交付文件（如Claude.ai的

present_files

功能），则使用该功能。否则，打印两个文件的绝对路径。

Pitfalls

注意事项

Don't fabricate details — only document what the trainer explicitly provided
Don't editorialize in General Observations — factual only
Don't write Individual Feedback unless explicitly provided — and stay diplomatic
Don't pad recommendations — 6 sharp ones beat 12 vague ones
Always include a Pacing recommendation in the Next Steps
This skill is not developer-specific — adapt vocabulary to the discipline
Never generate the .docx mid-conversation — Markdown is the draft stage
Never skip an annex or image — embed, reference, or placeholder

切勿编造细节——仅记录培训师明确提供的内容
在总体观察部分切勿发表主观评论——仅记录事实
仅当明确提供反馈时才撰写个人反馈部分——且需保持委婉
建议内容切勿冗长空洞——6条精准建议胜过12条模糊建议
在后续步骤中务必包含进度安排建议
此技能并非仅针对开发者——需根据领域调整词汇
切勿在对话过程中生成.docx——Markdown为草稿阶段
切勿遗漏任何附录或图片——需嵌入、提及或设置占位符