Vibe Coding the Apocalypse

What Anthropic Shipped

On July 21, 2026, Anthropic added a feature called "Record a skill" to Claude Cowork, its Claude desktop app. Instead of writing detailed instructions or code to teach the AI a task, you open the + menu, hit record, perform the task on screen while narrating your reasoning aloud, and stop. Claude then synthesizes your screen activity, mouse clicks, keystrokes, and voice into a structured, reusable "Skill" that lands in your library and can be run again on demand [1][2].

Anthropic's own framing is characteristically plain: "Record your screen while you do a task, talk through it as you go, and Claude turns it into a skill it can run again" [5]. The launch demo saved a 23.4-second recording as a skill named /file-expenses [7]. The feature is available on paid Pro, Max, and Team plans, and on the desktop app only—free-plan users can run existing Skills but can't record new ones [1][3].

Crucially, the narration matters as much as the clicks. Multiple write-ups stress that Claude uses your spoken commentary to learn the reasoning behind each step—why you click what you click, which values matter, how to handle exceptions—not just a click sequence [1][2]. The pitch is "show, don't tell": a live demonstration captures the naming conventions and if-X-then-Y judgment calls that people routinely omit when writing a standard operating procedure from memory.

What a "Skill" Actually Is

Under the hood, a Skill is not a fine-tuned model or a "trained copy" of the person [1]. It's a directory containing a SKILL.md file plus optional scripts and reference material, which Claude discovers and loads automatically when a task matches its description [8][9]. Skills occupy a distinct "method layer"—sitting between Projects (background knowledge), MCP (live data connections), and one-off Prompts—that encodes how a task is done correctly, every time [8].

Implementation-wise, a meta-tool named Skill acts as a dispatcher, injecting instructions into context and modifying tool permissions [10]. A key efficiency trick called progressive disclosure keeps SKILL.md under roughly 500 lines and pushes detailed material into separate files, so heavy resources only hit the context window when a task requires them [9][8].

Why It Matters

The thesis is bigger than the UI. "Record a skill" collapses the authoring cost of automation. The biggest friction in delegating to an agent was writing complete, edge-case-aware instructions; this reduces that to the time it takes to do the task once while talking. One practitioner had just published a manual "record with Loom, hand the transcript to Claude, build a skill" workflow—only for Anthropic to ship a feature that eliminated the intermediate steps entirely [15].

The target user is deliberately non-technical. Anthropic data cited by AlphaSignal says more than 90% of Cowork usage is non-software work—ops, finance, content [2]. That reframes skill-capture as SOP-capture for whole teams, turning "watch how I do this" into a portable, shareable artifact and, as one vendor puts it, marking "the difference between an AI assistant and a production-grade agent" [11].

The Catch: It's a Fast-Follow With Open Questions

Anthropic wasn't first. OpenAI shipped essentially the same idea—Codex's "Record and Replay"—on June 18, 2026, roughly five weeks earlier [4][12]. Anthropic's differentiators are real but modest: Codex is Mac-only, excludes the EEA, UK, and Switzerland, and replays only through Codex, whereas Claude targets general knowledge work [12][13]. Google's Gemini Spark also has "Skills," but teaches by prompt rather than demonstration [6].

Reliability is genuinely contested. A 650-trial experiment argues Claude Skills have two problems: activation (does Claude invoke the right skill?) and execution (does it actually follow the steps once activated?), with the latter described as an open issue—the model tends to deprioritize procedural overhead in favor of output that merely "looks complete" [14]. And one demonstration is not validation: a recording shows what happened once, but a useful skill must generalize beyond that single file or customer [1][3].

Then there's governance. SKILL.md is treated as a trusted instruction source, so a malicious skill needs only "a convincing English sentence," not a code exploit. One survey cited a 26.1% vulnerability rate across 42,447 community skills [18][19][21]. This mainly concerns installing third-party skills rather than recording your own—but recorded skills flow into that same ecosystem. Practitioners should also note that Cowork tasks consume far more usage than regular chat, that Claude can modify files without review if misconfigured, and that privacy and retention specifics remain under-documented [2].

The Practical Takeaway

"Record a skill" is a small feature carrying an outsized argument: the bottleneck for agent automation is no longer model capability but instruction-authoring, and demonstration-by-recording is Anthropic's bet on removing it for non-technical users. The disciplined workflow is clear—record with sanitized, low-risk data, inspect the generated SKILL.md, test against varied inputs to confirm Claude learned the rule rather than accidental details, and only then trust it in a real workflow.