channel-registry

Use when the user asks to register/query a social channel, record channel state, cadence, governance, voice adaptation, UGC permission, or advocacy facts; curates them through the append-only channels event stream and derived views. Not for ECHO scoring — use social-quality-auditor; not for channel selection — use channel-portfolio-planner. 渠道台账/账号档案/UGC授权记录

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

82%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.

A well-organized, lean protocol skill body with a concrete sequenced procedure and clear reference navigation. The main gaps are a missing full invocation example and an implicit rather than explicit validation feedback loop.

Suggestions

Add a copy-paste-ready example invocation of registry-events.py (with a sample aggregate-id, transition, and expected_revision) so the common case is fully executable.

Make the validation feedback loop explicit in step 8 — e.g., 'If verify channels fails, review conflicts/revision mismatches, fix, and re-run until it passes.'

Clarify or bundle the ../../references/ files so the referenced materials are present and navigable within the skill bundle.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout — no explanations of concepts Claude already knows (channels, UGC, event streams); every section (Skill Contract, Data Sources, Procedure) earns its place and assumes competence.	5 / 5
Actionability	Concrete guidance with named scripts ('registry-events.py'), commands ('verify channels'), and an env-var resolution snippet, but no full copy-paste invocation example for the common cases, leaving a minor gap.	4 / 5
Workflow Clarity	A clear 8-step sequenced procedure with checkpoints (verify script/schema/catalog in step 1, compare-and-set expected_revision, 'verify channels' in step 8), though the validate→fix→retry feedback loop is implicit rather than spelled out.	4 / 5
Progressive Disclosure	Good structure with well-signaled one-level-deep references (registry-event-protocol.md, runtime-invocation.md, echo-benchmark.md) and clean sections, but the referenced files live at ../../references/ outside this skill's bundle, so they are not verifiable within the bundled structure.	4 / 5
	Total	17 / 20 Passed

Description

92%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.

A strong, comprehensive description that clearly states capabilities, trigger conditions, and boundaries with explicit routing away from sibling skills. The only mild gap is specialized terminology over natural synonyms in the trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across the domain — 'register/query a social channel, record channel state, cadence, governance, voice adaptation, UGC permission, or advocacy facts' and 'curates them through the append-only channels event stream and derived views' — giving comprehensive coverage rather than just 1-2 actions.	5 / 5
Completeness	Explicitly answers both what ('curates them through the append-only channels event stream and derived views') and when ('Use when the user asks to register/query...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural keyword coverage ('register/query a social channel', 'record channel state', 'UGC permission'), but terms skew specialized (cadence, governance, voice adaptation, advocacy) and lack common synonyms or extensions a 5 would require.	4 / 5
Distinctiveness Conflict Risk	Clear niche with explicit negative triggers — 'Not for ECHO scoring — use social-quality-auditor; not for channel selection — use channel-portfolio-planner' — minimizing conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

81%

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 — 13 / 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: 10 suspicious	Warning

	Total	13 / 16 Passed

Repository: aaron-he-zhu/aaron-marketing-skills
Path: protocol/channel-registry/SKILL.md
Commit: 888dd38

Reviewed: 6 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.