Maintain a creator roster with sourced records of past rates, usage rights, exclusivity, and campaign results. Query current facts, review proposed updates, and preserve a traceable history of accepted and rejected changes.
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. 创作者档案/达人名册
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
The canonical creator-roster authority. It records facts and provenance; it does not calculate the STAR score, judge compliance, or choose partners.
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.
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.
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.
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.
../../references/registry-event-protocol.md../../references/runtime-invocation.mdregistry-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.python3 "$AARON_SKILLS_ROOT/scripts/registry-events.py" get creators <aggregate-id>. A missing record is Unknown, not a negative reputation signal.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.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.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.
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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Audit paid advertising accounts before increasing spend by comparing campaign exports with your own sales or lead records. Review 20 criteria covering measurement, spending, and safety, then receive a decision and prioritized fixes.
Create paid-ad headlines, descriptions, and opening hooks that match the destination page. Build a matrix of messaging angles and variants, check format limits, and flag unsupported claims or policy risks before handing the set off for review.
Plan advertising and landing page experiments with a clear hypothesis, controlled variants, sample sizes, and duration. Interpret exported results by separating statistical evidence from meaningful business impact, applying an action rule only when its owner approved it in advance.
Design employee and founder sharing programs with voluntary participation, personalized share kits, disclosure lines, and staggered posting windows. Get roster and Slack or Teams distribution specifications, plus safeguards against identical coordinated posts and organized engagement exchanges.
Reconcile paid advertising conversions with GA4 or ecommerce order records. Identify duplicate and unmatched claims, align attribution windows and currencies, compare how models assign credit, and assess additional orders when test and control data are available.
Turn customer interviews and won or lost deal notes into a map of buyer beliefs, recurring objections, and reasons to switch or stay. Each finding includes its evidence, with suggested ways to address objections and clear labels for assumptions.