You can move a Gemini Gem’s reusable instructions into a Skill in two ways: check whether Google’s account-specific Gems-to-Skills transition is available, or rebuild the workflow for a destination such as Codex using a SKILL.md file. Google says its automatic conversion preserves a Gem’s name, description, custom instructions, and uploaded knowledge files. That does not guarantee that Drive links, app integrations, sharing permissions, or Gemini-specific behavior will work elsewhere. Inventory each Gem, verify the converted result, and adapt the workflow to the tools and file conventions of its destination.
What moves—and what needs checking
Google describes an automatic transition from Gems to Skills. According to its transition guide and Workspace guidance, converted Skills retain the Gem’s original name, description, custom instructions, and uploaded knowledge files. Availability and controls can vary by account and surface, so check the transition instructions shown in your own Gemini account rather than relying on a universal button sequence.
As an Amazon Associate I earn from qualifying purchases.
A Gem is more than its prompt: it may also rely on knowledge files, Drive material, app-specific behavior, and sharing arrangements. Google’s Gems Help covers instructions, knowledge, Drive use, and sharing. Treat conversion as a starting point, then compare the result with an inventory of what the original Gem actually needed.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesA Gemini Skill and a Codex or OpenAI skill are not interchangeable runtimes. Moving instructions does not transfer Gemini’s tools or make their behavior available in Codex. For the latter, package the workflow in the skill format and replace unsupported platform-specific steps.
#1 Best Overall
Inventory each Gem before moving it
Make one inventory entry per Gem. Record the following so you can check a Google conversion or rebuild the workflow for another platform:
- Name and purpose: Preserve the current name and write down the task the Gem is meant to perform.
- Full custom instructions: Keep the original wording available for comparison, including constraints and expected output.
- Knowledge sources: List uploaded files separately from Drive references or other linked materials; note what each source contributes.
- Tools and assumptions: Flag Gemini-only commands, app connections, expected response features, or steps that depend on Workspace access.
- Access needs: Record who should be able to use the Gem or its knowledge, and identify private or sensitive material before sharing it elsewhere.
Check Google’s Gems-to-Skills transition
- Open Gemini and look for the current Skills area and any transition instructions displayed for your account.
- If a Gem has been converted, compare its name, description, custom instructions, and uploaded knowledge files with your inventory.
- Check any Drive references, linked sources, sharing needs, or platform-dependent behavior separately; do not assume that preserved uploaded files mean those other dependencies transferred.
- If the transition control is unavailable or expected content is missing, consult Google’s transition instructions and the current Skills Help for available creation or upload options.
Google documents creating a Skill from a chat or the Skills page and uploading a SKILL.md file, a folder, or a ZIP containing SKILL.md. Its Help page describes gradual availability and account requirements; the precise options may differ by account and surface. Check that page for the current availability relevant to you rather than assuming a rollout date or a fixed set of controls.
Rebuild a Gem as a Codex or OpenAI skill
For a Codex or OpenAI skill, create a directory for the workflow with a SKILL.md file. OpenAI’s Skills documentation and skill-authoring guide describe the format: YAML front matter with a name and description, followed by Markdown workflow instructions. For example:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
---
name: editorial-brief
description: Create a sourced editorial brief from an approved topic and source pack.
---
# Editorial brief
Instructions for the workflow go here.Keep the YAML valid: the description line must not be indented. Use a short, descriptive name and a description that tells the system both what the skill does and when it applies. OpenAI identifies the name and description as important discovery cues.
Rank #3
Write the instructions around the work the skill must perform, not just the original Gem prompt. Include:
- When to use the skill and what inputs it needs.
- The steps to follow and the order in which to follow them.
- The required output format and quality checks.
- Limits on assumptions, invented details, or unsupported actions.
- What to do when information is missing, including whether to ask for it or stop.
Put stable reference material, examples, templates, scripts, or assets in clearly named supporting files or directories such as references/, assets/, and scripts/. Link to those files from SKILL.md and explain when to consult them; do not assume a file is useful merely because it sits beside the instructions.
Translate platform-specific steps instead of copying them
Preserve the Gem’s intended outcome, decision rules, and useful knowledge, but rewrite the mechanics for the destination. For example, an instruction to “search Drive with Gemini” should become a step using an equivalent destination tool only if one is configured. Otherwise, make the Drive content a user-provided input or state that the action is unavailable. The same applies to app connections and expected response features.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →If a Gem contains distinct tasks with different triggers or success criteria, consider splitting it into focused skills rather than carrying over one broad set of instructions. Google documents combining Skills for more complex tasks; that does not remove the need to make each skill’s purpose and boundaries clear.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Gem-to-skill mapping
| Gem element | Google’s Skills transition | Codex or OpenAI adaptation |
|---|---|---|
| Name | Google says the converted Skill retains it. | Use a short, descriptive name in SKILL.md front matter. |
| Description or purpose | Google says the description carries over. | Rewrite it as a precise trigger: what the skill does and when it applies. |
| Custom instructions | Google says the instructions carry over. | Turn them into an ordered workflow with inputs, outputs, constraints, and checks. |
| Uploaded knowledge files | Google says uploaded files are retained in converted Skills. | Place supporting material in references or assets and tell the skill when to use it. |
| Drive or app-specific behavior | Verify supported content and behavior in the converted Skill. | Use a configured destination tool, ask the user to provide the material, or state that the capability is unavailable. |
| Sharing and access | Check current Google sharing and transition behavior. | Set access deliberately for the specific destination workspace and review sensitive files. |
Test the workflow and review access
Before relying on a rebuilt skill, try it with three representative requests: an ordinary case, one with an important input missing, and an edge case. Check whether it is selected for the right task, follows its steps, consults the right references, and returns the required format. If it is missed or triggered too broadly, refine the name or description; if the output is inconsistent, clarify the workflow instructions. This is practical validation, not a reported migration test result.
Before uploading or sharing, check instructions and knowledge files for customer data, private examples, internal procedures, or credentials. Remove secrets and confirm permissions in the destination. Google’s Gem sharing behavior and the access controls for a Codex or OpenAI workspace are separate; confirm each platform’s current settings rather than assuming access carries over.
Choose where the workflow should run
Use Google’s converted Skill if the workflow needs to run in Gemini and the account has access to the relevant transition or authoring options. Rebuild it as a Codex or OpenAI skill when it needs to run in that environment, but only after accounting for tools actually configured there. Before choosing, compare where the workflow must run, which tools it needs, where its references will live, who should access it, how it will be discovered, and who will maintain its instructions and files.
Google announced Skills as reusable workflows in a post published September 30, 2026, but forward-looking statements in an announcement do not establish that sharing, Drive, or Notebook capabilities are available now. Check the current Gemini Skills Help for present account and surface availability. OpenAI’s Skills documentation describes the destination file structure; neither source establishes a migration success rate or a guarantee of feature parity.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
