Agent skill for targeted Google Workspace edits

Make targeted edits to the Google files you already have.

Ask for a specific edit to a Google Doc, Sheet, or Slides file. DocuPuncture prepares an Apps Script for you to review and run against the existing file, preserving surrounding structure where the edit type supports it.

You review and run the script in Apps Script. Start with a dry run. The skill does not grant Google access, and preservation depends on the operation.

Move a pilot date without rebuilding the proposal

Illustrative Google Docs edit. You provide the existing text and requested change; the agent prepares a script for the same document.

1 · Existing proposal One date needs to change

Pilot schedule
Pilot begins on 4 May.
The review meeting stays on 18 May.

The request is to move the pilot start to 11 May. The surrounding proposal stays in place.

2 · Script to review Target that sentence and dry-run first

Excerpt of the generated Apps Script settings:

const DRY_RUN = true;
const before = "Pilot begins on 4 May.";
const after = "Pilot begins on 11 May.";

The script must find that text exactly once. The dry run reports the planned replacement; a missing or repeated anchor is skipped.

3 · You apply the edit The existing document gets the new date

After reviewing the script and dry-run log, you set DRY_RUN = false and run applyEdits.

Pilot schedule
Pilot begins on 11 May.
The review meeting stays on 18 May.

The second sentence and the rest of the proposal are outside this edit.

The excerpt is not a complete runnable script. Inspect the full script before use. Formatting and comment anchors on replaced text need checking; preservation is not guaranteed.

What you lose when the file is regenerated

  • Theme and branding
  • Comments and suggestion threads
  • Logos, notes, data validation, and layout

How a run works

  1. Point the agent at an existing Doc, Sheet, or Slides file (URL or ID) and the intended changes.
  2. Give it exact current text for anchors. If your host already has a Drive connector, it can read the file. The skill does not grant Google access by itself.
  3. Review the Apps Script it writes.
  4. Open the file, go to Extensions → Apps Script, paste, and run applyEdits.
  5. First run is a dry run. Read the log, set DRY_RUN = false, then run again.

Before running the generated script, confirm that it starts with DRY_RUN = true, uses the intended active file, logs missing or ambiguous anchors, and reports applied and skipped edits. Check repeat-run behavior for the specific operation. The script running as you, on your file, is the design. Generated output is not guaranteed to do all of that until you read it. Missing or ambiguous anchors are meant to be logged and skipped. For the showcased insert and update operations, a repeat run is meant to skip work that is already there.

Supported edits

Preservation is a design goal for the operations below. An edit adds a revision. The existing file stays the same artifact. Formatting and comment anchors are not guaranteed on every edit.

Surface Supported edits Watch
Docs Text swap, insert or delete at a unique anchor, and partial span styling Comment anchors on replaced or deleted text can orphan. Tabs cannot be deleted by script.
Sheets Cell or range value update at a unique finder, or a header plus offset Structural row changes can break dependent formulas. Notes and validation stay on cells you do not rewrite.
Slides Text on existing shapes, using replaceAllText or a targeted text range setText flattens mixed character styling. Moving or resizing many objects is layout surgery.

Install in your agent · Skills · Posts · GitHub

On the Catalyst Forge shelf next to TemperPass: a rule set you point an agent at.

Built by Catalyst Forge LLC. MIT.