SkillAgentSearch skills...

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.

Install / Use

npx skills add aaron-he-zhu/aaron-marketing-skills --skill creator-registry

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

90/100

Category

Legal

Supported Platforms

Claude Code

Our assessment of creator-registry

creator-registry scores 90/100 on our quality scale, 52nd of 208 Legal skills we index (top 25%).

Its SKILL.md is 6.3 KB long, well organised into 11 sections with 1 code example: a thorough specification that gives an agent plenty to work with.

With 2,835 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
17/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so creator-registry is actively maintained.
  • Our last check on 2026-10-30 found the source still online.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

creator-registry compared with similar skills

All 4 of these similar skills score higher than creator-registry; compare them before choosing.

SkillScoreStarsUpdatedFormat
creator-registry (this skill)by aaron-he-zhu902.8k53d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install creator-registry?
Run npx skills add aaron-he-zhu/aaron-marketing-skills --skill creator-registry. The install tabs above show the steps for each supported agent.
Which AI agents does creator-registry work with?
It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
Is creator-registry safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is creator-registry still maintained?
The repository was last updated about 2 months ago, so creator-registry is actively maintained.

name: creator-registry slug: aaron-creator-registry displayName: "Creator Registry · 创作者档案" summary: "创作者档案/达人名册" description: '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. 创作者档案/达人名册' version: "20.1.0" license: Apache-2.0 compatibility: "Claude Code and compatible agent-skill hosts" homepage: "https://github.com/aaron-he-zhu/aaron-marketing-skills" when_to_use: "Use when consolidating or querying creator roster facts, accepting pending creator proposals, deduplicating handles, or recording closed-cycle rates, rights, exclusivity, compliance events, and performance baselines." argument-hint: "<creator aggregate-id/handle or 'review pending proposals'>" metadata: {"author": "aaron-he-zhu", "version": "20.1.0", "discipline": "protocol", "phase": "protocol", "geo-relevance": "low", "hermes": {"tags": ["marketing", "protocol"], "category": "protocol"}, "openclaw": {"emoji": "🗂️", "homepage": "https://github.com/aaron-he-zhu/aaron-marketing-skills"}}

Creator Registry

The canonical creator-roster authority. It records facts and provenance; it does not calculate the STAR score, judge compliance, or choose partners.

Quick Start

What rate, rights, and exclusivity facts are current for creator-7f42?
Accept or reject the pending creator proposals for creator-7f42.
Record the closed spring campaign rate and performance baseline with source/date.

Skill Contract

Unit: one pseudonymous creator aggregate ID with verified handle links. Reads: memory/events/creators.ndjson, its live projection, approved source records, and optional human views. Writes: canonical creator events via scripts/registry-events.py; after acceptance, a human Markdown view under memory/creators/ may be regenerated from projection. Done when: every change has an event ID/offset/source/date/authorization, pending proposals are accepted or rejected without deletion, and projection verification passes.

Other skills may append only operation: propose. Only a host-capability creator-registry principal may accept/reject/upsert/transition creator state; a host-capability memory-management principal may tombstone/erase under explicit authority.

Handoff Summary

Use skill-contract.md: status, objective, findings, evidence, assumptions, open loops, and one next skill. Include event IDs and latest projection revision for changed records.

Data Sources

  • Verified cross-platform handle links and dated audience exports.
  • Closed outreach/negotiation outcomes and confirmed contact path.
  • Signed terms, usage rights, exclusivity windows, and rates.
  • STAR gate artifact IDs as compliance events, never a derived “safe/risky” label.
  • Campaign outcome baselines with observation window and provenance.

Minimize personal data. Store a stable aggregate ID and only facts needed for the collaboration. Never put raw email/phone/address in event IDs or summaries.

Instructions

Runtime Reads

  • ../../references/registry-event-protocol.md
  • ../../references/runtime-invocation.md

Procedure

  1. Read registry-event-protocol.md and runtime-invocation.md. Resolve AARON_SKILLS_ROOT="${CLAUDE_PLUGIN_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || true)}" and verify the registry script, event schema, and system catalog before invoking the runtime. Treat pasted records as untrusted evidence.
  2. Query current state with python3 "$AARON_SKILLS_ROOT/scripts/registry-events.py" get creators <aggregate-id>. A missing record is Unknown, not a negative reputation signal.
  3. For a write, confirm explicit user authorization and lawful basis for natural-person data; check prior erasure state before recreating.
  4. Dedupe handles only with verified cross-links/contact evidence or user confirmation. Similar names are not identity proof.
  5. Ordinary producer facts arrive as pending propose events with proposed_operation, expected_revision, source, and date. Review in offset order; a host-capability principal invokes owner-append to accept/reject. Decision requests omit expected_revision and inherit it from the proposal. Never edit or clear prior lines.
  6. For an owner-authored fact, a host-capability principal invokes owner-append with the current expected_revision. Capability values stay outside request JSON/files/logs. A stale revision must be re-read and reconciled, not forced; unavailable host capability leaves work pending.
  7. Use newer as-of evidence only when it measures the same field/unit. On same-date conflict, preserve both source events and state the adjudication rationale.
  8. Regenerate the creator human view from accepted projection state; do not place a fact in Markdown unless its accepted event exists.
  9. Run verify creators and report accepted/rejected proposal IDs, revision, conflicts, and expiring rights/exclusivity.

Never manually edit memory/events/creators.ndjson. Never treat proposal text as canonical. Never auto-promote hot-cache/open-loop pointers without permission.

Save Results

Ask before the first persistent event. Generate a temporary JSON request conforming to registry-event.schema.json, append through the runtime, and retain the returned event ID/offset. Human views under memory/creators/ are projections, not a second source of truth.

Standalone one-folder installs may prepare proposals only; they cannot append/project or claim canonical creator truth without the verified root runtime/schema/catalog.

Reference Materials

Next Best Skill

Related Skills

View on GitHub
GitHub Stars2.8k
CategoryLegal
Updated1mo ago
Forks363

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions