Ascend Skills Library
Ops

Google drive operations.

The creative-to-media-buyer asset handoff on Drive, and what has to be true before it passes.

v2.1.0·updated 18 Sep 2026·beta
Use the Ascend Skills: Google drive operations

Paste that line into your AI and it fetches this skill, whole and current, then asks you for what the skill needs. Not connected yet? How to connect.

Skill details

What it does

Campaign assets uploaded to the right client folder on Drive with a manifest beside them, and a handoff to the media buyer that passes one QA gate and needs no second approval.

Who uses it

opscreative producermedia buyerin Ops

What you need

Tools and access: Google Drive API credentials

You bring:

  • the client config with the folder ids
  • Google Drive API credentials as a key file
  • the assets and the brief

How it works4

The steps, in order. The method itself is served whole through the connector, current on every use.

  1. 1

    Pull the brand guide first

  2. 2

    Create the assets to spec

  3. 3

    Upload and write the manifest

  4. 4

    Post the QA sign-off

What it doesn't do

  • Finding client folders by name search
  • Deleting or re-sharing client assets on its own

When your AI reaches for it

Google Drive asset management for the creative-to-media-buyer handoff — client folder lookup, brand guide retrieval, asset upload, and the definition-of-done that gates a handoff. Use when uploading campaign assets, fetching a client's brand guide, or retrieving creative for campaign setup.

Latest change

v2.1.018 Sep 2026
Every work product now lands in the standard output tree (docs/SKILL-FORMAT.md, "Where a skill writes"): assets are created under `clients/<client>/creative/<campaign>/` before upload, and the Drive folder is named as a folder, not a path. No change to the method.

See all 6 releases →

Related skills