agency-client-handoff

Package completed agency engagements into reproducible white-label client handoff zip bundles.

4|2|Updated May 6, 2026
One-click install
npx skills add https://github.com/PicsArt/gen-ai-skills --skill agency-client-handoff-picsart
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-client-handoff
Source: https://github.com/PicsArt/gen-ai-skills/tree/main/skills/agency-client-handoff
Command: npx skills add https://github.com/PicsArt/gen-ai-skills --skill agency-client-handoff-picsart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an agency engagement ends, clients need more than a folder of final assets — they need the prompts, pinned model versions, brand documentation, and rights records required to regenerate consistent work without the agency. This Skill automates the inventory, filtering, metadata stripping, model pinning, documentation, packaging, and cold-test verification of a formal client handoff bundle. ## Core Features & Use Cases - Inventory and filtering: Pulls every asset and results.json from the client workspace, excluding drafts, rejected variants, and internal WIP. - White-label stripping and model pinning: Removes internal tags and competitor references, and locks every prompt to an exact model ID and version via gen-ai models info. - Documentation and packaging: Generates README, RIGHTS.md, CHANGELOG, prompt library, and a handoff-manifest.json, then zips everything with a consistent folder structure. - Cold-test verification: Extracts the zip to a clean directory and dry-run regenerates one asset to prove reproducibility before delivery. - Use Case: An agency finishing a year-long retainer for a fintech client packages 247 assets and 54 prompts into a versioned handoff zip, delivers it to the client's DAM, and the in-house team regenerates on-brand assets using a stock gen-ai CLI install. ## Quick Start Ask the agent to package the completed engagement for client acme-fintech into a white-label handoff zip with pinned models, prompt library, and rights documentation, then cold-test one regeneration before delivery.

Frequently Asked Questions about agency-client-handoff

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

FAQPage Schema
How do I create a client handoff package for an agency engagement?▼

Inventory all assets and results.json files from the client workspace, filter out drafts and internal WIP, strip internal tags, pin every model to an exact version, generate README and rights documentation, then zip the bundle and cold-test one regeneration before delivery.

How do I pin AI model versions for reproducible generation?▼

Run gen-ai models info <id> --json for every model used in the engagement and save the exact IDs to a model-pins.json file. Never ship prompts referencing 'latest', since model drift breaks reproducibility when the client regenerates months later.

What should be included in a creative agency client handoff?▼

Include final assets, a prompt library, pinned model IDs, brand-system.json and brand rules, RIGHTS.md, a CHANGELOG, and a handoff-manifest.json describing scope and regeneration support. Add CLI install steps so the receiving team can regenerate on a stock setup.

Why does client regeneration produce different output than the original assets?▼

Output drift happens when prompts reference unpinned or 'latest' model versions that changed since the original generation. Fix it by locking every prompt to the exact model ID and version recorded at handoff time and verifying with a dry-run regeneration.

When should I not use a formal handoff bundle?▼

Skip the handoff bundle for work-in-progress reviews, approval cycles, or internal archival — use Drive links, proof PDFs, or your agency's backup instead. Handoff is reserved for the formal, client-owned, reproducible final delivery.