Training Report

Turns your post-workshop brain dump into a polished Word document. It walks you through a structured interview covering session metadata, what actually happened minute by minute, individual participant observations, and follow-up recommendations. The skill loads reference files for tone and formatting as it goes, checks for a docx generation dependency, and can work with your branded template if you have one. It drafts everything in Markdown first so you can review before committing to the final .docx. Works across any training discipline, from coding bootcamps to compliance sessions. Voice mode friendly, with built-in clarification prompts for transcription errors.

skills.sh installs: 5K
GitHub stars: 242
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add samber/cc-skills --skill training-report --agent claude-code

Installs into .claude/skills of the current project.

Files

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)