CtrlK
BlogDocsLog inGet started
Tessl Logo

creator-registry

Use when the user asks "what did we pay this creator last time" or to "update the creator roster"; curates creator identity, rate, rights, exclusivity, compliance-event, and performance facts through the append-only creators event stream. Not for scoring fit — use fit-scorer; not for reviewing content — use creator-content-auditor. 创作者档案/达人名册

77

Quality

100%

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

100%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 content is a tight, protocol-focused overview with concrete commands, an ordered workflow including validation and reconciliation feedback, and a well-organized one-level reference structure. It assumes Claude's competence and avoids concept over-explanation.

DimensionReasoningScore

Conciseness

The body is dense with domain-specific protocol facts Claude does not already know (capability principals, owner-append/propose operations, revision reconciliation) and never explains basic concepts; every token earns its place.

3 / 3

Actionability

Provides concrete executable guidance — `python3 "$AARON_SKILLS_ROOT/scripts/registry-events.py" get creators <aggregate-id>`, the exact AARON_SKILLS_ROOT resolution, and `registry-event.schema.json` — and the policy steps are specific and actionable rather than vague.

3 / 3

Workflow Clarity

A 9-step ordered sequence includes an explicit validation checkpoint ("Run verify creators and report accepted/rejected proposal IDs, revision, conflicts...") and error-recovery feedback ("A stale revision must be re-read and reconciled, not forced").

3 / 3

Progressive Disclosure

The body is a lean overview that points one level deep to well-signaled references (skill-contract, registry-event-protocol, runtime-invocation, state-model, SECURITY, and the real bundled creator-record-template.md), with a dedicated Reference Materials section.

3 / 3

Total

12

/

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: it states concrete capabilities, includes natural user-spoken triggers, answers both what and when, and explicitly distinguishes itself from sibling skills. No dimension falls below the top anchor.

DimensionReasoningScore

Specificity

Names a concrete domain (creator roster) and enumerates specific fact types — "creator identity, rate, rights, exclusivity, compliance-event, and performance facts" — plus the mechanism "append-only creators event stream", matching the multiple-concrete-actions anchor.

3 / 3

Completeness

Explicitly answers both what ("curates creator identity, rate, rights...") and when ("Use when the user asks...") with an explicit Use-when clause, the top anchor.

3 / 3

Trigger Term Quality

Quotes two natural phrases a user would actually say — "what did we pay this creator last time" and "update the creator roster" — giving good coverage of natural trigger terms.

3 / 3

Distinctiveness Conflict Risk

Negative carve-outs ("Not for scoring fit — use fit-scorer; not for reviewing content — use creator-content-auditor") carve a clear niche unlikely to trigger the wrong skill.

3 / 3

Total

12

/

12

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.

Validation12 / 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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

16

Passed

Repository
aaron-he-zhu/aaron-marketing-skills
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.