CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 content is an exemplary lean protocol overview: dense operational instructions, explicit lifecycle and revision rules, verification checkpoints, and clean one-level reference structure. The only meaningful gaps are the absence of an example append/upsert command or event payload and an explicit error-recovery loop for revision conflicts or failed validation.

DimensionReasoningScore

Conciseness

The body is lean and telegraphic with zero concept-explanation padding — every section (Quick Start, Skill Contract, Data Sources, Procedure) carries only operational facts and defers detail to the protocol references, matching the "every token earns its place" anchor; it is not anchor 4 because there is no over-explanation left to trim.

5 / 5

Actionability

Concrete guidance dominates — specific paths (memory/events/channels.ndjson), script name (registry-events.py), a shell snippet for AARON_SKILLS_ROOT, the explicit state machine (proposed → warming → active → paused → retired), and the verify channels command — but the core append/upsert invocation has no example command or event payload in SKILL.md, leaving minor gaps characteristic of anchor 4.

4 / 5

Workflow Clarity

The 8-step Procedure is clearly sequenced with real checkpoints ("verify the registry script, event schema, and system catalog before invoking"; "run `verify channels`" after regenerating views) and compare-and-set revision discipline, but there is no explicit error-recovery loop for revision conflicts or failed validation, so it fits anchor 4 rather than 5.

4 / 5

Progressive Disclosure

The file is a clear overview with well-signaled one-level-deep references (Runtime Reads and Reference Materials sections with labeled links to registry-event-protocol.md, runtime-invocation.md, echo-benchmark.md, SECURITY.md) plus a Next Best Skill routing section, and all detail is appropriately split out rather than inlined, matching anchor 5; no bundle files exist alongside this SKILL.md to introduce nested-reference risk.

5 / 5

Total

18

/

20

Passed

Description

78%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, well-scoped description with explicit and specific trigger guidance, negative boundaries against neighboring skills, and bilingual trigger terms. Its main weakness is that the capability statement (the "what") is phrased abstractly through event-stream mechanics rather than concrete operations, keeping specificity and completeness at the 4 level.

Suggestions

State the core capability in concrete operational verbs up front (e.g., "Registers brand social channels and their governance/cadence/voice facts, records UGC permissions and advocate opt-ins, and answers queries about current channel state") before the trigger clause.

Replace internal jargon in the trigger list with phrases a user would naturally say (e.g., "social media account", "channel ledger", "UGC rights") alongside the existing domain terms.

Trim the Chinese keyword tail to the highest-value user phrases so the description stays scannable in both languages.

DimensionReasoningScore

Specificity

The description lists several specific actions ("register/query a social channel, record channel state, cadence, governance, voice adaptation, UGC permission, or advocacy facts") with enumerated fact types, but the operations remain somewhat abstract ("curates them through the append-only channels event stream and derived views") rather than fully concrete, matching anchor 4 rather than 5.

4 / 5

Completeness

The "when" is explicit and specific ("Use when the user asks to register/query a social channel, record channel state, cadence, governance, voice adaptation, UGC permission, or advocacy facts") and a "what" is present ("curates them through the append-only channels event stream and derived views"), but the what is abstract rather than concrete, so it does not reach anchor 5's fully explicit both-answers standard.

4 / 5

Trigger Term Quality

Trigger coverage is good within the niche (channel state, cadence, governance, voice adaptation, UGC permission, advocacy, plus Chinese synonyms "渠道台账/账号档案/UGC授权记录"), but it leans on internal jargon ("append-only channels event stream", "advocacy facts") and misses a few natural user phrasings, fitting anchor 4 rather than comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche and explicitly disambiguates against the two closest neighbors ("Not for ECHO scoring — use social-quality-auditor; not for channel selection — use channel-portfolio-planner"), giving minimal conflict risk and matching anchor 5.

5 / 5

Total

17

/

20

Passed

Validation

81%

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

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: 10 suspicious

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

protocol/channel-registry/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.