Teach Claude a Skill by Recording Your Screen: The New Record a Skill Feature

The Last Hard Part of Automation Just Disappeared

Teaching an AI to do a repeatable task has always had one stubborn barrier: you had to translate what you do into words or scripts. Even with Claude's skill-creator, you had to sit through a conversation describing your workflow step by step. The new Record a skill feature removes that barrier entirely. You start a recording, do the task the way you always do it, narrate what you are doing as you go, and Claude turns the whole demonstration into a reusable skill. Under the hood, its system captures your screen activity, your mouse clicks, your keystrokes, and your voice commentary, then processes all of it into a structured skill definition it can execute again on demand. This is a meaningful shift in who can automate their work. Writing instructions is a skill in itself, and it is exactly the part that stopped most non-technical people from building their own automations. Demonstrating a task, by contrast, is something everyone can already do - you do the task every week anyway. Record a skill turns that existing ability into the entire setup process.

What a Skill Actually Is - and Why Recording One Is Powerful

To see why this is a big deal, it helps to understand what a skill is in Claude. A skill is a folder containing instructions, and optionally scripts and resources, that Claude loads only when it is relevant to the task at hand. This selective loading is what keeps Claude fast while still giving it specialized expertise the moment it is needed - Claude reads a short description of each available skill up front, costing only a few tokens, and pulls in the full detail exclusively when a task matches. Skills are not a fringe feature; they are how Claude already produces Excel spreadsheets, PowerPoint presentations, and Word documents, and how organizations get Claude to follow their exact brand guidelines. They are also composable, meaning Claude stacks several together for a single task, and portable, so once a skill exists it works across the Claude apps, Claude Code, and the API. What Record a skill changes is the authoring path. Previously you either hand-wrote a SKILL.md file or talked Claude through the skill-creator. Now the most natural authoring method possible - showing Claude the task while narrating it - produces the same structured, reusable, portable skill. The power is not just convenience; it is that the fidelity of a live demonstration captures details you would forget to write down.

How to Record a Skill That Actually Works

Getting a good skill out of a recording comes down to a few habits. Start by choosing the right kind of task: something you genuinely repeat, with clear and consistent steps - assembling a weekly report, processing a new client's files, applying a formatting routine, running a multi-step export. One-off tasks are not worth recording; repeatable ones pay you back every time. When you record, do the task at a normal pace and, crucially, narrate as you go - and narrate the why, not just the what. Saying I copy the totals column and paste it into the summary because the header always needs the latest figures gives Claude the reasoning it needs to handle small variations later, rather than blindly mimicking clicks. Record the clean version of the workflow without detours or mistakes, so the resulting skill is tidy. When you stop, name the skill clearly and give it a description, because that description is what Claude uses to know when to trigger it automatically later. Then test it once right after recording; if a step was missed, refine it. And keep the scope tight - one skill for one task. Because skills are composable, you are better off with several precise skills that Claude can combine than one sprawling skill trying to do everything. Find the feature in the plus menu inside the Claude desktop app, on Pro, Max, and Team plans.

What This Unlocks: Automation for People Who Do Not Code

The larger significance of Record a skill is who it opens automation up to. For years, turning a manual workflow into something an AI could repeat required at least a little comfort with instructions, structure, or code - which quietly excluded most of the people whose work is full of exactly the repetitive tasks worth automating. This feature lowers that barrier to almost nothing. If you can perform a task on your screen and talk through it, you can now build the automation. That reframes what an AI assistant is for a non-technical professional: not just something you ask questions, but something you can train on the specific, idiosyncratic way you do your own work. A marketer can record how they format a campaign brief; an operations person can record how they reconcile a report; a freelancer can record how they prepare a client deliverable - and each of those becomes a one-command skill afterward. It fits directly alongside Cowork's existing automation layer of local file access, persistent memory, connectors, and projects, extending it from what Claude can do to what Claude can learn from watching you. The honest note is that it is new and available on Pro, Max, and Team plans, so results will improve as the feature matures - but the direction is unmistakable: the way you teach an AI is shifting from writing to showing, and that is a door open to everyone.

Prompt

# RECORD A SKILL - HOW TO TEACH CLAUDE BY DEMONSTRATION
# In Claude Cowork (Claude Desktop app). Plans: Pro, Max, Team.

# ─── WHERE TO FIND IT ───
# Claude Desktop → open Cowork → click the plus (+) menu
# Select "Record a skill" (next to: add files, browse skills,
#   connectors, plugins)

# ─── HOW TO RECORD A GOOD SKILL ───
# 1. Pick a REPEATABLE task with clear, consistent steps
#    (e.g. "assemble my weekly report", "process a new client file")
# 2. Start the recording session
# 3. Do the task at a normal pace - Claude captures screen activity,
#    clicks, and keystrokes
# 4. NARRATE as you go. Say what you are doing and WHY:
#    "Now I open the sales sheet... I copy the totals column...
#     I paste it into the summary and bold the header row."
# 5. Stop the recording. Claude processes it into a structured,
#    reusable skill definition.
# 6. Name it clearly + give it a description so Claude knows WHEN to use it.

# ─── HOW TO USE IT LATER ───
# Just ask for the outcome. Claude scans your skills, matches this one,
# loads only what it needs, and runs the workflow - no re-explaining.
# Skills auto-trigger: you do not have to say "use the X skill."

# ─── WHAT MAKES A SKILL (context) ───
# A skill = a folder Claude loads ONLY when relevant. It can hold:
#   - a SKILL.md with the steps/rules (Record a skill writes this for you)
#   - optional scripts + resources (templates, brand assets)
# Token-efficient: Claude reads a short description of each skill up front,
#   and loads the full detail only when the task matches.
# Composable: skills stack - Claude combines several for one task.
# Portable: once created, skills work across Claude apps, Claude Code, API.

# ─── GOOD FIRST SKILLS TO RECORD ───
# - Your weekly/monthly report assembly
# - A repeatable file-formatting or renaming routine
# - How you onboard/process a new client's documents
# - A multi-step export or data-cleanup you do often
# - Applying your brand formatting to a document

# ─── TIPS ───
# Narrate the WHY, not just the WHAT - it helps Claude generalize
# Record the CLEAN version of the task (no detours) so the skill is tidy
# Test the skill once right after recording; refine if a step was missed
# Keep one skill = one task. Compose several rather than one giant skill