skills/strategy/strategy-channel-architecture/SKILL.md
Designs a multi-platform traffic flow system for a client — defining what role each platform plays, how audiences move between platforms, and how content flows through a hub-and-spoke architecture. Output is a channel architecture map the client can use to allocate effort and budget. Invoke when a client needs to rationalise their platform presence, is spreading effort too thinly, is launching a new social media programme, or needs a clear answer to "which platforms should we be on and what do we do on each one?"
npx skillsauth add peterbamuhigire/social-media-skills strategy-channel-architectureInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Designs a hub-and-spoke channel architecture — defining the conversion hub, assigning platform roles, mapping the customer traffic flow, and allocating content production effort. Based on Schaffer's platform role framework (Maximize Your Social, Wiley, 2013) and adapted for the Uganda/East Africa market.
Cross-reference: 05-social-media-strategy (overall strategy context), 10-content-pillars (what content to produce per platform), owned-media-strategy (hub development and owned channel depth).
SKILL.md; do not skip mandatory steps or required fields.references/ directory is added later, treat its files as the deeper source material and keep this SKILL.md execution-focused.references/launch-channel-sequencing.md when channel roles must support a timed launch, event, or campaign sequence.Before generating any output, ask for the following. Do not proceed until all six inputs are provided.
Produce the channel architecture map in six sections, in this order.
State the client's primary conversion hub clearly before any spoke assignments. The hub is the owned asset that converts — every platform drives traffic toward it.
Hub options (in order of EA priority):
| Priority | Hub | Best fit | |---|---|---| | 1 | WhatsApp Business | Service businesses, retail, any client where personal conversation drives conversion | | 2 | Google Business Profile | Location-based businesses — restaurants, clinics, shops, salons | | 3 | Landing page | Lead generation campaigns, event registrations, single-offer products | | 4 | Website / blog | Content-driven businesses with consistent publishing capacity | | 5 | Email list | Businesses with a regular newsletter, product launches, or subscription model | | 6 | Brick-and-mortar location | Retail clients where footfall is the primary commercial outcome |
Important EA note: Many Ugandan and East African SMEs have no website or maintain an outdated one. Do not assume a website is the hub. Ask explicitly. If the client names a website but it has not been updated in six months or has no clear call to action, recommend WhatsApp Business or a landing page instead and note the reason.
Output format for this section:
**Hub:** [Hub type and platform name]
**Hub URL / Contact:** [Link, phone number, or address]
**Rationale:** [One or two sentences explaining why this hub fits the client's goal and audience]
**Primary Call to Action:** [The single action all spokes should drive — e.g., "Message us on WhatsApp to book", "Visit our Google Business Profile to get directions"]
For each platform the client has provided, produce a one-row audit table. If the client cannot supply engagement rate or monthly reach, note "Unknown — recommend pulling from platform insights" and proceed.
| Platform | Followers | Monthly Reach | Avg. Engagement Rate | Primary Content Type | Primary Audience | Current CTA | |---|---|---|---|---|---|---| | [Platform] | [Count] | [Reach] | [Rate] | [Type] | [Age/Location] | [Current action directed] |
Below the table, identify:
Assign exactly one primary role to each active platform. Do not assign two roles to the same platform. If the client is on more platforms than there are roles, some platforms must be deprioritised.
Role definitions (Schaffer, 2013):
| Role | Definition | Best platforms in Uganda/EA | |---|---|---| | Discovery | First contact — the audience finds the brand for the first time | Facebook, TikTok, Instagram Reels, Google Search | | Engagement | Builds relationship and trust over repeated interactions | Facebook Groups, WhatsApp Community, Instagram feed | | Conversion | Drives the specific commercial action (enquiry, purchase, visit) | WhatsApp Business, Google Business Profile, landing page | | Retention | Keeps existing customers connected and loyal post-purchase | WhatsApp Broadcast, Email, Facebook Page | | Advocacy | Turns satisfied customers into active referrers | WhatsApp (referral asks), Instagram UGC, Facebook reviews, Google reviews |
Output format:
| Platform | Primary Role | Rationale |
|---|---|---|
| [Platform] | [Role] | [One sentence] |
Flag if any role is unassigned after the mapping — particularly Conversion and Retention, which are the two roles most often neglected by EA clients.
Map the full customer journey from first contact to post-purchase advocacy. Use the five-stage model: Discovery → Engagement → Conversion → Retention → Advocacy.
Present this as a written flow and a visual text diagram.
Written flow:
Describe what a new customer experiences at each stage — what they see, what they do, and what the brand does to move them to the next stage.
Text diagram:
[Discovery Platform]
↓
[Content or action that triggers move]
↓
[Engagement Platform]
↓
[Content or action that triggers move]
↓
[Conversion Hub]
↓
[Post-purchase action]
↓
[Retention Platform]
↓
[Advocacy ask or trigger]
↓
[Advocacy Platform / Referral channel]
Reference examples for EA context:
EA retail brand: Facebook Reel (discovery) → Facebook Page comment or DM (engagement) → WhatsApp Business chat (conversion) → WhatsApp Broadcast list (retention) → Customer posts a story tag (advocacy)
EA professional services: LinkedIn post (discovery) → LinkedIn connection and message (engagement) → WhatsApp call or meeting (conversion) → Email newsletter (retention) → Referral via LinkedIn recommendation (advocacy)
EA restaurant: TikTok video (discovery) → Instagram follow (engagement) → Google Business Profile booking (conversion) → WhatsApp broadcast for weekly specials (retention) → Google review (advocacy)
Adapt these patterns to the client's specific industry and hub. Do not copy them verbatim.
Based on role assignments and the client's available weekly production time, produce an effort allocation table. Apply the rule: no more than three platforms at High or Medium effort. Spreading effort across all platforms produces nothing remarkable on any platform.
| Platform | Role | Effort Level | Posts / Week | Content Types | |---|---|---|---|---| | [Platform 1] | Discovery | High | 5–7 | [e.g., Reels, short videos, carousels] | | [Platform 2] | Engagement | Medium | 3–5 | [e.g., comments, polls, Group posts] | | [Platform 3] | Conversion | Low (responsive) | As needed | [e.g., WhatsApp replies, GBP updates] | | [Platform 4] | Retention | Low (broadcast) | 1–2 | [e.g., WhatsApp Broadcast, email] | | [Deprioritised] | — | Minimal | 0–1 | [Maintain presence only] |
Effort level definitions:
After the table, include a weekly time budget breakdown. Show how the client's stated available hours map to the effort levels above.
Show how content moves from production through to distribution across spokes. The governing rule: produce once, publish everywhere — but adapt format and copy for each platform. Never cross-post identical content.
Three content tiers:
Tier 1 — Pillar Content (weekly or biweekly) One substantial piece of content produced per cycle. Lives on the hub or primary platform. Examples: long video, detailed blog post, in-depth LinkedIn article, recorded webinar, podcast episode.
Tier 2 — Derivative Content (3–5 pieces per pillar) Shorter pieces extracted or adapted from the pillar. Posted to spoke platforms across the week. Examples: quote graphic from blog post, 60-second Reel from long video, three-slide carousel summarising the article, caption thread from a webinar insight.
Tier 3 — Platform-Native Content (as needed) Quick, timely, or ephemeral posts made directly on each platform. Not derived from pillar content. Examples: Instagram Stories, WhatsApp status updates, TikTok trend participation, real-time event coverage.
Content flow diagram:
PILLAR CONTENT (produced once)
│
├──→ Tier 2: Short video clip → [Discovery platform]
├──→ Tier 2: Quote graphic → [Engagement platform]
├──→ Tier 2: Summary carousel → [Engagement platform]
├──→ Tier 2: Key insight caption → [Secondary platform]
└──→ Tier 3: Native story/update → [Each active platform]
│
All pieces include
CTA pointing to the Hub
Produce a completed version of this diagram using the client's actual platforms, content types, and hub.
Apply these standing recommendations unless the client's data contradicts them.
Output meets the standard if all of the following are true:
tools
Generates a foundational social media training guide for clients and their teams who are completely new to social media marketing, or who have been posting without any strategic understanding. Invoke when the user says "write a social media basics guide", "create a beginner training document", "the client doesn't understand social media", "start-here training", or when a client needs to understand social media before any strategy or content work begins. Distinct from training-client-team (operational handover of an existing strategy) and training-diy-content (content creation for self-managing clients). This skill covers what social media is, how it works, and how to approach it intelligently — the conceptual foundation that makes all downstream strategy work land.
tools
Generates a practical smartphone video production training guide for East African clients and content teams. Covers shooting, audio, lighting, framing, editing, and platform-specific formats using only a smartphone — no professional equipment required. Invoke this skill when a client or their team needs to produce their own social video content and requires a hands-on, jargon-free training document tailored to EA field conditions.
tools
Generates a complete DIY content creation handbook for clients who want to manage some or all of their own content after the initial strategy engagement. Invoke when the user says "write a DIY content guide", "create a self-managed content handbook", "the client wants to manage their own content", or when a handover guide is needed at the end of a strategy engagement. Output is a self-contained reference document — not a training presentation — that the client keeps and uses independently.
tools
Generates a complete 2-hour in-person training workbook for a client's internal team — employees who will assist with content creation or community management. Invoke when the user says "create a team training guide", "write a staff training workbook", "onboard our internal team on social media", or needs a printable workshop document for client employees. Output is a structured, print-ready workbook — not a presentation deck.