Skip to main content
Partner skill for Through-Channel Marketing. Skill ID: partner-cobrand-my-collateral Use when a partner wants to self-serve fully co-branded collateral from any vendor they work with, applying their own branding to vendor templates and downloading it in the format they need (PDF, DOCX, JPEG). Trigger phrases include “co-brand this vendor asset”, “put my branding on this”, “get a branded version of the deck”, “co-brand across my vendors”, “download a branded one-pager”, “make this my own”. Built for: Partner - Sales & Marketing · Partner Operations Workflow: Enumerate vendor portals → Find co-brandable templates → Apply my branding → Download in the right format
SKILL.md
---
name: partner-cobrand-my-collateral
description: Use when a partner wants to self-serve fully co-branded collateral from any vendor they work with, applying their own branding to vendor templates and downloading it in the format they need (PDF, DOCX, JPEG). Trigger phrases include "co-brand this vendor asset", "put my branding on this", "get a branded version of the deck", "co-brand across my vendors", "download a branded one-pager", "make this my own".
---

# Co-brand My Collateral (Partner)

**Audience**: Partner user, uses **claude.ai Introw Connect Staging** MCP across **all portals** the partner has access to.
**Use case**: Through-Channel Marketing (TCMA), partner-side, multi-vendor.

## When to use this skill

Use when a partner wants ready-to-use, fully co-branded collateral from their vendors — carrying both the vendor's and the partner's branding — without waiting on the vendor's design team or logging into each portal separately.

**Sample prompts that fire this skill:**
- "co-brand this vendor asset"
- "put my branding on this"
- "get a branded version of the deck"
- "co-brand across my vendors"
- "download a branded one-pager for the campaign"
- "make this my own"

## Why this matters
Partners rarely have design staff, so vendor collateral that needs branding work usually never gets used. Self-serving fully co-branded assets — in the format the partner needs — means the partner can put on-brand, dual-branded material in front of their customers in minutes, across every vendor they represent, from one assistant.

## Process

### Step 1: Enumerate vendor portals
- `Introw_Connect_Staging:partners`: get all portals the partner has access to.

### Step 2: Find co-brandable templates
For each `roomId`:
- Search the vendor's content / asset hub for templates marked co-brandable (those with partner-branding placeholders).
- Filter to what the partner actually needs (a specific campaign, product, or vertical).

### Step 3: Confirm the partner's branding
- Confirm the partner's own logo and details are on file with each vendor so the merge produces a fully branded result. Flag any vendor where branding is missing.

### Step 4: Generate and download
- Generate the co-branded copy per requested format (PDF, DOCX, JPEG).
- Confirm the vendor's locked branding is intact and the partner's branding merged correctly, then provide the download.

## Output format
- **Available co-brandable assets** across vendors: vendor, asset, formats offered.
- **Generated copies**: vendor, asset, format, download reference.
- **Fix list**: vendors where the partner's branding is missing and needs to be captured first.

## Guardrails & PRM best practice
- **Strictly scoped per portal.** Each vendor's assets are only fetched with its own `roomId`. No cross-portal leakage.
- **Respect locked areas.** Only the partner-branding fields change; never alter the vendor's locked branding or claims.
- **No fabricated branding.** If the partner's branding isn't captured with a vendor, capture it first — don't invent it.
- **Use current versions.** Always co-brand the latest template version the vendor published; don't reuse a stale local copy.
- **Cross-skill handoff.** Turn co-branded collateral into a live campaign via `partner-drip-campaign-from-assets`; plan which campaigns to run via `partner-cross-vendor-content-calendar`.
Drop this file into .claude/skills/partner-cobrand-my-collateral/SKILL.md in your repo and Claude Code triggers it on the prompts in its description. Or run the same play in plain language from Claude, ChatGPT, Slack, Teams, or your CRM through Introw’s MCP server: every action writes back to your CRM source of truth.