channel-portfolio-planner

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. 社媒渠道选择/渠道组合规划/平台能力矩阵/自然社媒

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable planning workflow with clear sequencing and validation checkpoints. Its main weakness is conciseness: an unnecessary attribution aside and repeated cross-skill references that could be tightened.

Suggestions

Remove or compress the Forrester POST-method attribution in step 1 — the 'People before platform' ordering stands on its own without the bibliographic aside.

Deduplicate cross-skill references: audience-mapper and voice-dossier-builder each appear in Reads, Instructions, Reference Materials, and Next Best Skill; consolidate to one canonical mention plus the routing context.

Tighten the boundary-routing table in step 5 so each routed skill is named once with its discipline tag, rather than restating the same skills again in Reference Materials.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but includes some unnecessary explanation, e.g. the 'Forrester's POST method (Li & Bernoff, Groundswell, 2008)... cited descriptively — scoring stays on ECHO' aside, and several references (audience-mapper, voice-dossier-builder) are restated across Reads, Instructions, Reference Materials, and Next Best Skill.	2 / 3
Actionability	Highly actionable for an instruction-only skill: concrete field lists ('publish, comments, DMs, and insights capability'), named tools (registry-events.py, pageviews.py, hn.py), and a concrete save path template 'memory/social/channel-portfolio-planner/YYYY-MM-DD-<topic>.md'.	3 / 3
Workflow Clarity	An 8-step sequenced workflow with explicit validation: a 'Done when' exit checklist, a NEEDS_INPUT stop-and-route gate in step 1, and a cadence-budget reality check checkpoint in step 4.	3 / 3
Progressive Disclosure	No bundle files are present, but the SKILL.md body functions as an overview pointing to one-level-deep, clearly signaled references organized into a dedicated Reference Materials section with descriptive labels.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: third-person voice, concrete action list, natural trigger phrasings in both English and Chinese, and an explicit out-of-scope boundary. It clearly answers both what and when.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'capability/access matrix, cadence-budget reality check, declared ECHO operating profile, boundary routing, and proposed-state registry events' — rather than vague language.	3 / 3
Completeness	Explicitly answers both what ('produces an audience/objective-first portfolio with...') and when ('Use when the user asks to...'), with an explicit out-of-scope boundary ('Not for recording canonical channel facts — use channel-registry').	3 / 3
Trigger Term Quality	Natural user phrasings are quoted directly ('pick which social channels to run', 'should we be on X platform or 小红书', 'plan our organic social channel portfolio') plus Chinese keyword variants, covering what a user would actually say.	3 / 3
Distinctiveness Conflict Risk	A clear niche (organic social channel portfolio planning) with distinct triggers and an explicit disambiguating boundary routing canonical-fact work to channel-registry, making wrong-skill activation unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

75%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 27 suspicious	Warning
referenced_paths_exist	Referenced path issues: 5 missing, 4 deeper-than-1-level	Warning

	Total	12 / 16 Passed

Repository: aaron-he-zhu/aaron-marketing-skills
Path: social/explore/channel-portfolio-planner/SKILL.md
Commit: 4a77c48

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.