THE SIGNAL IN ONE SENTENCE
A reusable AI instruction has become easier to pass around. The permission problem came with it. Google announced on November 16 that Gemini users can share skills with viewer or editor access. Skills are reusable instruction packages that Gemini can apply automatically when they seem relevant, or that a person can call directly in a chat. Users can also attach files from Google Drive, Gemini Notebook and Google Photos. Drive files and Notebooks can update in real time, so the skill can keep working from the latest source instead of a frozen upload. That sounds like a small collaboration feature. It changes the object being shared. A skill is no longer only a block of instructions someone copied into a chat. It can be a live bundle made from instructions, attached files, editors, viewers, external sharing rules and source permissions that change after the first person installs it. The useful mental model is not a clever prompt. It is a small shared program with dependencies. Google's announcement says a skill can be shared from the Gemini web app with View or Edit permission. Recipients can review it before adding it. Once active, Gemini may use it automatically when relevant, or the user can mention it directly. The Help Center adds important detail. Sharing creates a copy of the skill in Google Drive. Owners and people with editor access can share it. Editors can change the instructions and uploaded files. Viewers can use the skill and inspect its description, instructions and uploaded files. If the skill includes Drive files, access to those files must be shared separately. That separate step is where many cheerful demos will meet ordinary organizational life. Someone can have permission to open the skill but not the policy document it depends on. Someone can edit the instructions but lack access to the spreadsheet that supplies its categories. An external collaborator may receive the skill under the organization's Drive sharing rules while one attached file remains internal. The result can be partial behavior that looks like model inconsistency when it is really a permission mismatch. Before sharing a skill, make a permission receipt. List the skill owner, every editor, the intended viewers, each attached source, the owner of that source, the access level required and whether external sharing is allowed. Record which files are live links and which are fixed uploads. Add an expiration date for access when the collaboration has an end date. Then test the skill as the recipient. Do not test only from the owner's account, where every door is already unlocked. Use a viewer account, an editor account and, if external sharing is intended, an account outside the organization. Confirm that each person can see the instructions, reach the required files and produce the expected result without gaining access to anything else. This is basic permission engineering. It is also editorial hygiene. When a skill produces a consequential document, the output should preserve a compact receipt: skill name, skill owner, instruction version, source files used, source versions or timestamps, execution date and the person who reviewed the result. Google says Drive files and Notebooks update in real time. That is useful because the skill can work from current material. It also means two runs with the same skill name may not be based on the same evidence. A policy changes at noon. The skill runs at 11:58 and again at 12:04. Both outputs say they used the same skill. One reflects the old policy and one reflects the new one. Without version provenance, the difference is invisible. Treat live sources like dependencies in software. Record what was available at run time. For important workflows, save a snapshot or immutable reference alongside the final output. If the source cannot be frozen, capture its modified time and a content hash when policy permits. The same rule applies to the instructions. Editors can change a shared skill. That is the point of editor access. It is also a reason to separate experimentation from production. A team should not discover during a customer response that someone revised the tone guide, removed a required citation rule or added a new source that contains stale material. Use a simple change path. Keep one production skill with a named owner. Let editors propose changes in a test copy. Run a fixed acceptance set. Review the differences. Then move the approved revision into production and record the effective date. The acceptance set should contain ordinary work and traps. For a customer-support skill, include a common question, an edge case, an outdated policy page, a request that requires escalation and a prompt containing instructions that should not override the skill. For a writing skill, include missing sources, conflicting sources, an inaccessible attachment, a document with sensitive text and a request that tempts the system to invent a fact. For a data skill, include blank cells, duplicate records, changed column names, an expired link and a viewer who can access the skill but not the source sheet. The goal is not to prove that the skill works once. It is to learn how it fails when people and files change. Sharing defaults also deserve attention. Google says skill sharing is on by default for Workspace organizations, though administrators can disable it. Skills follow the organization's Google Drive sharing settings. If Drive files can be shared outside the organization, skills can be shared externally as well. Google also says there is no separate admin control for adding files to skills. That puts more weight on existing Drive governance. Review external sharing rules, link-sharing behavior, group membership, expiration practices and ownership transfer before treating skills as a safe distribution channel. A skill can make access feel like one tidy package even when the underlying permissions remain spread across several systems. Do not confuse tidy with simple. The Help Center says an owner can transfer ownership of a shared skill. If the owner deletes it, the skill is permanently removed for everyone. If a non-owner removes it, the change affects only that person. Ownership therefore belongs in the operating plan. Use a role account or durable team owner for important skills when organizational policy allows it. Name a backup owner. Document what happens when the owner leaves, changes teams or loses access to an attached file. Test deletion and transfer on a disposable skill before the team depends on the workflow. Copies add another wrinkle. If a recipient already has a skill with the same name, Google may let them save a copy. The Help Center says copies do not automatically sync when the original is updated. That is a fork. Give production skills a visible version and owner in the description. If copies are allowed, require the copy to keep a parent reference. Decide whether local edits are permitted and how someone learns that the upstream skill changed. Otherwise the organization will collect several identically named skills that quietly disagree. The 100 MB limit also needs plain interpretation. Google says uploaded files cannot exceed 100 MB per skill. The limit is a technical boundary, not a recommendation to stuff every reference into one bundle. More files create more permission paths, more stale material and more chances for conflicting instructions. Attach only what the skill needs. Prefer authoritative sources over convenience copies. Remove expired material. Give every source an owner and review date. Finally, preserve human review where the output has consequences. A shared skill can improve consistency for briefs, meeting preparation, research, support drafts, analysis and recurring documents. It can also distribute one person's mistake with impressive efficiency. For public, financial, legal, personnel, medical, security or policy work, require a named reviewer. The reviewer should see the skill version and source receipt, not only the polished output. Sharing an instruction package is useful. Sharing the permission map and change history is what makes it dependable. Give viewers only what they need. Give editors a test path. Check the attached files separately. Record the source state. Test from the recipient's account. Keep a person responsible for the result. The skill is the recipe. The permission receipt tells you which kitchen it actually used.
01
WHAT ACTUALLY CHANGED
Google announced shareable Gemini skills on November 16, 2026, with viewer and editor access.
Recipients can review a shared skill before adding it, then use it directly or let Gemini apply an active skill when relevant.
Gemini skills can now include files from Google Drive, Gemini Notebook and Google Photos in addition to device uploads.
Google says Drive files and Notebooks update in real time, so a skill can use the latest available source.
Skill sharing and access management are available in the Gemini web app at launch, not the mobile app.
The Help Center says sharing a skill creates a copy in Google Drive.
Editors can share a skill and change its instructions and uploaded files, while viewers can use it and inspect its contents.
Access to attached Drive files must be granted separately from access to the skill.
Uploaded files are limited to a total of 100 MB per skill.
Google began a gradual rollout for Rapid Release and Scheduled Release domains on November 12, with visibility taking up to 15 days.
Skill sharing is on by default for Workspace organizations but can be disabled by administrators.
Skills follow organizational Drive sharing settings, including the possibility of external sharing when those settings allow it.
Google says there is no separate administrator control for adding files to skills.
02
WHY THIS MATTERS
A shared skill can now combine instructions, live dependencies and several permission systems rather than behaving like a static prompt.
Skill access does not automatically grant access to every attached Drive file, so recipients can receive a package that cannot fully run.
Live files improve freshness but can make two outputs from the same named skill rely on different source states.
Editor access can change behavior for everyone who uses the shared skill, making instruction changes an operational event.
Existing Drive governance becomes part of the skill-sharing boundary, including external sharing and group membership.
Saving a copy can create an unsynchronized fork that keeps the same purpose while missing later fixes.
Ownership transfer and deletion affect the continuity of a shared workflow, especially when a skill belongs to one employee.
Automatic use of active skills makes visibility into the applied skill and its sources important for consequential outputs.
A permission receipt can distinguish a model problem from an inaccessible, stale or differently shared source.
Human review remains necessary because a reusable mistake can spread as efficiently as a reusable improvement.
03
WHERE IT COULD HELP
- Create a permission receipt listing the owner, editors, viewers, attached sources and required access levels.
- Mark every attachment as a live source or a fixed upload.
- Test the skill from viewer, editor and external-recipient accounts instead of only from the owner account.
- Record the skill version, source timestamps and reviewer with consequential outputs.
- Keep a test copy and a fixed acceptance set before changing a production skill.
- Add inaccessible files, outdated sources and conflicting versions to the acceptance set.
- Use a durable team owner and name a backup for important shared skills when policy allows it.
- Set access expiration dates for temporary collaborators.
- Review organizational Drive sharing rules before enabling external skill sharing.
- Give copied skills a parent reference and a clear local version.
- Notify users when the production skill or one of its live dependencies changes.
- Keep attachments narrow, authoritative and owned rather than filling the 100 MB allowance.
- Capture a source snapshot, modified time or content hash when reproducibility matters.
- Require a named reviewer for public, financial, legal, personnel, medical, security and policy outputs.
- Test ownership transfer and deletion on a disposable skill before relying on the workflow.
KEEP A HAND ON THE WHEEL
Google began the rollout on November 12 and says feature visibility may take up to 15 days. Availability can therefore differ across accounts on the same date. Sharing and access management are web-only at launch. The Help Center says skills themselves can be used on supported Gemini surfaces, but the sharing controls described here remain in the web app. Drive file access must be shared separately. A skill can appear available while one or more dependencies remain unavailable to the recipient. Live Drive files and Notebooks improve freshness but can reduce reproducibility unless the workflow records the source state used for each important output. Skills follow an organization's Drive sharing settings. Administrators can disable skill sharing, but Google says there is no separate admin control for adding files to skills. Watch for stronger version history, dependency visibility, administrator reporting, recipient-side warnings for inaccessible sources, clearer receipts showing which skill was applied and independent testing of how shared skills behave when permissions or files change during a workflow.
04
TERMS WORTH KEEPING
OPEN GLOSSARY CARD
Version provenance
A record showing which people, sources, tools, instructions, and changes produced a particular version of an artifact.
OPEN GLOSSARY CARD
Permission scope
The specific systems, records, fields, users, and actions that an account or software connection is allowed to access.
OPEN GLOSSARY CARD
View-only access
Permission to inspect something without changing, deleting, or publishing it.
SOURCES AND VERIFICATION STATUS
This article was written from the materials below. Product claims and dates were checked against those sources on November 17, 2026.
THE PUBLICATION ENGINE
WANT A SIGNAL OF YOUR OWN?
We build source-grounded publications, private briefings, and editorial systems for organizations with something useful to say.
WORK WITH US