Async training content builder · free AI skill

Builds a complete self-paced training module from a topic, audience, and learning objective — including a written lesson broken into microlearning segments, a step-by-step demo script, 2-3 worked examples, a knowledge…

Purpose

Turn a single topic, audience, and learning objective into a ready-to-publish asynchronous training module — written lesson, demo script, worked examples, knowledge check, and job aid — built on instructional design principles so learners retain and apply the material without a live facilitator. Eliminates the slow, blank-page authoring process that stalls most enablement teams.

When to Use

Invoke this skill when the user asks to:

Build a self-paced or async training module for reps, CSMs, or new hires
Create onboarding content for a specific role, product, or process
Write a lesson plus knowledge check for an LMS or enablement platform
Turn a product feature, methodology, or playbook into a training asset
Convert live workshop content into a self-serve module
Produce a demo script or walkthrough learners can follow on their own

Inputs Required

Before starting, collect:

Topic: The specific subject the module teaches (feature, process, skill, or concept)
Audience: Role and experience level (e.g., new AEs in week 1, tenured CSMs, SDRs)
Learning objective: What the learner should be able to do after completing the module — action-oriented, not "understand X"
Delivery context: Where it lives (LMS, Notion, Google Doc, video-first) and any format constraints
Prerequisite knowledge: What the learner already knows walking in
Product/process specifics: Names, steps, screens, or terminology to use accurately (paste real details, not placeholders)
Estimated completion time: Target length (e.g., 10 min, 20 min) — drives segment count

If completion time is missing, default to a 15–20 minute module (~1,200–1,600 word lesson, 5–7 knowledge check questions). If the learning objective is stated as "understand," rewrite it into an observable action verb and note the change.

Instructions

Step 1: Convert the Objective into a Measurable Outcome

Rewrite the learning objective using an observable action verb from Bloom's applied levels — identify, demonstrate, apply, configure, respond, diagnose, position. Avoid know, understand, learn about. State the outcome as: "By the end of this module, the learner will be able to [verb] [task] [under what conditions / to what standard]." This single line anchors every downstream section — the lesson teaches to it, and the knowledge check measures it.

Step 2: Build the Written Lesson (Chunked into Microlearning Segments)

Break the lesson into 3–5 segments, each teaching one idea. For each segment:

Segment heading — a plain-language title stating the sub-skill
Why it matters — 1–2 sentences connecting it to the learner's day-to-day work
The teaching — the core content, written in second person ("you"), short paragraphs, concrete over abstract
A micro-example or callout — one specific instance using the real product/process details provided

Apply these instructional design principles throughout:

Chunking: One concept per segment; no segment longer than ~350 words
Relevance-first framing: Lead each segment with the "so what" before the "how"
Concrete language: Use the actual screen names, button labels, and terminology provided — never generic stand-ins
Cognitive load control: Introduce no more than 5–7 new terms across the whole lesson; define each on first use

Step 3: Write the Demo Script (Step-by-Step Walkthrough)

Produce a numbered demo script the learner can follow on their own or that a video producer can record against. For each step:

Action: The exact click, input, or say-this-line
On screen: What the learner should see or where they are
Narration/note: What to say or notice, and why it matters

Structure the demo as: setup/context → the core sequence (5–10 steps) → the "what good looks like" end state. Call out the 1–2 places learners most commonly go wrong.

Step 4: Provide 2–3 Worked Examples

Show the skill applied in realistic scenarios drawn from the audience's actual work. For each example:

Scenario: A specific situation the learner will face
Applied walkthrough: How the skill/process resolves it, step by step
Takeaway: The generalizable principle to carry to new situations

Vary the examples by difficulty — start with a clean case, then include one with a wrinkle or exception.

Step 5: Build the Knowledge Check

Write 5–7 questions that measure the Step 1 outcome — not recall of trivia. Mix formats:

Multiple choice (majority): 4 options each, with plausible distractors that reflect real misconceptions
Scenario-based: "A customer says X — what's your best next move?"
1 application/short-answer where appropriate

For every question provide:

The correct answer
Answer rationale: why it's correct AND why the strongest distractor is wrong (this is where the real learning lands)

Ensure at least half the questions test application, not definition.

Step 6: Create the Job Aid

Produce a one-screen reference the learner keeps after the module — a checklist, decision tree, or quick-reference table summarizing the key steps or criteria. It should be usable standalone in the flow of work, without re-reading the lesson.

Output Format

Structure: Six labeled sections in order, ready to paste into an LMS or doc
Length: 1,800–2,600 words total (scales with target completion time)
Format: Structured document — prose for the lesson, numbered steps for the demo, table/list for the job aid, formatted Q&A for the knowledge check
Sections: Measurable Objective → Written Lesson (3–5 segments) → Demo Script → Worked Examples (2–3) → Knowledge Check (5–7 Q&A) → Job Aid
Tone: Instructional and direct — second person, warm but efficient; teaches to a working professional, not a beginner being lectured

Quality Checklist

Before delivering output, verify:

[ ] The learning objective uses an observable action verb — no "understand" or "know"
[ ] The lesson has 3–5 segments, each teaching exactly one concept, none over ~350 words
[ ] Every section uses the real product/process details provided — zero generic placeholders
[ ] The knowledge check has 5–7 questions and at least half test application, not recall
[ ] Every knowledge check question includes rationale for the correct answer AND the top distractor
[ ] The demo script and job aid are usable standalone, without re-reading the lesson

Notes

The knowledge check is the module's spine — write it against the objective first if you're unsure the lesson is teaching the right thing, then confirm the lesson covers every tested point.
Distractors are where instructional quality shows: base them on real mistakes the audience makes, not obviously wrong throwaway options.
For video-first delivery contexts, the demo script becomes the recording storyboard and the written lesson becomes the video's supporting notes — flag which sections map to on-screen vs. spoken content.
If the topic is broad (an entire methodology or product area), recommend splitting it into a short module series rather than one overloaded module — cognitive load drops retention fast past ~20 minutes.

How to use this skill

This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.

Installing in Claude Code:

~/.claude/skills/<folder-name>/SKILL.md — auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)
<your-project>/.claude/skills/<folder-name>/SKILL.md — auto-loads only when working in that project (recommended for project-specific skills)

Restart Claude Code or open a new session to register.

Using in Claude.ai, ChatGPT, Gemini, or other AI tools:

Drag this file into a new chat, or copy and paste its contents
Send your task or request as your next message — the AI will apply the skill where it fits

For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills