November 14, 2026

AI Skills: How Leaders Turn a Process Into Instructions AI Follows Every Time (2026 Guide)

A skill is a standard operating procedure for AI. Compare skills in Claude, ChatGPT, Gemini, Copilot and Google Workspace, and copy a template.
AI Skills
Daan van Rossum
By
Daan van Rossum
Founder & CEO, Lead with AI

Presented by

Based on the Lead with AI AI Leader Advanced program.

Think about a task you explain to AI every week. You describe the audience, walk through the steps, set the format and remind it what to avoid.

A skill captures that explanation once. It is a set of reusable instructions that teaches AI how to do a specific task, like a standard operating procedure for AI. Each week, you add the new information, and AI follows the process you defined.

How is a skill different from a saved prompt?

A saved prompt is for the work in front of you and needs context each time, while a skill is for work you repeat and can load on its own with templates, examples and checks

A good prompt gives AI strong instructions for one piece of work. A skill makes those instructions reusable, and can add templates, examples, reference files and checks. Most tools can also load a skill automatically when they recognize a matching request, and you can combine skills, such as one for your process and one for your writing style.

What makes a good skill?

What a good skill contains: a name and description, CODO instructions, resources such as templates and examples, and checks for missing details

Start with the four parts of CODO: Character, Objective, Do and Don't, and Output. Then add two things that make it reusable:

  • Trigger: which requests should activate the skill.
  • Resources: the templates, examples and reference files it should use.

As you write it, make the important steps explicit, as if you were briefing a capable new colleague. Keep what stays the same, such as structure and process, in the skill, and put what changes, such as this week's notes, in your request. Include an example of a good result, and test the skill with realistic inputs before you share it.

The five skill tools at a glance

ToolWhere you create itHow you use itPlans
Claude skillsCustomize, then Skills, or record one in CoworkType / or let Claude chooseAll plans, with code execution on
ChatGPT skillsPlugins, then Skills, or ask skill-creatorType @ or let ChatGPT chooseBusiness, Enterprise, Healthcare and Edu
Gemini skillsCustomize, then Skills, in the Gemini appType @ or let Gemini choosePersonal and Workspace accounts
Copilot skillsManage plugins and skills in PowerPoint or ExcelChoose it from + in the prompt boxMicrosoft 365 Copilot license
Google Workspace skillsSkills in Workspace StudioType @ in the Gemini side panel, or add it to a flowWorkspace Business, Enterprise and Education

One skill file can travel. Claude, ChatGPT, Gemini and Copilot all use SKILL.md files based on the same open format, so you can often copy a skill from one tool to another and adjust it.

Which tool should you use?

Build the skill where the work happens.

A CODO skill template you can copy

This skill turns rough notes into a weekly leadership update. Paste it into any of the five tools, or save it as SKILL.md and upload it.

---
name: leadership-update-writer
description: Turns rough weekly notes into a concise, decision-ready leadership update. Use when I ask for a leadership update, weekly update or executive summary from notes.
---

Character: You are a chief of staff who writes for the executive team.

Objective: Turn the notes I provide into a one-page weekly update that keeps leaders informed and helps them make decisions.

Do:
- Keep every fact, figure and date exactly as given.
- Highlight the decisions needed, with owners and deadlines.
- Mark any missing owner or deadline as "Not provided".
- Ask for the notes and the reporting period if I have not shared them.

Don't:
- Don't invent information or add assessments the notes do not support.
- Don't add urgency or status labels that are not in the notes.

Output:
Five sections: executive summary, key developments, decisions and action items, risks or trade-offs, and next steps. Keep it to about one page.

What should you keep in mind?

  • Not every task needs a skill. Build one when a process repeats and consistency matters.
  • A skill scales a weak process too. Test it and improve it before you share it with your team.
  • Write a precise description, because it decides when the AI uses the skill.
  • Only install skills you trust, because some skills can run code.
  • Check the output, especially facts, figures and anything the notes did not include.

Want to go further? Build SOPs for any workflow with AI helps you write a process down, and Record a skill on Claude shows how to capture one by demonstration. To compare skills with projects and assistants, read our guide to reusable AI assistants.

Key takeaways

  • Turn your best repeated prompt into a skill.
  • Use CODO, plus a trigger and resources.
  • Keep variable inputs out of the skill.
  • Test before you share with your team.
  • Build the skill where the work happens.

This overview is based on the Skills module in Lead with AI's AI Leader Advanced program. Lead with AI helps senior leaders build practical AI fluency through hands-on courses and a membership community.

Flagship AI Newsletter
The AI Newsletter That Makes You Smarter, Not Busier
Join over 30,000 leaders and receive our insights on AI platforms, implementations, and organizational change management.
FlexOS Course - AI Content Accelerator - Testimonial Badge

Frequently Asked Questions

What is an AI skill?

A set of reusable instructions that teaches AI how to do a specific task, often with templates, examples and reference files. Think of it as a standard operating procedure for AI.

What is the difference between a skill and a prompt?

A prompt covers the work in front of you. A skill makes those instructions reusable, can include supporting files and can load automatically when a request matches.

Can I use the same skill in different AI tools?

Often, yes. Claude, ChatGPT, Gemini and Copilot use SKILL.md files based on the same open format, so you can copy a skill and adjust it.

When is a task worth turning into a skill?

When it repeats and consistency matters, such as a weekly update, a recurring report or a review against a checklist.

Are skills safe to share with my team?

Test a skill with realistic inputs before you share it, and only install skills from sources you trust, because some skills can run code.