Migrating Opal Workflows to Skills

Quick Start

Opal workflows stop running November 17, 2026. Workflow files persist in Google Drive under My Drive > Opal. Before that date:

1. Inventory all Opal workflows in Drive.
2. Extract the logic (inputs, steps, outputs) from each workflow.
3. Re-implement each as a Gemini skill (or equivalent custom skill format).
4. Validate parity, then retire the Opal version.

Workflow

Progress:

• Step 1: Locate all workflow files in Google Drive (My Drive > Opal)
• Step 2: For each workflow, document its purpose, trigger conditions, inputs/outputs, and step-by-step logic
• Step 3: Identify dependencies (connected apps, APIs, other workflows it calls)
• Step 4: Draft the equivalent Gemini skill, mapping each Opal step to a skill instruction or tool call
• Step 5: Test the new skill against the same inputs the Opal workflow used; compare outputs
• Step 6: Fix gaps (Opal-specific features without a direct Gemini equivalent) — note workarounds
• Step 7: Archive or export the original Opal workflow file for reference before Nov 17, 2026
• Step 8: Decommission reliance on the Opal workflow once parity is confirmed

Examples

Example 1: Input: An Opal workflow "Weekly Report Generator" that pulls data from a sheet, summarizes it, and emails a formatted digest. Output: A Gemini skill named generating-weekly-reports with description "Generates a weekly summary digest from a spreadsheet and drafts an email. Use when a recurring weekly report is needed." Steps translated: read sheet → summarize → format → draft email, matching the original workflow's logic.

Example 2: Input: User asks "I have 5 Opal workflows, how do I know which ones still matter?" Output: A triage checklist — check last-run date, list workflows actively used in past 30 days, prioritize migrating those first, archive unused ones without porting them.

Best Practices

• Start migration well before the deadline; don't wait until November 2026.
• Treat each Opal workflow as a spec, not just code to copy — capture intent, since Opal and Gemini skills may structure logic differently.
• Keep the original Opal workflow file in Drive as a reference/backup even after migrating.
• Test migrated skills against real past inputs/outputs from the Opal workflow to confirm behavioral parity.
• Prioritize migration by usage frequency and business criticality, not just by order in Drive.

Common Pitfalls

• Waiting until close to Nov 17, 2026 — active workflows simply stop running after that date, with no grace period.
• Assuming workflow files in Drive remain runnable — they are stored, not executable, after graduation.
• Migrating word-for-word without verifying the new skill produces equivalent outputs.
• Forgetting to document external dependencies (connected sheets, APIs, email accounts) that the new skill will also need configured.