# Gems to Gemini Skills: Check Missing Files Before December 17

Gems become read-only for personal adult accounts on November 17. Audit migrated skills, recover missing knowledge files and test the replacement workflow.

By Paras Madan | 2026-11-17

If your Gem stops working today, check the migration before rewriting its instructions. The useful next step is a file and workflow audit, not assuming that an automatically created skill contains everything your Gem used.

This guide uses Google's documentation. The review process and test examples are proposed, not results from a hands-on account migration.

## Check your account and the recovery deadline

Google's [transition guidance](https://support.google.com/gemini/answer/18560919?hl=en) sets November 17, 2026 as the read-only transition for personal users aged 18 or over: they can access Gems, but not use or edit them. Gems and their files become unavailable in Gemini Apps on December 17. Work and nonprofit accounts transition in March 2027; education accounts follow in June. Under-18 personal accounts have a later, unspecified date.

Automatic migration includes supported files, but the 100 MB total limit can remove the largest files first. GitHub files, audio, video, legacy Office formats and archives do not transfer. Compare the old Gem and new skill side by side, downloading missing files before the deadline.

Put that comparison ahead of cosmetic edits. A familiar name and an apparently correct description can make an incomplete replacement look ready. Start with the Gem you rely on most often, especially if its answers depend on reference material rather than general writing preferences.

## Make a simple file audit

I would keep a small local record with one row per original file: its name, whether the replacement includes it, whether a backup opens correctly and what task depends on it. A count alone is not enough. Losing one important policy document can matter more than preserving ten old examples.

For an unsupported document, retain the original before attempting a conversion. Then inspect the converted copy yourself. Tables, footnotes and slide notes deserve particular attention because a technically successful conversion can still remove the information your workflow needs.

For audio or video, decide whether a reviewed transcript is an adequate substitute. Do not quietly replace a visual demonstration with text and assume the same questions will remain answerable. Record what the substitute leaves out.

## Repair only what you need

Google's [skill-management documentation](https://support.google.com/gemini/answer/17094296) describes the Customize, then Skills page, including manual creation and skill uploads. A packaged skill needs `SKILL.md` in its root folder and a lowercase, hyphenated name. Supported reference formats include PDF, DOCX, XLSX and PPTX. Check the current format list before preparing replacements.

Keep the initial repair small. Restore the missing reference needed for your most important task, then test that task before reorganizing everything else. This separates migration problems from changes you introduced during cleanup.

If the interface exposes a different file-editing path, follow the controls available in your account and verify the saved result. Google's help currently describes both direct file controls and whole-skill replacement, so this guide does not assume every account has an identical upload experience.

## Test behavior, not just file presence

Google's [Skills announcement](https://blog.google/products-and-platforms/products/gemini/automate-tasks-with-skills/) explains that skills can be selected within a chat and combined. That changes the review question: you need to know which instructions are being applied, not simply whether the old Gem has a new name.

Use three harmless examples from your normal work. One should depend on a distinctive fact in a reference file. Another should test an exception, such as a request your process normally excludes. The third should omit information that the workflow needs.

For example, a proposed client-brief test could ask for a summary without providing a delivery date. Check that the response identifies the missing date rather than inventing one. Compare its formatting with your actual template and inspect the factual claims against the source yourself.

Google's [skill-writing guidance](https://support.google.com/gemini/answer/17102773) recommends clear usage descriptions and explicit handling of missing information. If you revise the instructions, change one issue at a time and rerun the same examples. Keep a short note of what passed so future edits do not erase a working behavior.

## Keep a manual fallback until the replacement passes

The transition page warns that skills do not yet support several Gem tools, including Canvas and Deep Research. A successful file transfer therefore does not prove full workflow compatibility.

Separate “instructions recovered,” “files recovered” and “task works” in your review. Only the last one establishes that you can rely on the replacement. For a recurring deadline, keep a manual fallback while you check the new skill, and finish recovery before the cutoff.

I'm Paras. I work at the intersection of AI, engineering and distribution.

I help developer-tool teams explain migrations and product changes clearly.

[Book a 30-minute call](https://cal.com/paras-madan/30min).
