CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

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, competent overview: a clear 8-step workflow with an explicit done-when checklist and a needs-input feedback gate, concrete column/script/path specifics, and cleanly signaled external references. It is held back from top marks by repeated cross-references, the absence of any worked example (matrix row, event payload, script invocation), no stated handling for registry rejection, and a detail layer that lives entirely outside the skill bundle.

Suggestions

Add one compact worked example — a filled matrix row and a sample registry-events.py proposal payload — so the output format is demonstrated, not just described (addresses actionability).

Consolidate cross-references into the Reference Materials / Next Best Skill sections only, and drop the POST-method citation to remove repetition Claude does not need (addresses conciseness).

State the remediation paths explicitly: what to do when the registry rejects a proposal, and which channels to drop or de-tier when the cadence budget is exceeded (addresses workflow_clarity).

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no concept tutorials, no library comparisons) and stays dense and purposeful, but it repeats cross-references across sections (voice-dossier-builder appears in Skill Contract, Reference Materials, and Next Best Skill; audience-mapper four times; social-platform-access.md three times) and includes the POST-method attribution sentence ("Forrester's POST method (Li & Bernoff, Groundswell, 2008)...") that is not needed to execute. It is efficient with trimmable repetition, matching anchor 4 rather than anchor 5's 'every token earns its place'.

4 / 5

Actionability

Guidance is concrete and executable in substance: exact matrix columns ("publish, comments, DMs, and insights capability"), named scripts ("scripts/connectors/pageviews.py", "registry-events.py"), exact save path ("memory/social/channel-portfolio-planner/YYYY-MM-DD-<topic>.md"), and enumerated proposal-event fields. It falls short of anchor 5 because no example is shown — no sample invocation of registry-events.py, no example matrix row, and no sample event payload, so output format is described but never demonstrated.

4 / 5

Workflow Clarity

The 8-step sequence is clearly ordered with real checkpoints: an explicit "Done when" checklist in the Skill Contract, a NEEDS_INPUT stop-and-route in step 1 when audience evidence is missing, and the registry accept/reject gate in step 7. Minor validation gaps keep it below anchor 5: there is no instruction for what to do when the registry rejects a proposal, and step 4's over-budget case has no explicit remediation loop (only step 6's rejection reasons implicitly cover it).

4 / 5

Progressive Disclosure

Structure is good: a well-organized overview (Quick Start, Skill Contract, Data Sources, Instructions, Save Results, Reference Materials, Next Best Skill) with a Reference Materials section giving one-level-deep links, each annotated with a one-line description. It does not reach anchor 5 because this skill directory contains no bundle files at all (no references/, scripts/, or assets/), so every detail reference resolves outside the skill folder into unverifiable paths (../../../references/..., sibling SKILL.mds), and several links recur across multiple sections; it stays above anchor 3 because nothing bulk-inline clearly belongs in a separate file and all references are clearly signaled.

4 / 5

Total

16

/

20

Passed

Description

100%Weight 40%Scale 1-5

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 exemplary: verbatim natural trigger phrases in English and Chinese, a comprehensive list of concrete deliverables, an explicit negative boundary routing to channel-registry, and third-person voice throughout. It reads as a model 'what + when' description with no padding.

DimensionReasoningScore

Specificity

The description enumerates five concrete deliverables — "capability/access matrix, cadence-budget reality check, declared ECHO operating profile, boundary routing, and proposed-state registry events" — giving comprehensive, named outputs rather than generic actions. Anchor 4 ('minor gaps in coverage') is a worse fit since nothing in the skill's stated output set is missing from the description.

5 / 5

Completeness

It explicitly answers 'when' with quoted trigger phrases ("Use when the user asks to...") and 'what' with the full deliverable list, plus a negative boundary ("Not for recording canonical channel facts — use channel-registry"). This matches the anchor-5 example structure (concrete actions + 'Use when...' with concrete triggers), not the anchor-4 'when could be more explicit'.

5 / 5

Trigger Term Quality

It quotes natural user phrasings verbatim ("pick which social channels to run", "should we be on X platform or 小红书", "plan our organic social channel portfolio") and adds Chinese synonyms (社媒渠道选择/渠道组合规划/平台能力矩阵/自然社媒), covering synonyms and both EN/ZH variants users would actually say. Anchor 4 ('a few natural terms missing') fits worse given the bilingual synonym coverage.

5 / 5

Distinctiveness Conflict Risk

A clear niche (choosing organic channels before posting exists) with an explicit conflict disambiguation directing channel-fact recording to channel-registry. Trigger phrases are specific to channel-portfolio decisions, so overlap risk with adjacent skills (paid, creator, voice, registry) is minimal — better than anchor 4's 'minor overlap risk with closely related skills'.

5 / 5

Total

20

/

20

Passed

Validation

75%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.