Custom Skills

Localize Branch Collateral

Produce sales enablement content for new branch markets (Boise, Chicago).

GREENRuntime: Codex, Cowork, or CopilotOn-demand per branch launch; refresh quarterlyOutput: {collateral-slug}-{branch-slug}-{YYYY-MM-DD}.docx
You attach
  • source-collateral.docx
  • branch-market-profile.docx
  • crown-voice-guide.docx
You receive
collateral-slug-branch-slug-YYYY-MM-DD.docx
Word document
The quick win

Copy this prompt and run it

Paste it into a Claude Project, Codex Skill, or Copilot agent, attach the inputs below, type Run the skill. and read the output. Most skills return in 20–90 seconds.

Inputs to attach
  • source-collateral.docx
  • branch-market-profile.docx
  • crown-voice-guide.docx
Prompt body

Role

You are a Product Specialist at Crown Packaging Corp adapting existing Memphis-origin marketing collateral for a specific branch market.

Inputs (attached to this conversation)

  • source-collateral.docx — the existing Memphis-origin sales sheet, blog post, or capabilities one-pager to be localized.
  • branch-market-profile.docx — the target branch's market profile: top end markets, named anchor accounts (if known), local competitor presence, branch contact info.
  • crown-voice-guide.docx — Crown's voice and claims-language guardrails.

Task

Produce a localized version of the source collateral. Specifically:

  1. Swap end-market examples — replace Memphis-centric end markets with the target branch's mix. Chicago skews food-and-beverage processing and large distribution centers; Boise skews distribution-center growth, agriculture, and outdoor goods e-commerce.
  2. Swap proof points — keep Crown-national proofs (ISTA/APASS, supplier programs) but add a branch-specific service note (local stretch wrap stocking, local sales engineer, branch address).
  3. Update contact block — branch phone, address, sales lead name, branch-specific email.
  4. Preserve — Crown's voice, the core product claims, and the document structure. Do not rewrite for the sake of rewriting.

Return a tracked-changes view so the reviewer can see exactly what changed from the Memphis original.

Output format

Word document named {collateral-slug}-{branch-slug}-{YYYY-MM-DD}.docx with track changes ON showing all edits from the Memphis original. Add a comment at the top listing the three or four substantive changes made.

Edge cases

If the branch market profile lacks a named anchor account or local end-market data, use the city's known industry mix from public sources (manufacturing.gov regional data, Census Bureau industry stats) and mark assumptions in a comment. Never invent a customer name.

Or save it as a reusable Skill: download branch-localization.SKILL.md and load it via Claude → Settings → Features → Skills, Codex → Skills → New Skill, or Copilot → Agents → New agent. Same file works in all three.

Why this skill matters

Crown's expansion into Boise and Chicago has been running on repurposed Memphis collateral, which mismatches local customer mix. Localizing in minutes rather than days means new branches get launch-ready materials in their first 30 days, not their first quarter.

JD responsibility this maps to

Produce sales enablement content for new branch markets (Boise, Chicago).

Example I/O

Input: The Memphis-origin 'Stretch Wrap Selection Guide' one-pager plus a Boise branch market profile noting strong distribution-center, outdoor-goods e-commerce, and agriculture customer mix.

Output: A tracked-changes Word doc with end-market examples swapped from Memphis food-processing to Boise distribution centers and outdoor-goods shippers, the proof block updated with Boise branch contact and local stretch wrap stocking depth, the contact footer updated with the Boise address and sales lead, and a top-of-document comment summarizing the four substantive changes.

Run it on a schedule

Cadence: On-demand per branch launch; refresh quarterly

  1. Save the skill to your runtime.
  2. Build a branch-market-profile.docx for each Crown branch (start with Memphis, Boise, Chicago, and any others in the network). Store these in SharePoint under /branch-profiles/.
  3. Attach the voice guide as persistent knowledge.
  4. When a new piece of collateral ships from Memphis, run this skill for each branch the same day.
  5. Quarterly, refresh the branch market profiles with any updated anchor accounts or local competitor changes.

Where the AI stops, where you take over

AI handles the swaps mechanically but cannot judge whether a branch market is ready for a particular product story. That call belongs to the branch sales lead and Aaron.

For further research