ship

Name: ship
Availability: InStock
Author: rooster-sanchez

Export approved ad batches to Google Drive with a manifest.json and final images.

2|Updated Apr 5, 2026

Search Tags:#workflow #manifest #ship #drive #google-drive #ads

Ready to run

npx skills add https://github.com/rooster-sanchez/iterator-template --skill ship-rooster-sanchez

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/rooster-sanchez/iterator-template/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/rooster-sanchez/iterator-template --skill ship-rooster-sanchez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exports an approved ad batch to Google Drive, generating a manifest.json and final images in a shared Drive folder to streamline post-review delivery.

Core Features & Use Cases

Export to Google Drive: creates a versioned, shareable folder and uploads final assets.
Manifest generation: builds a structured manifest.json detailing the batch, ads, and assets for downstream launchers.
Post-review workflow: enables shipping after /review-batch approval and maintains an auditable trail.

Quick Start

After batch approval, run the /ship command to export the batch to Drive, generate the manifest.json, and upload final images to the shared folder.

Frequently Asked Questions about ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I export approved ads to Google Drive with a manifest?▼

Export approved ads to Google Drive by running the ship command, which automatically creates a versioned folder, uploads final images, and generates a structured manifest.json for the batch.

What is the workflow for shipping post-review ad batches to Drive?▼

The post-review workflow for shipping ad batches to Drive requires batch approval first, then running the ship command to export assets and generate a manifest.json for downstream launchers.

Do I need Google Drive authentication to ship ad assets?▼

Yes, Google Drive authentication is required to ship ad assets, as the process creates a shareable folder and uploads final images and a manifest.json directly to the shared Drive.

How do I structure output batches for Google Drive delivery?▼

Structure output batches under clients/{slug}/output to ensure the ship command can locate available assets, generate a manifest, and upload them to Drive with predictable folder naming.

Can I integrate shipped ad assets with a downstream launcher?▼

Yes, shipped ad assets integrate with downstream launchers through the generated manifest.json, which details the batch, ads, and assets to ensure predictable folder naming and uploads.

What limitations exist when exporting ad batches to Google Drive?▼

Exporting ad batches requires a valid manifest structure and batch availability under clients/{slug}/output; without these prerequisites, the ship command cannot deliver assets to Drive.