agency-multi-brand-pack

Generates branded asset batches for multiple retainer clients via the gen-ai CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running weekly or monthly creative production across many retainer clients usually means repetitive manual batch setup, brand-rule mistakes, and untraceable per-client spend. This Skill coordinates one batch run where every client's output is namespaced, brand-gated, and audit-ready. ## Core Features & Use Cases - Multi-client batch orchestration: Expands a clients × templates matrix into a single gen-ai batch manifest with per-client job IDs and output folders. - Brand isolation and audit trail: Enforces per-job brand rules, slug-namespaced outputs, and results.json-based per-client spend and completion reporting. - Use Case: An agency refreshes Q2 creative for 8 retainer brands — one dry-run estimate, one batch run with resume support, then per-client folders and billing breakdowns delivered to each client channel. ## Quick Start Ask the agent to run a multi-brand batch for your client slugs using this week's brief, with a dry-run cost estimate before execution.

Frequently Asked Questions about agency-multi-brand-pack

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

FAQPage Schema
How do I run one batch generation for multiple clients?▼

Build a manifest listing each client slug with its templates, expand it into flat jobs with IDs like client-slug/asset-name, then run gen-ai batch run with a dry-run estimate first. The slash in job IDs automatically creates per-client output subfolders.

How do I prevent brand cross-contamination in batch image generation?▼

Attach each client's brand rules at the job level, not the batch level, so every prompt carries the correct brand.md constraints. Also namespace all outputs by client slug to avoid filename collisions between clients.

What happens if a large gen-ai batch run fails midway?▼

Use gen-ai batch resume with the output directory to continue from where the run stopped instead of restarting. This preserves completed jobs and avoids paying twice for finished assets.

How do I track per-client spend for agency billing?▼

Tag every job with the client slug in its ID, then parse results.json to group completed and failed jobs per client. Combine this with gen-ai pricing data to produce a per-client spend breakdown for finance.

When should I not use a multi-brand batch workflow?▼

Avoid it for single-client deep-production work, where a client-specific workflow or pitch-mockup skill fits better. Multi-brand batching is designed for portfolio parallelism, not one-off detailed creative.