/training-report

name: training-report
description: 'Produce a professional training/workshop report as a .docx file. Use this skill whenever the user mentions "training report", "workshop report", "compte rendu", "compte rendu de formation", "formation report", "debriefing a workshop", "write up a training session", "résumé de formation", or any request to document a training session, workshop, or onboarding event with individual participant feedback and recommendations. Also trigger when the user says things like "I just ran a workshop and need to write it up", "help me summarize what happened in my training session", or "I need to report back to management about a session I ran". Always use this skill — for short or long sessions, across any discipline (technical, soft skills, creative, compliance, onboarding, etc.) — whenever a structured written deliverable about a training event is needed.'
user-invocable: true
license: MIT
compatibility: Designed for Claude or similar AI agents.
metadata:
  author: samber
  version: "1.0.1"
  openclaw:
    emoji: "📚"
    homepage: https://github.com/samber/cc-skills
allowed-tools: Read Edit Write Glob Grep Agent AskUserQuestion

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.

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) |

Step 0 — Check dependencies

**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.

Step 1 — Language & audience

Ask:

1. "In what language should I write the report? (French / English / other)" 2. "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.

Step 2 — Template

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`

Step 3 — Interview

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

• 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

• 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

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

Batch D — Session walkthrough

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

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

• 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

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