New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Google Docs, Sheets and Slides Editing

by asgeirtj in asgeirtj/system_prompts_leaks

Guidance for creating and editing Google Docs, Sheets and Slides through connectors, with per-app API rules and helper scripts for positions, ranges and slide layout.

CC0-1.0Auto-check: warningsDocuments & Office

Install Google Docs, Sheets and Slides Editing

The automated check flagged lines worth reading first. See the safety section below.

skills CLI
$ npx skills add asgeirtj/system_prompts_leaks --skill google-workspace -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install asgeirtj/system_prompts_leaks google-workspace --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/asgeirtj/system_prompts_leaks.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Anthropic/claude-code/skills/google-workspace .claude/skills/google-workspace && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
google-workspace
GitHub stars
69k
Token cost
~3.7k tokens
SKILL.md length
2,286 words
Files
9 (incl. scripts, references)
Skills in repo
128
Repo updated
First seen
Licence
CC0-1.0

At a glance

Guidance for creating and editing Google Docs, Sheets and Slides through connectors, with per-app API rules and helper scripts for positions, ranges and slide layout.

  • Works in 6 steps: Check the connectors before you start → Rules for every file → Drive, for all three apps → …
  • Editing an existing Google Doc in place, directly or as suggestions
  • SKILL.md covers Read the reference before you…, 1. Check the connectors before…, 2. Rules for every file and 3. Drive, for all three apps, plus 3 more sections
  • Runs Python scripts from its folder

What it does

This skill supplies the guidance that Google's thin connector wrappers lack: which connector does what, the rules that keep edits inside the user's existing file, and one reference file per app describing how each API actually behaves. The agent is told to read the reference for every app a task touches before the first edit, for example both the Sheets and Slides references when embedding a chart in a deck.

The references flag common traps. Docs edits use UTF-16 positions that shift after each insert and go stale after each write, and tabs and pending suggestions change them. Sheets writes are parsed like the Sheets UI, so text can silently become numbers or dates, and formatting needs numeric sheet IDs, 0-based ranges and field masks. In Slides, positions are in EMU, an element's real size is its size times its scale, and text is never shrunk to fit.

Helper scripts cover document positions, cell ranges and slide layout, plus rendering an export. Drive can create all three file types but cannot edit them afterward, so without the matching editor connector every change would mean a new file and a new link. The skill is not for read-only questions about a Google file or for Word, Excel, PowerPoint and PDF files.

When your agent uses it

  • Editing an existing Google Doc in place, directly or as suggestions
  • Writing values, formulas or formatting into a Google Sheet
  • Adding or changing slides, shapes and text in a Google Slides deck
  • Following up on an earlier Google file edit with a request like adding a tab
  • Embedding a Sheets chart in a Slides deck

Example prompts

  • “Fix the typo in the second paragraph of this Google Doc and leave it as a suggestion.”
  • “Add a Totals tab to the sales Google Sheet with formulas summing each month.”
  • “Add a title slide and an agenda slide to my Google Slides deck for Monday's review.”
  • “Format the header row of the budget sheet in bold with a gray background.”

Requirements

  • Google Drive, Docs, Sheets and Slides connectors with access to the user's files
  • Python to run the bundled helper scripts

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Check the connectors before you start
  2. Rules for every file
  3. Drive, for all three apps
  4. Helper scripts
  5. Common failures across apps
  6. What the connectors can't do

What it can do on your machine

Read from SKILL.md and the folder at commit 60d44cc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 4 files in scripts/ (Python), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Google Docs, Sheets and Slides Editing loads about 3.7k tokens when it runs, and up to ~39k if it reads all its reference files. Until then it costs about 240 tokens; SKILL.md has 2,286 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~240
When it runs · the whole SKILL.md, loaded when a task matches
~3.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~39k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: warnings

The automated check found patterns that need a careful read before installing.

  • WarningContains instruction-override wording (e.g. “without asking the user”)SKILL.md:48
    file, even if a result said they could. Don't tell the user to use a card or preview unless a result said one is shown.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from asgeirtj/system_prompts_leaks at commit 60d44cc, republished under its CC0-1.0 licence (© asgeirtj). 2,286 words, ~3,716 tokens.

Download SKILL.mdSave it as .claude/skills/google-workspace/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.
name
google-workspace
description
Read this before the first Google Drive, Docs, Sheets or Slides connector call whenever the task creates or changes a Google file. Use this skill whenever the user wants to create or change a Google Doc, Sheet or Slides file in their Google Drive. Triggers include: a request that names Google Docs, Sheets, Slides or Drive and asks to make, edit, format, copy or rename a file; a docs.google.com link with a request to change that file, even a one-line fix or suggested edits; and any follow-up change to a Google file from earlier in the chat, even "change it" or "add a tab". Includes helper scripts for document positions, cell ranges and slide layout. However, if the user asks for a doc, deck or spreadsheet without naming Google, or gives a Google file only as source material for something new, use Claude's own output type instead. Do NOT use for read-only questions about a Google file, or for Word, Excel, PowerPoint or PDF files.

Google Docs, Sheets, and Slides

The Google connectors are thin wrappers over Google's raw APIs, with almost no guidance of their own. This skill supplies that guidance: which connector does what, the rules that keep edits in the user's file, and, in one reference file per app, how each API really behaves. Most of the app-specific rules in the references were tested against Google's Docs, Sheets and Slides APIs; the rest were seen through the connectors, and a few have not been checked yet.

Read the reference before you touch the file

Working onRead firstWhy it matters
A Google Docreferences/docs.mdDocs edits address UTF-16 positions that shift after every insert and go stale after every write. Tabs and pending suggestions change the positions too.
A Google Sheetreferences/sheets.mdBoth write tools parse input like the Sheets UI, so text can silently become numbers or dates. Formatting needs numeric sheet IDs, 0-based ranges, and field masks without parentheses.
A Google Slides deckreferences/slides.mdPositions are in EMU, an element's real size is its size times its scale, and an unmasked read can exceed 150 KB for three slides. Slides never shrinks text to fit.

Read the reference for every app the task touches before the first edit. Embedding a Sheets chart in a deck means reading both. The references are short, and skipping one is how edits land in the wrong place.

1. Check the connectors before you start

ConnectorWhat it can do
Google DriveCreate files, upload and convert content, rename, read a file as text, export (PDF and other formats), search, trash
Google DocsRead a doc's full structure and edit it in place, directly or as suggestions
Google SheetsRead values and structure, write values and formulas, format, add tabs and charts
Google SlidesRead a deck, add and edit slides, shapes, text, tables, and linked charts

Drive can create all three file types. It can't edit a file after that. Without the matching editor connector, every change means a new file and a new link, and the user loses the link they already have.

  1. Check which Google tools are available in this conversation. On surfaces where tools are deferred, search for and load the tools you need first, such as "google sheets update". Tool names differ by surface, so use the names your surface lists. If a search returns nothing, list all available tools before deciding the connector is missing, because the tool may exist under a different name.
  2. If the editor tools are missing, tell the user. When you can list the conversation's connectors, say which case it is: a connector that is set up but turned off in this chat (ask them to turn it on in the chat's connector settings, then continue), or one that isn't connected at all (tell them which connector to add and what it enables).
  3. With an editor connector missing, a request to create a new file continues with Drive. A change to an existing file stops and asks. See the missing-connector rule in section 2.
  4. If the user asks only for a new file, create it with Drive. If the editor connector is off, add one line saying edits will need it.

Example: "I can create the sheet now. If you want changes later, turn on the Google Sheets connector in this chat first. Then I can edit this file, and the link will stay the same."

2. Rules for every file

  • A change goes in the same file. "Change", "update", "fix", "add", and "switch it to" all mean the user wants the same file and link. Do not recreate the file to skip an edit.
  • A missing editor connector is a choice for the user, not a workaround for you. When the user asks for a change to an existing file and the editor connector is missing, your whole reply is a short question, not a deliverable. Building the next-best thing feels helpful, but the user's file is still untouched and now there are two artifacts, which is the exact failure this skill exists to prevent. Lead with the fix: name the connector and say that with it on, the edit lands in their existing file and the link stays the same. You may offer an alternative, such as drafted text to paste or a file to import by hand, but only as a named option, and build it only after the user picks it. Example reply, in full: "To add the slide to your deck directly, turn on the Google Slides connector in this chat and I'll do it. Same deck, same link. Or I can draft the slide as a file you'd import by hand. Which do you prefer?"
  • Never trash a file the user didn't ask you to delete. Drive can trash a file, but it can't restore one. The Docs, Sheets, and Slides connectors can't open a trashed file.
  • Read before you edit, and guard the write. Send every Docs and Slides batch with writeControl.requiredRevisionId set to the revisionId from a read taken after your last write, including batches built on IDs or positions from your own earlier writes. The only exception is a batch made entirely of replaceAllText requests, even one limited to some tabs or slides. If the file changed since that read, whether from your own write or someone else's, Google rejects the whole batch instead of applying it at stale positions or IDs. Read again before each guarded batch, and don't reuse a revision ID from a write reply. On a rejection, read again and rebuild; never drop the guard. read_doc and read_presentation (the mask in references/slides.md includes it) return the ID. read_slide_page returns it only if its mask includes revisionId; read_slide_page_thumbnail and Drive read_file_content never do. For a saved read, the first line of docs_index.py outline or slides_helper.py outline shows it; if that line says None, read again with read_doc or read_presentation. get_spreadsheet returns a revisionId even with a field mask, but don't send it: send Sheets writes without writeControl, and read again right before a write that depends on positions.
  • Put everything for one step in one batch. Batch requests run in order and atomically: if one is invalid, none apply. One call per logical step is faster and leaves no half-finished state.
  • Sheets field masks. Write each path in full, with no parentheses: one path per item in get_spreadsheet's fields list (["spreadsheetId", "sheets.properties"]), and comma-separated in a batch update request's fields string ("userEnteredFormat.numberFormat,userEnteredFormat.textFormat.bold").
  • Verify the result. Read the file again after each edit and check the result before you report it. A tool accepting the call does not mean the content is correct. Each reference has a Verify section.
  • Rename with Drive update_file. A rename keeps the same link.
  • Link every file you name. When you name a Google file you created, copied, found, or edited, make its title a link, inside the sentence that says what you did: "I added the row to [Team roster](its link)." Don't set the file apart after a colon or on a line of its own ("I've created a file for you: Team roster"). If a Drive result says the user can already see or open a file from the chat, leave that file's link out unless they ask. Always give the link when the user asks for it, wants to send it to someone, or says they can't see or open the file, even if a result said they could. Don't tell the user to use a card or preview unless a result said one is shown. After an edit, say that the link stays the same.

3. Drive, for all three apps

  • Find a file: use Drive search when the user names a file without a link. Confirm the match with the user if more than one file fits.
  • Create: create_file with contentMimeType set to application/vnd.google-apps.document, .spreadsheet, or .presentation creates an empty file. Uploading content with a source type (HTML, CSV, .xlsx, .pptx) converts it into the matching Google type. Each reference says which route fits that app.
  • Read as text: read_file_content returns a compact text rendering: Markdown for a Doc. It is a few KB where the editor connector's full read can be over 100 KB, so use it to understand content, then use the editor read when you need positions.
  • Export: download_file_content with exportMimeType: "application/pdf" returns the rendered file as base64. It is large (about 65 KB of text for a four-slide deck), so export only for a visual check, and only where you can run code.
Show full SKILL.md (858 more words)Show less

4. Helper scripts

The scripts/ folder next to this file holds tested helpers. They turn the APIs' raw JSON into short readable summaries, and turn simple specs into correct request batches, so the error-prone arithmetic never happens by hand. Use them wherever you can run Python. Run them by their full path inside this skill's folder; the references write that folder as <skill>.

ScriptCommandsUsed for
docs_index.pyoutline, find, new-table, fill-tableDocs positions, text search with bold and suggestion state, adding a filled table in one call, filling an existing table
sheets_helper.pyrange, format, cellsA1 ranges to grid ranges, formatting batches from a short spec, reading formulas and error cells
slides_helper.pyoutline, buildReal slide geometry with overflow and overlap warnings, building slides from an inch-based spec
render_export.pyone commandDecoding a PDF export into page images to look at

Getting JSON to a script. Large tool results are often saved to a file by the app, and the result tells you the path. Point the script at that path; the scripts read the file as the app saved it. When a result comes back in context and is small (a few KB, such as a masked read or sheet metadata), write it to a file and run the script on it. Don't re-type a large result into a file: that doubles the cost and invites copying errors. If a large result was cut off and not saved, read a smaller slice instead (a field mask, a range, or one tab) rather than guessing.

Every script prints --help with its full usage. Each reference shows the commands in context.

5. Common failures across apps

SymptomCauseFix
"No such tool available"The tool is deferred, or the name is different on this surfaceSearch for and load the tool. Use the exact name your surface lists.
Permission denied on a file you createdThe file is in the trashAsk the user to restore it from Drive's trash. You can't restore it with the connectors.
400: required revision ID does not matchThe file changed after your read: your own previous write, or someone else editingRead again, rebuild the requests from the new read, and send them with the new revision. For Sheets, send them without writeControl.
A whole batch failed on one bad requestBatches are atomicFix the named request and resend the full batch. Nothing from the failed call was applied.
A read is too large or cut offUnmasked editor reads include everythingUse Drive read_file_content, a field mask, a range, or a single tab. Run the helper on a saved result.
Two files where the user expected oneAn edit was done by creating a new fileMake changes in place with the editor connector. Tell the user about the extra file; don't trash it without asking.

Each reference ends with the failures specific to that app.

6. What the connectors can't do

When a request runs into one of these, say so plainly and do the alternative. Reported: seen through the connectors or in their tool schemas. Untested: not yet checked.

  • Claude can't see the user's screen. No connector shows what the user has selected, or which file, tab or slide they have open. If "this" or "here" isn't clear from the chat, ask which file, heading, slide number or cell range they mean. Reported.
  • Comments: read_doc has returned no comments even with commentsIncluded: true. To read comments, use Drive read_file_content with includeComments: true, or ask the user to paste them. update_doc has accepted insertComment in one report, although its description is cut before listing it; if that request fails, say you can't add comments and offer to list your notes in the reply. Reported.
  • Suggestion mode can be refused with "Unsupported WriteControl mode". Never make direct edits in its place: offer to list the proposed changes or to edit directly (see references/docs.md). Reported.
  • Request lists are cut short. The update_doc, update_spreadsheet and update_presentation descriptions stop partway through their request lists. Requests missing from the description, such as addDocumentTab and addChart, have still worked, so try one before deciding it isn't supported. Reported.
  • Uploads travel inside the call. create_file takes the whole file as text or base64, so an .xlsx or .pptx upload is slow and often fails. Build in the file with the editor connectors where you can, and keep uploads small. Reported.
  • Images need a public URL. Slides createImage and Docs insertInlineImage fetch the image from a URL Google can reach; a file from the chat can't be inserted this way. For a deck, offer the .pptx route; otherwise ask the user to insert the image. Untested.
  • A Slides chart must already exist in a Sheet. Create it there with addChart, then embed it with createSheetsChart. Reported.
  • Drive search uses title, not name. name contains '…' fails with "Unsupported query field: name"; write title contains '…', and put the file type in a mimeType clause. Reported.
  • Slides edits may not show in an open deck right away. If the user doesn't see a change, ask them to reload the deck before you change anything again. Reported; may be fixed.

© asgeirtj, CC0-1.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 8 other files (scripts, references) in Anthropic/claude-code/skills/google-workspace of asgeirtj/system_prompts_leaks.

  • SKILL.md
  • references/charts.md
  • references/docs.md
  • references/sheets.md
  • references/slides.md
  • scripts/docs_index.py
  • scripts/render_export.py
  • scripts/sheets_helper.py
  • scripts/slides_helper.py

Open the folder on GitHubat commit 60d44cc

Compare with similar skills

Google Docs, Sheets and Slides Editing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Google Docs, Sheets and Slides Editing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Google Docs, Sheets and Slides Editing this skillasgeirtj/system_prompts_leaks69k—~3.7kAutomated safety check: WarnCC0-1.0
Chart To Driveai-analyst-lab/ai-analyst304—~1.4kAutomated safety check: PassMIT
Google Workspaceespennilsen/pi122—~3.4kAutomated safety check: PassMIT
Managing Google Workspacetaylorwilsdon/google_workspace_mcp3.3k—~2.9kAutomated safety check: PassMIT
Gwskv0906/pm-kit138—~1.6kAutomated safety check: PassMIT
Auth Preflightai-analyst-lab/ai-analyst304—~3.1kAutomated safety check: PassMIT

Similar skills

  • Chart To Drive

    ai-analyst-lab/ai-analyst

    Standardized workflow for uploading local chart PNGs to Google Drive and making them available for insertion into Google Docs and Slides.

    304 GitHub stars~1.4k tokensUpdated 9 days ago
    Documents & OfficeAuto-check passed

  • Google Workspace

    espennilsen/pi

    Manage Google Workspace via the gws CLI — Drive, Gmail, Sheets, Docs, Slides, People, Chat, Meet, Forms, and cross-service workflows.

    122 GitHub stars~3.4k tokensUpdated 18 days ago
    Documents & OfficeAuto-check passed

  • Managing Google Workspace

    taylorwilsdon/google_workspace_mcp

    Manages Google Workspace operations across 12 services (Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts, Chat, Apps Script, Custom Search).

    3.3k GitHub stars~2.9k tokensUpdated today
    Documents & OfficeAuto-check passed

  • Gws

    kv0906/pm-kit

    This skill should be used when the user asks to "set up gws", "install Google Workspace CLI", "connect Gmail to Claude", "manage Google Drive from terminal", "send email from CLI", "check my…

    138 GitHub stars~1.6k tokensUpdated 3 mo ago
    Documents & OfficeAuto-check passed

  • Auth Preflight

    ai-analyst-lab/ai-analyst

    Verify Google Workspace MCP authentication at the start of any session that needs Google APIs (Docs, Slides, Drive).

    304 GitHub stars~3.1k tokensUpdated 9 days ago
    Documents & OfficeAuto-check passed

  • Google Workspace Ops

    affaan-m/ECC

    Operate across Google Drive, Docs, Sheets, and Slides as one workflow surface for plans, trackers, decks, and shared documents.

    276k GitHub starsUsed in 2 repos~684 tokens
    Documents & OfficeAuto-check passed

More from asgeirtj/system_prompts_leaks

All 128 skills in this repo

  • Fleet Manager for Agent Sessions

    asgeirtj/system_prompts_leaks

    Shows one digest of coding-agent sessions across your connected machines and lets you open, read, steer, approve, stop and close them, over Herdr, tmux or MSP.

    69k GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Muse Code Product Doctor

    asgeirtj/system_prompts_leaks

    Diagnoses a Muse Code installation's own failures from binary and session evidence, instead of treating the report as an ordinary repository bug.

    69k GitHub stars~3.5k tokensUpdated today
    Auto-check passed

  • DOCX

    asgeirtj/system_prompts_leaks

    A skill your agent uses whenever the user wants to create, read, edit, or manipulate Word documents (.docx) or Word templates (.dotx).

    69k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Agents Project Coordinator

    asgeirtj/system_prompts_leaks

    Runs a goal as a project in which the agent coordinates separate agent threads, judging when to split the work, and interviews you first when nothing can be verified.

    69k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Muse Plugin Creator

    asgeirtj/system_prompts_leaks

    Creates and validates a new native Muse plugin package in the current workspace, limited to five capability families, and leaves installation to you.

    69k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Deep Research

    asgeirtj/system_prompts_leaks

    A skill your agent uses when the user's prompt requires (1) researching a topic across multiple sources, comparing options or alternatives, analyzing trends or history, understanding markets or…

    69k GitHub stars~3.3k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Google Docs, Sheets and Slides Editing

What does Google Docs, Sheets and Slides Editing do?

Guidance for creating and editing Google Docs, Sheets and Slides through connectors, with per-app API rules and helper scripts for positions, ranges and slide layout. This skill supplies the guidance that Google's thin connector wrappers lack: which connector does what, the rules that keep edits inside the user's existing file, and one reference file per app describing how each API actually behaves. The agent is told to read the reference for every app a task touches before the first edit, for example both the Sheets and Slides references when embedding a chart in a deck.

When should I use Google Docs, Sheets and Slides Editing?

Google Docs, Sheets and Slides Editing fits situations like: editing an existing Google Doc in place, directly or as suggestions; writing values, formulas or formatting into a Google Sheet; adding or changing slides, shapes and text in a Google Slides deck; following up on an earlier Google file edit with a request like adding a tab.

How do I install Google Docs, Sheets and Slides Editing in Claude Code?

Run `npx skills add asgeirtj/system_prompts_leaks --skill google-workspace -a claude-code`. Or copy the skill folder (Anthropic/claude-code/skills/google-workspace in asgeirtj/system_prompts_leaks) into .claude/skills/google-workspace in your project. Claude Code loads it when a task matches its description.

How do I install Google Docs, Sheets and Slides Editing in Codex?

Run `npx skills add asgeirtj/system_prompts_leaks --skill google-workspace -a codex`. Or copy the skill folder (Anthropic/claude-code/skills/google-workspace in asgeirtj/system_prompts_leaks) into .agents/skills/google-workspace in your project. Codex loads it when a task matches its description.

Can I use Google Docs, Sheets and Slides Editing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add asgeirtj/system_prompts_leaks --skill google-workspace -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/google-workspace, .gemini/skills/google-workspace, .github/skills/google-workspace and .opencode/skills/google-workspace in your project.

What does Google Docs, Sheets and Slides Editing need to run?

Going by SKILL.md and its folder, Google Docs, Sheets and Slides Editing needs Python for the scripts in its folder. Our summary lists: Google Drive, Docs, Sheets and Slides connectors with access to the user's files; Python to run the bundled helper scripts.

Does Google Docs, Sheets and Slides Editing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Google Docs, Sheets and Slides Editing safe to install?

Our automated static check of SKILL.md flagged 1 warning(s): contains instruction-override wording (e.g. “without asking the user”). Read the flagged lines before installing; the check is not a guarantee either way. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Google Docs, Sheets and Slides Editing use?

Google Docs, Sheets and Slides Editing is published under the CC0-1.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Google Docs, Sheets and Slides Editing use?

About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 35k tokens, read only when the agent opens those files.

What are the alternatives to Google Docs, Sheets and Slides Editing?

Skills that share tags, products or a category with Google Docs, Sheets and Slides Editing: Chart To Drive (ai-analyst-lab/ai-analyst, 304 stars), Google Workspace (espennilsen/pi, 122 stars), Managing Google Workspace (taylorwilsdon/google_workspace_mcp, 3.3k stars) and Gws (kv0906/pm-kit, 138 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Google Docs, Sheets and Slides Editing?

asgeirtj (a GitHub user) maintains it in asgeirtj/system_prompts_leaks, which has 69,280 GitHub stars. The repository holds 128 skills in this directory. The repository was last updated on October 10, 2026.

Source: asgeirtj/system_prompts_leaks on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.