New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Training and Workshop Report

by samber in samber/cc-skills

Produces a training or workshop report as a Word file, with participant feedback and recommendations, drafted in Markdown first and converted once at the end.

MITAuto-check passedDocuments & Office

Install Training and Workshop Report

skills CLI
$ npx skills add samber/cc-skills --skill training-report -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install samber/cc-skills training-report --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/samber/cc-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/training-report .claude/skills/training-report && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
training-report
GitHub stars
228
Token cost
~2.7k tokens
SKILL.md length
1,266 words
Files
5 (incl. references)
Skills in repo
16
Repo updated
First seen
Licence
MIT

At a glance

Produces a training or workshop report as a Word file, with participant feedback and recommendations, drafted in Markdown first and converted once at the end.

  • Works in 7 steps: Check dependencies → Language & audience → Template → …
  • Writing up a workshop you just ran for management
  • SKILL.md covers Reference files, Step 0 — Check dependencies, Step 1 — Language & audience and Step 2 — Template, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

This skill produces a written report on a training session or workshop, with feedback and recommendations for each participant, as a Word file. It works in Markdown first and generates the .docx once at the end, when the content is final, so the Markdown stays the canonical version. It applies to any discipline, from coding workshops and leadership seminars to safety training and onboarding, and it can run in a voice conversation by asking short follow-ups when a transcription is unclear.

The process starts by checking that the `docx` skill is available, which the final step needs, and looking for a humanizer skill in the chosen language. It then asks which language to write in and who will read the report (executive, HR, direct management, external client or internal archive), asks whether you have a Word template with a company header, logo and fonts, and runs a structured interview in batches, using what you already said first. A Markdown draft with a humanizing pass follows, then the Word document.

Three reference files are loaded only at the step that needs them: tone of voice, Markdown draft structure and .docx generation. If no template is supplied, the document uses a clean layout and asks for a brand color before falling back to a default blue. An `evals/evals.json` file is included.

When your agent uses it

  • Writing up a workshop you just ran for management
  • Documenting a training session with feedback for each participant
  • Producing a French or English training report as a Word file
  • Summarizing an onboarding event with recommendations

Example prompts

  • “I just ran a two-day Go workshop for the platform team and need to write it up for my manager.”
  • “Help me produce a compte rendu de formation on last week's safety training.”
  • “Turn my notes on the leadership seminar into a report with feedback for each participant, using our company template.”

Requirements

  • The `docx` skill, needed to generate the final Word document
  • A Word template, if you want company branding
  • Compatibility (from SKILL.md): Designed for Claude or similar AI agents.
  • Pre-approved tools (allowed-tools): Read, Edit, Write, Glob, Grep, Agent, AskUserQuestion

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Check dependencies
  2. Language & audience
  3. Template
  4. Interview
  5. Feedback synthesis (if survey data provided)
  6. Markdown draft
  7. Final .docx generation

What it can do on your machine

Read from SKILL.md and the folder at commit 123cb15. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Edit
    • Write
    • Glob
    • Grep
    • Agent
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude or similar AI agents.

    From compatibility in the SKILL.md frontmatter.

Context cost

Training and Workshop Report loads about 2.7k tokens when it runs, and up to ~8.6k if it reads all its reference files. Until then it costs about 218 tokens; SKILL.md has 1,266 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~218
When it runs · the whole SKILL.md, loaded when a task matches
~2.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~8.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from samber/cc-skills at commit 123cb15, republished under its MIT licence (© samber). 1,266 words, ~2,715 tokens.

Download SKILL.mdSave it as .claude/skills/training-report/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
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.
allowed-tools
Read, Edit, Write, Glob, Grep, Agent, AskUserQuestion
compatibility
Designed for Claude or similar AI agents.
user-invocable
true
license
MIT
metadata.author
samber
metadata.version
1.0.1

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.

FileLoad at
references/tone-of-voice.mdStep 1 (after language + audience confirmed)
references/markdown-draft.mdStep 5 (before writing the draft)
references/docx-generation.mdStep 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 know, consider whether naming individuals is appropriate at all.

See references/tone-of-voice.md — Diplomatic framing section.

Batch H — Recommendations & next steps

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
Show full SKILL.md (482 more words)Show less
Batch I — Annexes

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
Batch J — Closing & contact

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.

Step 4 — Feedback synthesis (if survey data provided)

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.

Step 4b — Confirm outline

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?"

Step 5 — Markdown draft

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.

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.

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.

Step 6 — Final .docx generation

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.

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

© samber, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/training-report of samber/cc-skills.

  • SKILL.md
  • evals/evals.json
  • references/docx-generation.md
  • references/markdown-draft.md
  • references/tone-of-voice.md

Open the folder on GitHubat commit 123cb15

Compare with similar skills

Training and Workshop Report next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Training and Workshop Report compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Training and Workshop Report this skillsamber/cc-skills228—~2.7kAutomated safety check: PassMIT
Industry Bid Document WriterGet00/BiaoShu-SKILL172—~4.6kAutomated safety check: PassApache-2.0
Chinese Official Document Draftingzhaohui-yang/official-document-drafting140—~1.5kAutomated safety check: PassMIT
Hermes3000 WritingHybridAIOne/hybridclaw158—~2.7kAutomated safety check: PassMIT
Ministry News Daily Reportzhaohui-yang/official-document-drafting140—~555Automated safety check: PassCustom licence
Word Document Reader and WriterHKUDS/DeepTutor41k—~2.5kAutomated safety check: PassApache-2.0

Similar skills

  • Industry Bid Document Writer

    Get00/BiaoShu-SKILL

    Converts a tender document into Markdown, extracts scoring criteria and requirements, then drafts an industry-formatted technical bid as a Word file.

    172 GitHub stars~4.6k tokensUpdated 15 days ago
    Documents & OfficeAuto-check passed

  • Chinese Official Document Drafting

    zhaohui-yang/official-document-drafting

    Drafts, rewrites and standardizes Chinese official documents and formal reports such as notices, requests and meeting minutes, and exports the result to Word.

    140 GitHub stars~1.5k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check passed

  • Hermes3000 Writing

    HybridAIOne/hybridclaw

    Use Hermes3000 to plan, draft, revise, save, check consistency, and export long-form manuscripts through the Hermes3000 AI writing portal API.

    158 GitHub stars~2.7k tokensUpdated today
    Documents & OfficeAuto-check passed

  • Ministry News Daily Report

    zhaohui-yang/official-document-drafting

    Collects the latest updates from Chinese central ministry websites and drafts a daily formal report on them, optionally exported to Word.

    140 GitHub stars~555 tokensUpdated 1 mo ago
    Documents & OfficeAuto-check passed

  • Word Document Reader and Writer

    HKUDS/DeepTutor

    Reads, creates and edits Word .docx files with python-docx, and drops to raw OOXML for tracked changes, comments and byte-exact edits.

    41k GitHub stars~2.5k tokensUpdated yesterday
    Documents & OfficeAuto-check passed

  • BiSheng DOCX Builder

    dataelement/bisheng

    Builds or edits Word .docx documents inside BiSheng's code executor with python-docx, handling Chinese fonts, tables of contents, page numbers and official-document layout.

    12k GitHub stars~2.6k tokensUpdated today
    Documents & OfficeAuto-check passed

More from samber/cc-skills

All 16 skills in this repo

  • End-of-Article CTA Designer

    samber/cc-skills

    Interviews you about objective, audience and context, then designs an end-of-article call to action with copy, placement, A/B test plan and accessibility check.

    228 GitHub stars~3.1k tokensUpdated 8 days ago
    Auto-check passed

  • Prose Style Guide Creator

    samber/cc-skills

    Builds a PROSE.md writing guide that captures how a person or brand writes, such as vocabulary, sentence rhythm and signature moves, separate from emotional tone.

    228 GitHub stars~5.3k tokensUpdated 8 days ago
    Auto-check passed

  • Press Release Writer

    samber/cc-skills

    Drafts press releases that fit the release type, target media and region, after collecting the facts and checking that the story has a real news angle.

    228 GitHub stars~1.8k tokensUpdated 8 days ago
    Auto-check passed

  • Site Launch Checklist

    samber/cc-skills

    Pre-launch checklist for shipping a new website or web app. An agent skill from samber/cc-skills.

    228 GitHub stars~13k tokensUpdated 8 days ago
    Auto-check: notes

  • Conventional Git

    samber/cc-skills

    Conventional Commits v1.0.0 branch naming, worktree naming, and commit message standards for GitHub and GitLab projects.

    228 GitHub stars~1.8k tokensUpdated 8 days ago
    Auto-check passed

  • Copywriting Hooks

    samber/cc-skills

    Writes opening hooks and post titles for long-form articles in EN or FR — blog posts, Substack/Medium/dev.to, LinkedIn long-form, newsletters, essays.

    228 GitHub stars~6.8k tokensUpdated 8 days ago
    Auto-check passed

Works with

Categories

Questions about Training and Workshop Report

What does Training and Workshop Report do?

Produces a training or workshop report as a Word file, with participant feedback and recommendations, drafted in Markdown first and converted once at the end. This skill produces a written report on a training session or workshop, with feedback and recommendations for each participant, as a Word file.docx once at the end, when the content is final, so the Markdown stays the canonical version.

When should I use Training and Workshop Report?

Training and Workshop Report fits situations like: writing up a workshop you just ran for management; documenting a training session with feedback for each participant; producing a French or English training report as a Word file; summarizing an onboarding event with recommendations.

How do I install Training and Workshop Report in Claude Code?

Run `npx skills add samber/cc-skills --skill training-report -a claude-code`. Or copy the skill folder (skills/training-report in samber/cc-skills) into .claude/skills/training-report in your project. Claude Code loads it when a task matches its description.

How do I install Training and Workshop Report in Codex?

Run `npx skills add samber/cc-skills --skill training-report -a codex`. Or copy the skill folder (skills/training-report in samber/cc-skills) into .agents/skills/training-report in your project. Codex loads it when a task matches its description.

Can I use Training and Workshop Report in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add samber/cc-skills --skill training-report -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/training-report, .gemini/skills/training-report, .github/skills/training-report and .opencode/skills/training-report in your project.

What does Training and Workshop Report need to run?

SKILL.md names no scripts, command-line tools or credentials: Training and Workshop Report is instructions for the agent only. Our summary lists: The `docx` skill, needed to generate the final Word document; A Word template, if you want company branding. Its frontmatter pre-approves these tools: Read, Edit, Write, Glob, Grep, Agent, AskUserQuestion. Compatibility (from SKILL.md): Designed for Claude or similar AI agents..

Does Training and Workshop Report access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Training and Workshop Report safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Training and Workshop Report use?

Training and Workshop Report is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Training and Workshop Report use?

About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.9k tokens, read only when the agent opens those files.

What are the alternatives to Training and Workshop Report?

Skills that share tags, products or a category with Training and Workshop Report: Industry Bid Document Writer (Get00/BiaoShu-SKILL, 172 stars), Chinese Official Document Drafting (zhaohui-yang/official-document-drafting, 140 stars), Hermes3000 Writing (HybridAIOne/hybridclaw, 158 stars) and Ministry News Daily Report (zhaohui-yang/official-document-drafting, 140 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Training and Workshop Report?

samber (a GitHub user) maintains it in samber/cc-skills, which has 228 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 1, 2026.

Source: samber/cc-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.