Briefing
Episode 37 · Primer · About 6 minutes
Download the MP3 · Linda and Leonard, AI voices, read a script written from the sources below.
Checked against each vendor's own notice and documentation on 13 November 2026. Vendor dates are targets and vary by plan and account, so check the original notice before quoting a date.
Before we record, every claim the hosts make is checked against the sources (this table was last updated 13 October 2026). Confirmed means a primary source or two independent reports; Reported means one party says so; Partly right, Disputed, Unverified and Not yet known mean what they say, and the hosts say so on air. This is the table as we left it.
Sign up for our podcast at agile-insights.com.au.
Linda Here is the idea for today. A skill is a written recipe. An A I assistant takes it off the shelf by itself when the work matches. ChatGPT, Gemini, Copilot and Claude now all use the same format for them. So the skills inside your organisation are becoming a real asset. Each one needs an owner, a home and a test. By the end, you will know what a skill is and how the assistant chooses one. You will also know what to do before the year ends.
Leonard The timing is why this matters now. Many staff have built custom G P Ts, the small tailored assistants inside ChatGPT. OpenAI says those are scheduled to retire on the eleventh of December. Some United States government workspaces, and enterprise workspaces with an approved delay, get until February. Google is moving its Gems over to skills as well. For Workspace business customers, Gems stop no sooner than the first of March next year. In both cases, the old assistants get converted into skills. So a lot of organisations are about to learn how many of these their people built.
Linda Which may be a surprisingly long list.
Linda Let me build it up in four steps. Step one is what a skill actually is. It is a folder. Inside is one plain text file called skill dot M D. That file has a name, a short description of when to use it, and then the instructions. It can also carry a template, some reference files, or even a small program. Take a weekly project report. The skill holds the steps, the report template, and a checklist to run before handing the report back. It is a recipe, not a separate chatbot.
Leonard A recipe card, then.
Leonard So how is that different from a custom G P T or a Gem? Those also had instructions and a few files attached, and plenty of people were happy with them. What actually changes for the person using it?
Linda Step two is the difference, and it is the important one. You had to open a G P T or a Gem and choose to talk to it. A skill gets chosen by the assistant. At the start, the assistant reads only the name and description of every skill it has. When your request matches a description, it loads the full recipe and follows it. Anthropic, which created the format, calls this progressive disclosure. It means an assistant can keep dozens of skills on hand without slowing down. It also means the description decides when a skill fires.
Leonard So the description does the real work.
Leonard Step three is the shared format. Anthropic introduced skills in October last year and published the format as an open standard in December. OpenAI now builds its ChatGPT plugins from skills. Google says its Gemini skills use the same open format, so skills from other platforms can be copied in. Microsoft has added them to Copilot Studio agents and to Copilot in PowerPoint. Because a skill is just a folder, you can hand the recipe to a colleague without handing over your data. On the How I A I podcast, Neo Aplin described it as sharing the recipe, not the files.
Linda Step four is what converting looks like. In ChatGPT, a migration button turns a G P T's instructions into a skill. Its knowledge files become reference files. Custom actions, the connections to other systems, do not come across and have to be rebuilt. The original becomes read only. And OpenAI says plainly that the new version may respond differently. Its advice is to compare familiar prompts and at least one harder case before relying on it. Google will turn leftover Gems into draft skills that their creators must review and switch on.
Leonard Fair warning, at least.
Leonard So the common belief is that one standard means a skill runs the same everywhere. Write it once, copy it into every tool, and forget about it. Is that how it works in practice?
Linda Only partly. The format is shared, but each product supports it differently. Aplin's answer was yes, with a small asterisk: some tinkering, and different file limits. Google's own Gemini app and its Workspace apps do not share skills yet, so you make one twice. And because the assistant chooses when to use a skill, OpenAI warns it will not necessarily run on every request. Portable is true. Identical is not. Every skill needs testing on each platform it will run on.
Leonard Portable, not identical. Noted.
Leonard Which brings us to governance. Look at what a skill now is. It is a file that moves between people and platforms, outside each vendor's sharing controls. It can contain code that runs. Anthropic warns that a malicious skill could open security holes or direct the assistant to send data out. It advises installing skills only from trusted sources. In PowerPoint on the web, staff can add their own skills with no admin step. Microsoft itself recommends reviewing governance for them. That is shared software, arriving without a software process.
Linda So here is what to do. First, use the retirement as an inventory. Find every custom G P T and Gem your people rely on, and who built it. Second, give each skill an owner, one place where it is kept, and a version history. Third, read the description, because that decides when it fires. Check that no client or personal data is bundled inside. Fourth, test a converted skill against the original on a few known cases before anyone relies on it. And check the vendor's own notice for your dates, because they vary by plan.
Linda If you'd like to know more, sign up for our podcast at agile-insights.com.au.
Leonard Thanks for listening.
All of the briefings (38) · Follow Briefing in Apple Podcasts or any podcast app
Everything from Agile Insights: briefings, Making You Think and the reference series