agentleFS
RojiosRojios/everything-claude-code/skills/google-workspace-ops/SKILL.md

google-workspace-ops

Skill1 starsChanged 7 months agoMITView on GitHub

Operate across Google Drive, Docs, Sheets, and Slides as one workflow surface for plans, trackers, decks, and shared documents. Use when the user needs to find, summarize, edit, migrate, or clean up Google Workspace assets without dropping to raw tool calls.

6 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 6 are common, 0 are distinctive, and 0 are very specific to this project.

  • 6

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Use Google Drive as the entry point, then switch to the right specialist:

    line 21
  2. Common:

    Do not guess structure from filenames alone.

    line 27
  3. Common:

    Start with the Drive search surface to locate:

    line 33
  4. Common:

    If several documents look similar, confirm by title, owner, modified time, or folder.

    line 40
  5. Common:

    If the requested work is visual or layout-sensitive, iterate with inspection and verification instead of one giant blind update.

    line 58
  6. Common:

    When the file is part of a larger workflow, also surface:

    line 62

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Google Workspace Ops

This skill is for operating shared docs, spreadsheets, and decks as working systems, not just editing one file in isolation.

When to Use

  • User needs to find a doc, sheet, or deck and update it in place
  • Consolidating plans, trackers, notes, or customer lists stored in Google Drive
  • Cleaning or restructuring a shared spreadsheet
  • Importing, repairing, or reformatting a Google Slides deck
  • Producing summaries from Docs, Sheets, or Slides for decision-making

Preferred Tool Surface

Use Google Drive as the entry point, then switch to the right specialist:

  • Google Docs for text-heavy docs
  • Google Sheets for tabular work, formulas, and charts
  • Google Slides for decks, imports, template migration, and cleanup

Do not guess structure from filenames alone. Inspect first.

Workflow

1. Find the asset

Start with the Drive search surface to locate:

  • the exact file
  • sibling assets
  • likely duplicates
  • recently modified versions

If several documents look similar, confirm by title, owner, modified time, or folder.

2. Inspect before editing

Before making changes:

  • summarize current structure
  • identify tabs, headings, or slide count
  • detect whether the task is local cleanup or structural surgery

Pick the smallest tool that can safely perform the work.

3. Edit with precision

  • For Docs: use index-aware edits, not vague rewrites
  • For Sheets: operate on explicit tabs and ranges
  • For Slides: distinguish content edits from visual cleanup or template migration

If the requested work is visual or layout-sensitive, iterate with inspection and verification instead of one giant blind update.

4. Keep the working system clean

When the file is part of a larger workflow, also surface:

  • duplicate trackers
  • outdated decks
  • stale docs vs canonical docs
  • whether the asset should be archived, merged, or renamed

Output Format

Use:

ASSET
- file name
- type
- why this is the right file

CURRENT STATE
- structure summary
- key problems or blockers

ACTION
- edits made or recommended

FOLLOW-UPS
- archive / merge / duplicate cleanup / next file to update

Good Use Cases

  • "Find the active planning doc and condense it"
  • "Clean up this customer spreadsheet and show me the churn-risk rows"
  • "Import this deck into Slides and make it presentable"
  • "Find the current tracker, not the stale duplicate"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.