Claude Cowork Can Learn How You Work: Turning Conversations into Reusable Skills

July 22, 2026Updated: July 25, 2026Articles

On July 22, 2026 in Japan, Anthropic used the official Claude account on X to show how people can teach Claude “their way of working” in Cowork and turn it into reusable Skills.

Skills themselves are not new. Users could already create and upload custom Skills, but preparing the folder structure and a SKILL.md file manually made the process feel technical to first-time users.

The new emphasis is Skill Creator, which builds a Skill through conversation with Claude. Explain your usual procedure, share examples of good output, and describe the standards that matter. Claude organizes that information into something it can reuse later.

A Skill is a reusable playbook for a specific job

Claude Skills are reusable instructions that teach Claude how to perform a particular kind of work.

You might define how an internal report should be structured, which checks must happen before an article is published, or which column should drive a spreadsheet summary. When a similar request appears later, Claude can identify the relevant Skill and load its instructions.

According to Anthropic’s documentation, a Skill can include:

Instructions describing procedures and decision criteria
Reference material such as templates, examples, and brand guides
Scripts that make a repeated process more reliable

That makes a Skill more than a long prompt. It can package instructions, supporting material, and executable steps into one reusable unit of work.

You can now build a Skill through conversation

Anthropic’s tutorial describes the process like this:

Tell Claude that you want to create a Skill for a particular task
Share an existing template or examples of good work if you have them
Answer Claude’s questions about quality standards and when the Skill should be used
Let Claude use Skill Creator to assemble SKILL.md and any required resources
Save the Skill, test it on real work, and refine it

You do not need to learn the file format first. You can focus on explaining when the procedure applies and what a good result looks like.

One especially useful pattern is extracting a successful method from a previous conversation. After a request goes well, ask Claude to turn that approach into a Skill you can use next time. The conversation becomes source material for a repeatable process.

Prompts, Projects, global instructions, and Skills serve different roles

Claude now has several ways to retain information, so it helps to choose by purpose.

Method	Best suited to
Ordinary prompt	A one-off request or work where you are still exploring the direction
Projects	Background material and conversations that keep growing around one project
Global instructions	Baseline rules such as voice or output format that should always apply in Cowork
Skills	Repeatable procedures or specialist knowledge that should load only when relevant
MCP and connectors	Connecting Claude to external services and data

For editorial work, the site-wide voice might live in global instructions, research for one article in a Project, the pre-publication checklist in a Skill, and access to the CMS or analytics data behind MCP.

Skills and MCP do not compete. MCP determines which tools and information Claude can access; a Skill explains how to use them and in what order.

Start with work whose result you already know how to judge

A good first Skill is a task for which you already have your own definition of a correct result.

Extract decisions and owners from meeting notes
Check spelling, headings, and sources before publishing an article
Format a monthly report in a standard structure
Turn an image request into your usual composition and color palette
Convert a customer’s text into an internal template

A one-time task or a process that is still unsettled is a poor candidate. Turning it into a Skill too early can lock in rules that are not actually useful. Try the work in ordinary conversation a few times, then package the method once you know what works.

Test a new Skill with three different examples

Do not judge a Skill from one successful example. Try it with:

A standard request that fits the expected use case
A request that is missing some information
A related but different request where it is unclear whether the Skill should run

This reveals not only missing instructions, but also whether the Skill triggers when it should not. If Claude fails to use the Skill, check whether its description clearly explains when it applies.

Convenience makes reviewing the Skill more important

A Skill can contain scripts and external packages as well as written instructions. Avoid enabling a Skill from an unknown source without checking it.

Anthropic recommends using Skills only from trusted providers and reviewing their files, dependencies, and external network instructions before enabling them. A malicious Skill could contain prompt-injection instructions or send information somewhere you did not intend.

Even when you create a Skill yourself through conversation, it is worth reading the completed SKILL.md and bundled files once. If it includes internal documents or personal information, check who will be able to access it.

What to check if the feature is missing

Claude’s Help Center says Skills are available on Free, Pro, Max, Team, and Enterprise plans when code execution is enabled. Cowork itself is intended for paid plans, and Cowork on the web and mobile devices is being rolled out gradually.

If Skill Creator or the Skills menu is not visible:

Update the Claude app
Check that code execution is enabled under Settings and Capabilities
Look for Skills under Customize
On Team or Enterprise, ask whether the organization administrator has enabled Skills

Eligibility labels can differ between official pages during a rollout, so prioritize the menu shown in your account and the latest Help Center information.

Configuration moves from AI specialists to people who know the job

The biggest change with Skill Creator is that Skills are no longer limited to people who understand Markdown and folder structures.

The person who knows, “This order works,” or, “Always check this condition,” can explain that knowledge directly to Claude. Claude handles the technical packaging while the user teaches it the work. Skill Creator moves AI customization out of a settings screen and closer to an everyday conversation.

A practical first step is to pick one job you repeat every week and give Claude both your usual procedure and an example of a good result.