The News, Explained

Google has announced a gradual rollout of skills across Workspace apps including Gmail, Docs and Slides. A skill saves reusable instructions for Gemini: the tone, document structure or reference material it should use when carrying out a task. Those instructions can then be called on across different pieces of work. Source Source

For example, a team that often writes proposals could connect its brand guidance and document template to a skill. It could request drafts using those saved rules instead of pasting lengthy instructions each time. Workspace Studio lets users build from scratch or a template, test email drafts, documents or presentations, and then enable the skill. Studio is a tool for configuring and automating Workspace tasks; a skill guides how Gemini performs work within its existing capabilities. Source Source

Colleagues can also develop instructions together in Google Docs. Choosing “Make this skill in Studio” creates a copy for each collaborator who clicks it, and that person must turn it on in Studio. Gemini can select relevant enabled skills for a request, or users can explicitly invoke them with @ and the skill name. Several skills can be combined in one request. Source Source

The sharing model matters for a team. A recipient of a Studio skill saves an independent copy in their own library, where they can customize and enable it. Later edits by the original creator do not overwrite copies that others have already saved. “Sync with Docs,” which brings revised document instructions into one’s own skill, is a separate sync action the user initiates. Source Source

Reference-file access is managed separately. If a shared skill links to a Drive guide, its recipients also need permission to read that file. Receiving the skill copy and gaining access to its reference document are separate steps. The help page directs users to place reference material in Drive and add its link to the instructions, rather than attaching local files directly to a skill. Source Source

Creating, editing, testing and sharing skills are supported on the web. Invocation is supported in Studio, Gmail, Docs, Slides, Drive and Chat on the web, and in Google Chat on Android and iOS. Sheets and Meet are not yet supported. Prompts and instructions currently support English only, a relevant adoption condition for readers whose work is in Korean. Source

Timing depends on an organization’s release track. Rapid Release organizations, which receive features earlier, begin receiving skills on November 9; Scheduled Release organizations begin on November 30. Each gradual rollout can take up to 15 days. Users must be at least 18. Skills are on by default for eligible editions, but administrators can disable them for a domain, organizational unit such as a department, or group. Source Source

Both the announcement and the admin help page list Business Starter, Standard and Plus; Enterprise Standard and Plus; and Google AI Pro for Education. The announcement also lists Enterprise Starter and AI Expanded Access, which are absent from the linked admin page’s supported-edition list. The official guidance still differs on the scope of these two entries. Source Source

Workspace skills are managed separately from skills and Gems in the Gemini app, without automatic synchronization. Google says the automated migration of remaining Gems in 2027 will create draft skills in the Gemini app. To reuse instructions in Workspace as well, users can manually copy them using the shared SKILL.md instruction-file format. This separates the Gemini-app transition from the Workspace rollout described here. Source

OYOPICK’s Take

We welcome the ability to reuse a team’s accumulated writing and working rules across apps. With independent, customizable copies, distributing a standard and keeping everyone current become separate tasks. Departments gain room to adapt a proposal format, while changes to common guidance call for an agreement on which version each person should apply.

For a team that also references Drive material, we think it would be useful to manage the instruction version alongside access to the source files. That suggestion follows from the current independent-copy design. We hope shared-skill screens make differences from the original and newly available versions easier to see, helping teams preserve both individual flexibility and common standards.