training-report
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.
git clone --depth 1 https://github.com/samber/cc-skills /tmp/training-report && cp -r /tmp/training-report/skills/training-report ~/.claude/skills/training-reportSKILL.md
# 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 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 ### 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
Comprehensive guide for building Chrome extensions with Manifest V3. Use this skill whenever the user mentions Chrome extension, browser extension, manifest.json, content script, service worker (in extension context), popup, side panel, chrome.runtime, chrome.tabs, chrome.storage, chrome.scripting, background script, MV3, Manifest V3, or any Chrome extension API. Also trigger when the user wants to inject scripts into web pages, communicate between page and background, bypass CSP from a content script, build an RPC layer over chrome messaging, or publish to the Chrome Web Store. Covers both new extension projects and adding features to existing ones. Do NOT use for framework-specific questions.
Conventional Commits v1.0.0 branch naming, worktree naming, and commit message standards for GitHub and GitLab projects. Use when creating branches, naming worktrees, writing commits, generating commit messages, reviewing branch conventions, or setting up changelog automation. Apply when your project needs consistent git history, SemVer-driven releases, parseable changelog generation, or automatic issue closing. Trigger when the user asks how to name a worktree, create a git worktree, or organize worktrees alongside branches.
Design end-of-article CTAs (calls-to-action placed at the bottom of blog posts, newsletters, essays, articles, or any long-form content). Use this skill whenever the user asks to write, design, review, or improve a CTA at the bottom of an article, blog post, or essay; mentions "end-of-post CTA", "bottom of the article", "call-to-action", "signup box", "newsletter CTA", "subscribe block", "what should I put at the bottom", "how do I get readers to subscribe / share / book a call / buy / follow / join / download"; or asks how to convert article readers into subscribers, leads, customers, community members, or supporters. Also trigger when the user wants A/B testing guidance or accessibility review for a CTA block. Covers independent / personal writing, newsletter publications, and brand / content-marketing blogs across any topic — tech, finance, food, climate, design, lifestyle, B2B, B2C. Produces both the copy (content) and the structural / visual design (form), matched to the user's objective and audience.
>
Codifies how someone or a brand writes — prose mechanics (lexicon, syntax, rhythm, structure, signature moves) independent of emotional tone. Output: PROSE.md. Three modes: BUILD a fresh guide from SOUL.md + TONE.md + discovery interview; ADAPT an existing guide to a new channel; AUDIT a corpus for prose patterns before codification. Use when: writing rules for a content factory, codifying ghostwriting voice for multi-writer consistency, defining banned words and sentence-length targets, building a house style guide, reverse-engineering prose from a corpus, porting style across channels. Trigger on: PROSE.md, writing style guide, prose guide, house style, ghostwriter style, writing playbook, brand writing mechanics, signature moves. NOT for: writing actual content (→ linkedin-ghostwriting, technical-article-writer, press-release-writer), removing AI patterns (→ humanizer), tone decisions (→ copywriting-tone-of-voice), hooks (→ copywriting-hooks), CTAs (→ copywriting-cta).
Build a brand tone of voice guide (TONE.md) via discovery, voice definition, and channel modulation. Outputs voice attributes with do's/don'ts, NN/g positioning, tone modulation matrix, lexicon, mechanics, and channel rules — consumed by downstream content skills writing on-brand copy. Covers B2B SaaS, B2C/D2C, NGO, public sector, consulting, industrial, product-led, personal, and volunteering brands; researches uncovered contexts (politics, regulated niches, religious orgs, gaming) on demand. Also adapts an existing TONE.md to a new channel (blog → LinkedIn, web → Twitter/X, in-product UI). Optionally consumes SOUL.md to pre-fill brand identity. Apply when the user wants to create a TONE.md, define brand voice, port voice to a new channel, refresh an outdated voice, or set up a content factory writing across many supports. Not for writing individual posts, articles, emails, or UI strings (→ dedicated writing skills), nor SOUL.md, PROSE.md, DESIGN.md.
CRXJS Chrome extension development — true HMR for popup, options, content scripts, side panels, manifest-driven builds, dynamic content script imports (`?script`, `?script&module`), and `defineManifest` for type-safe manifests. Uses Vite as its build tool. Use when the user mentions CRXJS, crxjs, @crxjs/vite-plugin, 'extension with hot reload', 'HMR for chrome extension', or wants to set up a CRXJS-based Chrome extension project with any framework (React, Vue, Svelte, Solid, Vanilla). Also trigger when the user has an existing CRXJS project and wants to add features, fix HMR issues, or configure content scripts with CRXJS. For general Chrome extension architecture (messaging, CSP, storage, permissions) -> See `samber/cc-skills@chrome-extension` skill.
Deep research skill — broad parallel web searches, multi-source validation, confidence tracking, cited Markdown report. Supports 11 research types: market (TAM/SAM, segments, pricing, trends), domain (industry structure, ecosystem, regulatory landscape), technical (architecture, tools, benchmarks), competitive (competitor teardown, positioning, win/loss), product (feature analysis, reviews, roadmap signals), academic (literature survey, citation networks, key authors), person/org (due diligence on a company or public figure), financial (funding rounds, valuation multiples, revenue signals), legal (IP, patents, litigation, compliance), trend (emerging signals, foresight, scenario mapping), community (ecosystem health, key voices, governance, fragmentation). Use when asked to: 'research <topic>', 'deep dive on X', 'analyze the landscape', 'competitive analysis', 'compare these options', 'who are the players in Z', 'literature review', 'background on Y', 'what papers exist on X', 'product teardown', 'technology evaluation', 'regulatory overview', 'funding landscape', 'what trends are emerging in X', 'patent landscape', 'community health', or any request requiring scanning many sources and producing a cited written analysis. Apply whenever the deliverable is a thorough, sourced report rather than a quick answer. Trigger even when phrased casually: 'look into X', 'what's the deal with Y', 'dig into Z', 'I need to understand the space', 'catch me up on X'.