Agent skill · marketing growth · aiskillstore
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. 创作者档案/达人名册
Why this skill is useful
Adds domain-specific knowledge for managing creator data and compliance events that the AI wouldn't reliably generate on its own.
What it needs
Requires python3 installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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 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 1. Read registry-event-protocol.md and runtime-invocation.md. Resolve AARONSKILLSROOT="${CLAUDEPLUGINROOT:-$(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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/creator-registry