How to Use Claude Skills at Work: A Skill for Every Tool You Already Use

September 12, 2026

Skill · SKILL.md

The skill behind this guide: AI Skill for Canva. One file that makes Claude, ChatGPT or any AI chat answer like a Canva specialist instead of a generalist - $29.00, one payment, yours permanently.

View the Canva skill →

Claude skills are small instruction files you load once, and from then on the chat answers about one tool the way a colleague who uses that tool every day would answer. The honest limit: a skill does not connect Claude to your Canva account, your Docker daemon or your Premiere timeline. It changes what Claude knows and how it replies. You still do the clicking. What you get back is the specific setting, the exact menu path, the command with the right flags, and why it is that one.

A generic chat answers about design software. A tool skill answers about the tool open on your second monitor. Below: what the files are, how to install them, and which of the 78 tool skills in the catalogue to load first.

What are Claude skills, and how are they different from a prompt?

A prompt is a message: you type it, you get one reply, and next time you type it again. A skill is a file, usually called SKILL.md, that sits above the conversation. It carries the role, the method, the vocabulary, the output format and the questions the model should ask before it answers. Load it once and every message in that chat inherits it:

It persists. A prompt lasts one turn. A skill lasts the whole conversation, and in Claude it lasts across every conversation until you switch it off.
It carries method, not just tone. Good skills encode a sequence: file format first, then deadline, then audience. A prompt rarely survives that much structure.
It is portable. The file is plain Markdown. The same text works as a Claude skill, as ChatGPT custom instructions, or pasted into Gemini.
It is specific by design. A tool skill knows Lightroom calls it a Develop preset and Premiere calls it a Lumetri look, and will not blur the two.

None of that makes the model smarter. It makes it narrower, which for a tool question is the same thing as better.

Why does a tool skill beat a generic prompt?

Ask a general chat how to keep a Canva brand kit consistent across forty social posts and you get advice that fits any design app: use templates, lock your colours, name things clearly. Correct, and useless at 4pm on a Thursday. Ask with the Canva skill loaded and the answer is about brand kits, Magic Switch, folder structure and what breaks when five people edit one template.

The gap is widest where the tool has its own dialect. Asana, ClickUp and Trello all promise the same thing and mean different objects by the word "task", which is why these are separate files rather than one "project management" skill.

PROMPT - the tool audit

List the software I touch in a normal working week: [TOOL, TOOL, TOOL, TOOL, TOOL].

For each one, answer four questions in a table:
1. What do I use it for, in one line?
2. Where do I lose the most time in it, and is the cause the interface, the setup, or not knowing the feature exists?
3. Would a written expert answer help, or does it need a human looking at my screen?
4. Rank 1 to 5 for how much a dedicated AI skill for that tool would change my week.

Then name the two I should start with, and say plainly which of my tools would not benefit at all. Do not tell me all five are worth it.

How do you install Claude skills in Claude, ChatGPT and Gemini?

Every skill arrives as a ZIP with a SKILL.md file inside. Only the first of these is a real install.

Claude. Open Customize, then Skills, press the + button, choose Create skill, then Upload a skill, and select the ZIP. Toggle it on and it is live. Skills work on the Free, Pro, Max, Team and Enterprise plans. The one requirement is code execution, under Settings, then Capabilities; on Team and Enterprise plans an owner controls it. Anthropic documents the flow in its Skills help article, and the folder locations are in our install guide.

ChatGPT. There is no uploader. Open the ZIP, copy the SKILL.md text, and paste it into custom instructions, or into a custom GPT if you want it saved as its own assistant.

Gemini. Paste the same text into a Gem's instructions; a plain chat forgets it when the chat ends. Because the files are Markdown rather than something proprietary, moving between chat products costs one copy and paste.

Skill · The Design Tool Most Teams Share

AI Skill for Canva

$29.00this skill vs hours of trial and errorlearning it yourself

Brand kits, template systems, resizing a campaign across six formats without it falling apart, and the parts of Canva that behave differently in a team account. Claude cannot open your design, so the answers come as steps you follow with the editor in front of you.

View the Canva skill →

Which Claude skills should a team load first?

Start where the whole team touches the same tool, because that is where inconsistent knowledge costs most: the work tracker and the design file.

On the tracking side there are separate skills for Asana, ClickUp, Trello and Coda, the closest thing here to a Notion-style docs-and-database workspace. Each is built around the objects that tool actually has: Asana thinks in projects and sections, Trello in boards and cards, ClickUp in spaces, folders and lists, Coda in docs, tables and buttons. Ask any of them to design a workflow and you get something you can build rather than a diagram you then have to translate.

For everyday office output, PowerPoint and Slack cover the two places most internal work gets written. Least glamorous in the set, among the most used.

What do the developer skills actually do?

Code is where a general chat is already decent, so these earn their place on the boring parts: project layout, build configuration, dependency management and errors specific to one ecosystem.

The Java skill stays in Java idiom instead of writing Python with semicolons, and knows the difference between a Maven and a Gradle problem. The JavaScript skill keeps the answer on the runtime you are actually on rather than sliding between browser and Node assumptions halfway through. The Docker skill covers what people get wrong once and remember forever: layer caching, build context size, what belongs in an entrypoint, and why the container runs locally and dies in CI. The wider set runs from TypeScript through to Terraform.

What about design, photo and video tools?

This is where the honest limit matters most. Claude reads text and images, but it does not edit your photo, render your timeline or run your software. The creative tool skills give you the decision and the recipe: which adjustment, in what order, and why.

Lightroom covers develop settings, catalogue hygiene and presets that survive a whole shoot rather than one frame. Premiere Pro covers sequence settings, proxy workflows, the export presets that stop a client file looking soft, and the audio pass most edits skip. Photoshop handles the non-destructive side: smart objects, masks, and the layer structure that lets you change your mind two days later.

Skill · The Photo Workhorse

AI Skill for Photoshop

$29.00this skill vs a course you never finishthe usual alternative

Answers in Photoshop's own vocabulary: adjustment layers rather than "brightness", masks rather than "erase the background", smart objects rather than "save a copy first". Pairs with the Lightroom and Premiere Pro skills.

View the Photoshop skill →

Where does it fail?

It does not touch the tool. No skill logs into your account, moves a card, or presses export. Everything it gives you is an instruction for you to carry out.
Interfaces move. Menu paths and feature names change between releases. Treat a named path as a strong hint, and search the tool's own help if it is not there.
It cannot see your file. Paste a screenshot and Claude can read it. Without one, it is answering about a project it has never seen.
Pricing and plan limits go stale. Check what a tier includes on the vendor's own pricing page before you commit budget.
A skill does not fix a vague question. "Make my deck better" gets an average answer with or without a skill loaded.

Can you write your own instead of buying one?

Yes, and for anything specific to your own company you should. A SKILL.md file is a Markdown document with a name, a description of when to use it, and the instructions. The catalogue version saves you research on a tool you did not build; your own version captures the process only your team has.

PROMPT - turn your own workflow into a SKILL.md

Turn a process I repeat into a reusable skill file.

The process: [DESCRIBE IT]
The tool: [TOOL]
Who runs it: [ROLE]
What good output looks like: [DESCRIBE]
What usually goes wrong: [DESCRIBE]

Interview me first, one question at a time, and stop when you have enough rather than when you run out of ideas.

Then write a SKILL.md with: a short name, a one-line description of when it triggers, the role, the step-by-step method, the questions it must ask me first, the output format, and a list of what it must never claim to have done.

Under 300 lines, plain Markdown.

Run it for a week, note where it guesses wrong, and edit the file. A skill corrected three times beats one written perfectly on the first pass. For how other people structure theirs, see Claude skill examples.

In summary:

A SKILL.md file makes the chat answer like a specialist in one tool instead of a generalist about software. Install it in Claude under Customize, then Skills, or paste the text into ChatGPT custom instructions or a Gemini Gem. Start with the tool your team shares: Canva ($29.00) for design, ClickUp or Asana for the work tracker, Docker for the build. No coding, 30-day money-back guarantee.

Skill · SKILL.md · Works with Claude & ChatGPT