Claude Cowork Record a Skill: Plans, Steps, Privacy Limits

Record a skill in Claude Desktop Cowork (Mac) turns a live screen-and-voice demo into a reusable Skill proposal. It is not model retraining.

Think of it as packaging task-specific instructions from a walkthrough so you can rerun the work later with less prompt drafting.

What this guide covers

This guide does two things:

• Anchors on Claude Help Center limits (plans, Mac-only Cowork, ~10-minute cap, retention)
• Cross-checks independent reporting and hands-on write-ups so you can decide when to adopt it versus keeping handwritten Skills or existing automation

---

What Record a skill is — from demo to reusable Skill

In short: Record a skill is the official demo path that turns “watch me do it” into a savable Skill.

During a session it can capture on-screen actions, clicks, keystrokes, and narration, then propose a reusable Skill. It is closer to packaged instructions than to a pixel-perfect click macro.

Official positioning

Anthropic’s Claude account (@claudeai) announced that you can record your screen while talking through a task and Claude will convert the walkthrough into a rerunnable skill.

Key points:

• Entry: Desktop + menu → Record a skill
• Plans: Pro, Max, and Team
• Source: official X post

---

How it differs from older Skill paths

Older Skill paths still matter:

• Handwritten SKILL.md
• Generate-from-text
• Package a successful Cowork process
• Upload files

Record a skill’s differentiator is capture while you execute. That lowers teaching cost when writing a perfect procedure first is the bottleneck.

---

Independent reports and demo call patterns

ITmedia AI+ independently reported a 2026-07-21 (local) rollout (ITmedia AI+).

• Slash-style invocation example: /file-expenses

---

Charlie Hills hands-on demo

Charlie Hills’ hands-on write-up walks Cowork → + → Record a skill and emphasizes the pre-record privacy warning (Charlie Hills / MarTech AI).

Reported demo outcomes:

• Workflow: Notion→Buffer repurposing
• Proposed skill: repurpose-to-buffer
• Assembly: three parallel sub-agents (draft, platform rules, packaging)

Source

---

How to set expectations

Coursiv frames the feature as a demo-to-Skill workflow for task-specific instruction packages—not foundation-model training (Coursiv).

• If headlines sound like “Claude learns your job,” reset expectations
• Prefer reusable operational instructions from a supervised demo

For designing Skills after save, see How to write Claude Code Skills.

• Record a skill mainly reduces creation friction
• Edit/share/delete still follow normal Skill operations under Customize → Skills

---

Requirements and first run (plans, Mac, two paths, ~10 minutes)

If you are outside the supported boundary, the control simply will not appear.

Per Claude Help Center “How to create custom skills,” recording a skill is available as follows (Claude Help Center):

• Available: Pro / Max / Team in Claude for Mac Cowork
• Not available: chat, Windows, Free, or Enterprise

Prep before you hit record

1. Update Claude for Mac
2. Grant macOS Accessibility (mouse/keyboard tracking) and Screen recording
3. Close notifications, password vaults, private chats, and sensitive files
4. Prefer sample data over production customer records

Help Center warns not to type passwords/secrets or expose sensitive or private conversations. Assume everything on screen and spoken audio is captured for the session.

---

Two start paths

Path	How to start
Composer	Cowork composer + → Record a skill
Skills admin	Customize → Skills → Add → Record your screen

After Start recording, work as usual and narrate intent/exceptions. Use Discard to abort or Done to finish.

---

Time cap and review-before-save

• Cap is about 10 minutes
• A ~1-minute countdown appears near the end; at zero the session auto-finishes and sends (Done equivalent)
• Claude reviews the recording inside the Cowork task and proposes a Skill
• New Skill: Save / Dismiss; existing Skill update: Update / Dismiss
• Expand Content and read it before saving

Charlie Hills also notes details that are easy to miss in short official blurbs:

• Slash-command retests from a fresh chat
• Possible Claude in Chrome / Control Chrome permission needs
• Optional “Schedule it” automation

Treat first success as: record → review → save → rerun in a new session.

---

Comparison table — Record a skill vs handwritten Skills vs Codex Record & Replay

Similar teaching metaphors do not mean interchangeable products. Compare entry points, plan gates, and verifiability.

Side-by-side comparison

Dimension	Claude Record a skill	Handwritten / generated Skill	OpenAI Codex Record & Replay
Teaching style	Screen demo + voice	Docs / prompts	Demo-style (reported earlier peer)
Entry	Mac Cowork + / Skills	Customize and related Skill flows	Codex / ChatGPT product surface
Plans	Pro / Max / Team	Often broader for Skills themselves	Product-specific
Output	Proposal → saved Skill	SKILL.md etc.	Replay-oriented skill equivalent
Best fit	Visual, narratable, repeatable work	Procedures you can fully specify in text	Often discussed in coding-agent context

---

Sources for this comparison

Sources (as of July 2026):

• Claude Help Center (custom skills)
• ITmedia AI+
• Coursiv

---

Observed fit and weak cases

Hands-on observers often describe goal-oriented tool use (connectors, selective browser control) rather than pure coordinate replay.

Coursiv’s weak/avoid cases still apply:

• One-off work
• Hard-to-verify outcomes
• High-harm domains such as payments, medical, or contracts

---

Codex peer reading

For the Codex peer feature, see:

• Codex Record & Replay
• Hands-on try write-up

Choose based on your org’s standard tool boundary, not the metaphor alone.

---

Privacy, retention, and operational governance

Most practical risk lives in what appears on screen and what remains after save.

Recording and retention

Help Center states the retention boundary as follows:

• Video/audio are not retained
• Session screenshots remain under the Recorded demonstration step
• Deleting the Cowork task removes those screenshots

Independent analyses also caution against inventing retention details beyond published Help Center text.

---

Cowork safety boundary

“Use Claude Cowork safely” centers risk on two axes (Use Claude Cowork safely):

• What Claude can read
• What Claude is allowed to execute

Practical guidance includes:

• Separate read tools from write tools
• Supervise high-impact writes
• Keep local reach Desktop-mediated and limited to connected folders
• Avoid sensitive local shares
• Avoid money/PII sites in Claude in Chrome
• Limit untrusted MCP
• Treat computer use carefully
• Require explicit permission before permanent deletion

---

Team and governance angles

Skill-izing tribal knowledge lowers handoff cost, but these remain separate decisions:

• On-screen business data boundaries
• Default-off shared Skills
• Monitoring needs

Treat Record a skill as a transfer-cost reducer that still needs a defined allowlist of tasks and a named reviewer for Save.

For teams, decide target jobs, banned screen content, and review ownership before the feature spreads informally.

---

Adoption checklist — try, skip, or fall back

This week’s minimum viable test is three steps: record one low-risk job, read the proposal before Save, then rerun it in a fresh session.

Strong fit

• Weekly reports, table cleanup, content repurposing, research brief templates—repeatable and visually verifiable
• Work where exceptions are faster to narrate than to pre-document
• Failures that do not create legal, medical, or payment harm

---

Weak / skip

• One-off tasks with little reuse
• Outcomes you cannot verify
• Payments, contracts, medical workflows, bulk production data changes

---

Checklist

1. Confirm Mac + Pro / Max / Team
2. Record on sample data; hide passwords, notifications, and sensitive UI
3. Split work into ~10-minute segments
4. Expand proposal Content; look for unexpected steps or permissions
5. After Save, rerun via new chat or slash command
6. Define fallback to handwritten Skill or existing RPA/runbook
7. On Team, confirm sharing defaults, scope, and audit/monitoring needs

Skipping the checklist and mass-recording “everything the team does” expands privacy and misfire risk first. Passing the three-step set on a few jobs is how you keep only reproducible automation.

---

FAQ

Q1. Does Record a skill work on Free, Windows, or Enterprise?

As documented in Help Center: Pro / Max / Team on Claude for Mac Cowork only. Chat, Windows, Free, and Enterprise are out of scope. Do not confuse general Cowork availability with this recording gate.

---

Q2. Is the recording stored?

Video/audio are not retained. Screenshots can remain in the Cowork task until the task is deleted. That does not make sensitive on-screen content safe during capture.

---

Q3. How do I invoke a saved skill?

Like other Skills after save. Reports and demos show slash-style examples such as /file-expenses or /repurpose-to-buffer. Always review Content before Save, then test once in a new session.

---

Q4. Is this the same as Codex Record & Replay?

The “demo → reuse” idea is a close peer pattern, but product entry points and target work differ. Decide inside your toolchain boundary.

---

Q5. What if replay is unreliable?

Work through the problem in this order:

1. Shorten the demo
2. Narrate exceptions explicitly
3. Edit the proposal
4. Fall back to handwritten Skills or existing automation

Do not force unverifiable high-harm work through recording.

---

Key takeaways

Record a skill lowers the cost of teaching repeatable desktop work from “write the perfect procedure first” to “demo once, review, save, and retest.”

It still fails outside the official boundary:

• Mac
• Pro / Max / Team
• ~10 minutes
• Video/audio not retained (screenshots live in the task until deleted)

Next actions:

1. Confirm plan and OS
2. Record one sample-data job and read the proposal before Save
3. Rerun in a new session and define the handwritten Skill / RPA fallback

Start with low-risk, high-repeat work so you keep automation you can trust—not just a new AI PC feature label.

Related articles:

• How to write Claude Code Skills: official rules and real examples
• OpenAI Codex Record & Replay Turns Screen Demos into Skills
• Trying Codex Record & Replay to Turn Workflows into Reusable Skills