Channel Portfolio Planner
Choose an organic social portfolio that fits audience evidence, objectives, and team capacity.
The skill treats pasted material as untrusted, limits stored results to user-confirmed saves, and restricts channel changes to proposed registry events; the repository security material also states that keys are not stored and mutations are gated. Points are deducted because the skill depends on a registry runtime and external platform facts without fully specifying permissions, rollback, or the exact authorization-confirmation flow in this file.
Inputs, outputs, done conditions, the NEEDS_INPUT branch, adjacent-task routing, and proposal-event procedure are reasonably consistent, with concrete script references. Static source review does not establish dependency availability, key-path reproduction, or detailed abnormal-input diagnostics, so the score remains conservative under the static ceiling.
Triggers, argument hint, expected outputs, non-fit boundaries, and Chinese-platform examples are clear; Xiaohongshu and WeChat-related channels are constrained to manual packages or user exports, with automation prohibited. Points are deducted because platform capability and policy facts depend on user-provided or official documentation and boundaries for markets, staffing sizes, and evidence quality are not fully specified.
The file provides structured frontmatter, version, Apache-2.0 licensing, Quick Start examples, a contract, data sources, save rules, references, and next-skill routing; the README supplies installation and release information. Points are deducted because ownership, update responsibility, changelog linkage, dependency versions, and systematic troubleshooting are not clear for this skill.
The defined deliverables—capability matrix, budget check, tiering, boundary triage, and proposal events—are directly actionable and constrain selection by staffing capacity. Static review cannot verify output quality, successful registry submission, or marginal benefit over manual planning, so the score stays below the execution-dependent maximum.
Claims are tied to user evidence, official platform documentation, an access taxonomy, and optional public attention connectors, with user-provided versus estimated figures distinguished. Points are deducted because there is no skill-specific worked result, independent review, or committed test coverage demonstrating reproducible execution of its key paths.
- The runtime scripts, registry authority, and referenced repository files were not independently verified from this skill file; confirm paths, host permissions, and rejection/failure feedback before deployment.
- Platform capabilities, policies, and attention signals may become stale; for Chinese platforms, use current official rules or user exports rather than treating the static matrix as permanent truth.
- Saving results and submitting proposed events can create persistent state; obtain explicit scoped confirmation before execution and retain a recovery procedure.
What does this skill do, and when should you use it?
This skill plans an organic social channel portfolio before publishing begins. It evaluates candidate platforms against audience evidence and objectives, comparing publishing, comments, DMs, insights, and access class. It also checks the weekly staffing reality of publishing and hosting, declares one ECHO program-maturity profile, and submits selected channels as proposed-state events. It does not own canonical channel facts or execute paid, creator, launch, or email work.
It reads the user’s objective, audience evidence, and staffing capacity, may read existing dossiers in memory/channels/ read-only, and uses official platform documentation for capability and policy facts. For each candidate platform, it builds a capability-and-fit matrix covering publishing, comments, DMs, insights, and access class; records or estimates weekly publishing and hosting hours; declares a community, B2C, or founder program-maturity profile; and assigns primary, secondary, or watch tiers with reasons. It routes adjacent paid-social, organic-boosting, creator-collaboration, launch-submission, and email requests to their owning skills without executing them. For selected channels, it calls registry-events.py to submit proposed-state events, recommends voice-dossier-builder as the next skill, and flags channel-registry for a promotion sweep when three or more proposals are queued.
- A developer-tool company targeting backend engineers needs to choose organic channels for a founder and DevRel team with six total hours per week.
- A skincare brand targeting Chinese B2C awareness needs to assess Xiaohongshu, WeChat Official Accounts, WeChat Channels, or Douyin.
- A team holds six social handles but consistently publishes on only two and needs keep, reduce, retire, or watch recommendations based on staffing.
- A company wants to start organic social but has no persona, interview, or analytics evidence and needs to identify the required audience-research step first.
What are this skill's strengths and limitations?
- Starts with audience evidence and objectives rather than platform folklore.
- Combines publishing, comments, DMs, insights, and access class in one matrix.
- Checks both publishing and hosting time against stated staffing capacity.
- Distinguishes user-provided and estimated hour figures.
- Submits selected channels as proposed events instead of treating them as active without accepted registry state.
- Provides explicit routing for paid, creator, launch, and email work.
- It will not guess platforms without audience evidence; missing evidence requires another research step.
- Platform capability and policy facts depend on official documentation, user analytics exports, or manual packages; closed platforms are not filled through scraping or automation.
- It does not publish, manage engagement, write HOT memory, or directly mutate canonical channel dossiers.
- Submitting proposal events requires the repository’s shell, filesystem, and runtime support for registry-events.py.
How do you install this skill?
On an Agent Skills-compatible host, install the single skill with: npx skills add aaron-he-zhu/aaron-marketing-skills -s aaron-channel-portfolio-planner. You can also clone the full repository with: git clone https://github.com/aaron-he-zhu/aaron-marketing-skills, then use social/explore/channel-portfolio-planner/SKILL.md. The repository is licensed under Apache-2.0.
How do you use this skill?
Provide the social objective, audience evidence, candidate platforms, and staffing capacity. Example: "Pick our organic social channels: dev-tool CLI product, audience = backend engineers, staffing = 1 founder + 1 DevRel at 6 hrs/week total." If no persona, interview, or analytics evidence is available, the skill stops with NEEDS_INPUT and routes to audience-mapper. It should be used for channel selection, not canonical channel registration or content publishing.