← Claude Code Hub
Nov 21, 2026 · 5 min read ✦ Tip #280

How to create a Claude skill: record it once, use it in Claude Code

Creating a Claude skill no longer means writing one: you record your screen in Cowork and Claude drafts it. What the recording captures, and how that skill reaches Claude Code.

How to create a Claude skill: you record the task in Cowork with Record a skill, Claude proposes the skill and, once saved, Claude Code loads it in your terminal under claude.ai sync

TL;DR In Claude for Mac, open Cowork, click + → Record a skill and do the task while you talk it through. Save the skill Claude proposes: in your terminal, with Claude Code signed in to your claude.ai account, it shows up in /skills under claude.ai sync without a restart.

Creating a Claude skill no longer means writing a SKILL.md. Record a skill captures your screen, clicks, typing and voice while you do the task once, and Claude turns that into a skill. Once you save it, it lives in your claude.ai account, and Claude Code pulls your account's skills down to your terminal. You record in the app and use it while you code.

Record the skill

1. Open Cowork in Claude for Mac

Update the app to the latest version first. Recording only exists in Cowork: it isn't in chat, and it isn't on Windows.

2. Open the recording dialog

Click + in the composer and pick Record a skill. It's also under Customize → Skills → Add → Record your screen. The first time, macOS asks for Accessibility and Screen Recording permissions, and you may need to restart Claude.

3. Close what you don't want recorded, then click Start recording

The dialog itself warns you:

Don't type passwords or secrets, or display sensitive information or private conversations while recording.

The whole screen is captured for the entire session, not only the window you work in. Keep the microphone on: the control next to it mutes it or switches the input.

4. Do the task once, narrating as you go

The capture bar counts the steps so far. A recording runs for about 10 minutes: a countdown appears with about a minute left, and at zero it's sent on its own. Done sends it to Claude; Discard throws it away and nothing gets created.

Say why you take each step, not only what you click. What you say is what Claude can't infer from the screen: which value you check, when you stop, what you do when something fails.

5. Read the skill before you save it

Claude starts a Cowork task, reviews the recording and proposes one of two things:

What it proposes Button When
A new skill, marked NEW Save The recording matches none of your skills
An update to a skill you already have Update The recording overlaps it; the card names which one

Expand Content to read the skill before deciding; Dismiss throws it away. The video and audio aren't kept: a set of screenshots stays in the task's Recorded demonstration step, and deleting the task removes them.

Use it in Claude Code

What you save shows up in Customize → Skills and works like any other skill on your account. Claude Code syncs those skills with no setup, in sessions where you sign in with your claude.ai account.

1. Sign in to Claude Code with your claude.ai account

/login

You need Claude Code v2.1.273 or later. If you run /login mid-session, restart Claude Code so it starts syncing.

2. Don't restart to get it

At startup, Claude Code downloads your skills to ~/.claude/skills/synced/ in the background, then asks claude.ai for changes: about every 10 minutes while you work, about every 40 when the session sits idle. A skill you save in Cowork joins the open session at the next check.

3. Find it in /skills

/skills

Your account's skills are grouped under claude.ai sync, next to the Anthropic ones that always sync, such as pdf and xlsx. Call one with /<name>, or with /anthropic-skills:<name> when another command already owns the short name: with a local deploy skill and a recorded deploy, /deploy runs the local one.

When it doesn't reach your terminal

Your session Why
API key, ANTHROPIC_AUTH_TOKEN, CLAUDE_CODE_OAUTH_TOKEN or an apiKeyHelper It doesn't use the /login sign-in
Bedrock, or CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC set It doesn't fetch feature flags from Anthropic
--bare, --safe-mode, or a --setting-sources list without user Those modes don't sync your account's skills
syncClaudeAiSkills: false in your settings You turned syncing off on that machine
A short claude -p run It can finish before the skill downloads: start it with CLAUDE_CODE_SYNC_SKILLS=1

Whatever already synced stays on disk: a later session on the same account loads it even when it can't reach claude.ai. Cowork and cloud sessions get it on their own, because they read your account's skills rather than your ~/.claude/skills/. It's the same mechanism behind skills you didn't install.

Edit it on claude.ai, not on disk

Claude Code downloads synced skills and never uploads them. Edit the file under ~/.claude/skills/synced/ and the next sync overwrites it. Change the skill in Customize → Skills and the next check pulls the new version.

A recording gets you a first draft, not the final skill. To find out whether it improves the result, test it with skill-creator. Check it against Anthropic's five rules for skills, and if it changes case by case, have it take arguments. If the task happened in a Claude Code session rather than in the app, there's another way to skip writing it: capture the pattern on the spot from the same session.

Official docs: How to create custom skills · Where synced skills load

Requirements

  • Claude for Mac with Cowork, on a Pro, Max, Ultra or Team plan. Not on Free or Enterprise.
  • Skills need code execution turned on in claude.ai (Settings → Capabilities).
  • Claude Code v2.1.273 or later, signed in with the same claude.ai account.

Found this useful? See more of wmedia.es in your Google results.

Add wmedia.es as a preferred source on Google
Free guide

The 51 essentials, as a guide.

One page per tip. Five chapters. What I actually use daily in production. No theory, no fluff.

  • 1. Getting started 10 tips
  • 2. Awareness 3 tips
  • 3. Mastery 22 tips
  • 4. Autonomy 15 tips
  • 5. Comparison 1 tip
Are you a professional Web developer?

You'll receive the guide by email · You join the Gravitas newsletter · Unsubscribe anytime

of 51
#

Wmedia · 51 tips
Free guide · 51 tips · 5 chapters

The 51 essentials, as a guide.

One page per tip. Five chapters. What I actually use daily in production. No theory, no fluff.

Are you a professional Web developer? · Unsubscribe anytime
How I use AI

My Claude Code workflow.

The skills, agents and instructions I use as a professional Software Engineer. It's called Craft, and it's a plugin you can install.

See the skills

Want the 51 Claude Code essentials as a guide?