Google is introducing a more modular way to customise Gemini. Skills package reusable instructions that users can apply within an ongoing conversation, combine for a task and transfer through the open, Markdown-based SKILL.md format. The September 30 announcement also sets out a gradual transition away from Gems.
For SEO teams, the opportunity is operational: turn recurring editorial checks, brand guidance and research procedures into reusable components. The change does not establish a new ranking signal or guarantee visibility in AI answers. It makes the instructions behind that work easier to carry into another conversation or supported tool.
Reusable instructions inside the conversation
Google’s Workspace announcement explains that multiple Skills can be used in one prompt or at different points in a chat. It confirms the open format, but flags a practical limit: Skills currently do not synchronise between the Gemini app and Workspace apps. Users must create them separately for each environment.
The Gemini help documentation describes automatic application when instructions are relevant and importing a standalone SKILL.md file, a folder or a ZIP package containing it. Supported reference material can accompany the package. Scripts requiring internet access are currently unsupported, so importing instructions should not be confused with granting an unrestricted automation environment.
Rollout and retirement follow different clocks
For Workspace domains, Google schedules Skills from October 5 for Rapid Release and October 19 for Scheduled Release. The Gemini app rollout for Workspace domains begins October 13, with completion expected by mid-November. Separately, the consumer announcement says Gemini chat began its global rollout on September 30. These dates refer to different audiences.
Gems are not disappearing everywhere at once. Google’s transition guide places personal-account retirement in November 2026, business and enterprise in March 2027, and education in June 2027. It describes automatic conversion when Gems are removed, including supported files. It also notes that Skills do not yet work with every Gemini feature, including Canvas and Deep Research.
What a portable SEO workflow could contain
A useful editorial Skill could define when a news brief needs verification, require primary sources for product claims and specify how to distinguish a test from an official rollout. A separate brand Skill could govern language, terminology and presentation. Combining the two would reduce the need to repeat the same instructions whenever a new story arrives.
An AI-visibility workflow could similarly specify how to record a prompt, identify cited sources and separate observations from inferred explanations. Its value would come from making the research repeatable. The Skill should describe the procedure and required evidence rather than hard-code a favourable conclusion about a brand’s performance.
Portability still requires validation. After importing a package, teams should check its trigger, available tools, reference files and actual output in the destination environment. The same instruction file can encounter different permissions and feature support. A small set of representative tasks can reveal whether the workflow preserves the intended checks.
The broader implication is that editorial standards can become maintained assets rather than prompts scattered across individual chats. Versioned instructions, named owners and periodic reviews would help teams update a procedure when source requirements or product capabilities change. Gemini’s adoption of SKILL.md makes that approach easier to distribute; reliable SEO and AI-search work still depends on the evidence gathered and the judgement applied.