| name | channel-portfolio-planner |
| slug | aaron-channel-portfolio-planner |
| displayName | Channel Portfolio Planner · 渠道组合规划 |
| summary | 受众优先选社媒渠道/平台能力匹配矩阵/节奏预算体检/ECHO目标列声明 |
| description | Use when the user asks to "pick which social channels to run", "should we be on X platform or 小红书", or "plan our organic social channel portfolio"; produces an audience/objective-first portfolio with capability/access matrix, cadence-budget reality check, declared ECHO operating profile, boundary routing, and proposed-state registry events. Not for recording canonical channel facts — use channel-registry. 社媒渠道选择/渠道组合规划/平台能力矩阵/自然社媒 |
| version | 20.1.0 |
| license | Apache-2.0 |
| compatibility | Claude Code and compatible agent-skill hosts |
| homepage | https://github.com/aaron-he-zhu/aaron-marketing-skills |
| when_to_use | Use when choosing organic social channels before posting exists: match platform capabilities/access to audience and objective, declare the relevant ECHO program-maturity profile, size cadence against staffing, and route paid/creator/launch/email work to its owner. Not the channel fact record or voice dossier. |
| argument-hint | <objective + audience evidence> [candidate platforms] [staffing hours/week] |
| metadata | {"author":"aaron-he-zhu","version":"20.1.0","discipline":"social","phase":"explore","geo-relevance":"low","hermes":{"tags":["marketing","social","explore"],"category":"social"},"openclaw":{"emoji":"📣","homepage":"https://github.com/aaron-he-zhu/aaron-marketing-skills"}} |
Channel Portfolio Planner
Picks organic channels with audience and objective first. It feeds ECHO platform-capability evidence and submits each selected channel as a proposed-state event so no handle is treated as active without accepted registry state. It declares one operating profile for future program-maturity reads; the asset gate remains profile-independent.
Scope guard: this skill decides which channels to run. It submits proposed state but does not own canonical facts/transitions, voice records, norm cards, warmup, or ECHO gates. Adjacent paid, creator, launch, and email asks route to their owners.
Quick Start
Pick our organic social channels: dev-tool CLI product, audience = backend engineers, staffing = 1 founder + 1 DevRel at 6 hrs/week total.
Should we add 小红书 and 视频号? Objective: B2C skincare awareness in China. Audience research: [paste]. Current team: one part-time social manager.
Rebalance the portfolio — we hold 6 handles but only ship on 2. Staffing hours: [list]. Recommend keep / reduce / retire per channel.
Skill Contract
Expected output: a capability/access matrix, cadence-budget reality check, declared ECHO program-maturity profile, primary/secondary/watch tiers, boundary triage, authorized proposed-state events, and the standard handoff.
- Reads: objective and staffing capacity (User-provided); audience evidence from audience-mapper output in
memory/influencer/audience-mapper/ or pasted persona/analytics exports (User-provided); existing dossiers in memory/channels/ read-only, so re-planning starts from recorded states; platform capability and policy facts from official platform docs; public attention signals via scripts/connectors/pageviews.py and scripts/connectors/hn.py (keyless).
- Writes: the portfolio to its WARM path after permission; selected channel facts become authorized
operation: propose events. It does not write HOT automatically.
- Done when: every candidate platform has all four capability columns and an access class filled; the selected portfolio fits inside the stated staffing budget with every hour figure labeled; and each selected channel proposal is submitted through the runtime.
- Primary next skill: voice-dossier-builder — codify voice and content pillars for the channels just chosen.
