How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

google-workspace-ops - Skill

Name: google-workspace-ops
Author: affaan-m

Imported from affaan-m/ecc (skills/google-workspace-ops/SKILL.md) via skills.sh. Install upstream with npx skills add affaan-m/ecc --skill google-workspace-ops. Copyright stays with the author.

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"

Install google-workspace-ops and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "affaan-m-ecc-google-workspace-ops", "kind": "skill", "name": "google-workspace-ops", "description": "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.", "publisher": "affaan-m", "version": "1.0.0", "capabilities": { "domains": [ "customer_support" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "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." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/affaan-m/ecc", "path": "skills/google-workspace-ops/SKILL.md", "ref": "HEAD", "url": "https://www.skills.sh/affaan-m/ecc/google-workspace-ops", "key": "affaan-m/ecc/skills/google-workspace-ops/SKILL.md" } }, "instructions": "# Google Workspace Ops\n\nThis skill is for operating shared docs, spreadsheets, and decks as working systems, not just editing one file in isolation.\n\n## When to Use\n\n- User needs to find a doc, sheet, or deck and update it in place\n- Consolidating plans, trackers, notes, or customer lists stored in Google Drive\n- Cleaning or restructuring a shared spreadsheet\n- Importing, repairing, or reformatting a Google Slides deck\n- Producing summaries from Docs, Sheets, or Slides for decision-making\n\n## Preferred Tool Surface\n\nUse Google Drive as the entry point, then switch to the right specialist:\n\n- G", "cost": { "context_tokens": 600 } }

google-workspace-ops

About

Google Workspace Ops

When to Use

Preferred Tool Surface

Workflow

1. Find the asset

2. Inspect before editing

3. Edit with precision

4. Keep the working system clean

Output Format

Good Use Cases

Install google-workspace-ops and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews