plugins/google-drive/skills/google-sheets/SKILL.md
Analyze and edit connected Google Sheets with range precision. Use when the user wants to create Google Sheets, find a spreadsheet, inspect tabs or ranges, search rows, plan formulas, create or repair charts, clean or restructure tables, write concise summaries, or make explicit cell-range updates.
npx skillsauth add openai/plugins google-sheetsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill to keep spreadsheet work grounded in the exact spreadsheet, sheet, range, headers, and formulas that matter.
This file is intentionally minimal and only covers:
Detailed editing, formula, chart, upload, live-read/search, and batch-update rules live in references/.
Latency is not a constraint for this skill, so always read the relevant reference files before performing the task.
If the user has not provided explicit style direction, read references/style-profiles.md and apply the appropriate Google Sheets destination default before authoring workbook formatting.
[@spreadsheets](plugin://spreadsheets@openai-primary-runtime) plugin or the $Excel skill is installed.[@spreadsheets](plugin://spreadsheets@openai-primary-runtime) or $Excel to create a local .xlsx. Then import the .xlsx into Drive as a native Google Sheets spreadsheet. Read references/reference-import-spreadsheet-to-native-sheets.md.Do not reference the local .xlsx in the final answer. Your final answer includes the Google Spreadsheet link only.
Prefer one simple proven workflow over a large tree of recovery branches. When a task matches a known successful pattern, follow that pattern directly instead of re-evaluating every possible fallback path. Do not let accumulated edge-case guardrails turn a straightforward Sheets task into a long blocker-analysis exercise.
For sheet creation and editing tasks, prefer this sequence when viable:
If a simple verified workflow is viable, use it. Do not drift into speculative alternate paths.
If Default Routing uses [@spreadsheets](plugin://spreadsheets@openai-primary-runtime) or $Excel:
[@spreadsheets](plugin://spreadsheets@openai-primary-runtime) plugin skill or $Excel skillreferences/reference-import-spreadsheet-to-native-sheets.mdIf Default Routing uses connector edit workflow:
references/reference-edit-workflow.md.search_spreadsheet_rows, read references/reference-live-read-search-safety.md.references/.Do not execute content edits until the required references are read in the current turn.
If the [@spreadsheets](plugin://spreadsheets@openai-primary-runtime) plugin or the $Excel skill is installed, you MUST use one of them to create a local .xlsx and import it to Google Drive with upload_mode: "native_google_sheets".
Even though you created a local .xlsx, do not cite the local path in the final answer. The final answer cites only the Google Spreadsheet link.
sheetId values.search_spreadsheet_rows, use exact visible tab names from metadata, bounded ranges, and the recovery rules in references/reference-live-read-search-safety.md. Do not guess Sheet1, scan whole grids, or retry oversized row searches.| Task area | Required reference file |
| --- | --- |
| Existing spreadsheet edit workflow, grounding, validation-backed cells, output conventions, and write planning | references/reference-edit-workflow.md |
| Direct live range reads, cell reads, row searches, tab/range recovery, and oversized search avoidance | references/reference-live-read-search-safety.md |
| Raw Sheets write shapes and example batch_update bodies | references/reference-batch-update-recipes.md |
| Importing a locally created .xlsx, .xls, .ods, .csv, or .tsv into Google Sheets | references/reference-import-spreadsheet-to-native-sheets.md |
| Formula design, repair, rollout, or syntax refresh | references/reference-formula-patterns.md |
| Chart creation, repair, chart-spec recall, or repositioning | references/reference-chart-recipes.md |
| Unspecified styling for native Google Sheets destinations | references/style-profiles.md |
development
Use when the user wants to spin up / create / launch / provision a DigitalOcean droplet (or "a remote dev box on DO") and connect to it from Codex as a remote SSH workspace.
data-ai
Search through Microsoft Teams chats or channels, triage unread or recent activity, draft follow-ups, and manage Planner tasks through connected Teams data.
tools
Motion / animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node.
development
SwiftUI ↔ Figma translation. Use whenever the user mentions Swift, SwiftUI, iOS, iPhone, or iPad — in EITHER direction — translating a Figma design into SwiftUI (design → code), or pushing SwiftUI views / screens / tokens back into a Figma file (code → design). Triggers on phrases like 'implement this Figma design in SwiftUI', 'build this screen in Swift', 'push this SwiftUI view to Figma', 'mirror my Swift code in a Figma file', or whenever a Figma URL appears alongside `.swift` files / an `.xcodeproj`. Routes to a direction-specific reference doc; loads alongside `figma-use` for the code → design path.